US Election Day is Tuesday, November 3, 2026. Use these checks to prepare your application for heavy traffic before the event and ensure your team is set up for a smooth event day (and night!).
Start here: Do ASAP
1. Tell VIP about your plans
We’ll be on hand no matter what, but letting us know in advance ensures you’re on our radar.
Open a Support ticket with:
- Anticipated coverage window and peak traffic hours.
- Expected traffic numbers, using peak hourly sessions from 2020, 2022 and 2024.
- Your key URLs for heavy traffic.
- Every third-party dependency.
- Custom cron jobs.
- Apps that rely on the site, for example: mobile apps.
- A note if the site is decoupled, has middleware, or is behind a reverse proxy.
- High traffic API endpoints.
2. Review performance
The two numbers that matter most are cache hit rate and origin response time. Both are in Insights & Metrics in your VIP Dashboard. Last-minute tuning tends to force compromises, and slow queries often stay hidden until traffic rises. The weekly Performance Report tab gives a health score and a cache hit rate card.
For sites with VIP APM or New Relic enabled, performance bottlenecks can be quickly identified by checking the stack trace on requests with the longest response time.
3. Load test responsibly, or not at all
VIP scales automatically, so most sites don’t need a load test. If you run one, open a ticket first describing its goals, method, and success criteria. Then:
- Run a baseline test before and after each change.
- Ramp traffic up gradually.
- Stop as soon as you hit your failure threshold.
- Size the test for origin traffic. On average only about 1 in 10 requests reaches the origin.
- Edge IP rate limiting applies to everyone and has no exemptions.
- Notify VIP at least a week ahead. Give the environment, rate, duration, source IPs and URLs.
Plan now for a smooth event day
4. Set a feature cut-off and a code freeze
Ship election features as early as possible, preferably by October 22, including any WordPress, PHP or plugin updates. Freeze all code by October 27. Make sure the team knows how to roll back a deployment from the VIP Dashboard.
- Rollback covers only the three most recent unique production deployments.
- It needs an Org member or admin role, or an App write role.
- It does not change the database or the GitHub history.
- WordPress minor and security releases apply automatically, and managed updates move sites to the latest stable release.
5. Prepare fallbacks
Have these ready before the event:
- A lightweight homepage template.
- A super lightweight 404 template.
- A switch to turn off each widget, in case of emergencies.
- Pull requests that fix your slowest queries, deployed ahead of code freeze.
6. Monitor and set alerts
- Set your own alert thresholds for origin response time, cache hit rate, and slow queries, and send alerts to your team. This requires an Enhanced, Signature, or Premier package.
- Use VIP APM or New Relic for detail on slow code.
7. Staff the event and know how to escalate
- Name an on-call engineer and an editorial contact.
- If the site becomes unstable, open an Urgent ticket.
- Confirm editors can still use /wp-admin under load.
- Plan for traffic to stay high for several days, and hold a review afterward.
Next: Review caching
8. Protect your cache hit rate
Remove anything that makes logged-out pages skip the cache:
- Extra query parameters.
- Cookies.
- Requests other than GET.
- Unnecessary Vary headers.
- HTTP authorization headers.
9. Set cache times on purpose
Give pages that rarely change a longer cache time (max-age). Give fast-moving pages a short cache time, no less than 60 seconds.
- Above about 24 hours, rarely requested content wastes page cache space.
- s-maxage takes precedence over max-age.
- A custom max-age cannot be set for files in the VIP File System, or for 301, 302, 307, 404 and 410 responses (cache-control headers).
- The REST API default is already 60 seconds.
10. Purge narrowly
Purge specific URLs with VIP’s purge tools. Don’t clear the homepage on every update. Never flush the whole page cache or object cache during the event. A code deploy will not cause the object cache to be flushed, and will not clear the page cache for a site’s cached content responses. A code deploy will purge any static assets if their files change.
- Switching the active theme purges the whole page cache.
- Purging a URL purges all of its query-parameter variants.
- The purge tools take up to 4,000 URLs at a time. A full-site purge can cause the site to experience temporary instability (purge tools).
- Do not flush the object cache, particularly during high traffic events (more on flushing the object cache).
11. Make live updates cache-friendly
- Live results endpoints are the most heavily trafficked resources on an election site.
- Results widgets and live blogs should poll cacheable endpoints with a cache time of at least 60 seconds.
- Add exponential backoff and a kill switch.
- Never call authenticated REST endpoints from public pages.
- Pause polling when document.visibilityState is hidden.
- Do not use cache: “no-store.”
- Run one poller per page, not one per widget.
- Make sure any CDN in front of VIP caches wp-json.
- REST responses must never cause database writes.
- /wp-admin/admin-ajax.php requests are never cached, so do not poll them.
Next: Review requests at the origin
12. Fix slow queries
Use Query Monitor and the database metrics. Pay particular attention to core queries that slow down as content grows, and to functions WordPress doesn’t cache. Remove SQL_CALC_FOUND_ROWS. Add no_found_rows to the WP_Query if pagination is not needed. Eliminate front-end writes and minimize DB updates.
13. Use the object cache, with protection against stampedes
Cache expensive fragments with staggered expiry times. While a value is being rebuilt, serve the stale copy so many requests don’t rebuild it at once.
- Optimize the query first: It is best not to completely rely on the object cache.
- Cache entries must be kept under 1MB in size. Don’t store the entirety of the post content in cache; instead, store post IDs.
14. Offload heavy WP Query requests to Enterprise Search
This covers site search, feeds, sitemaps, SEO metadata, and related-content queries.
15. Take remote requests out of page loads
Fetch election results feeds and APIs with cron or cache them, set firm timeouts, and show the last good result if a feed fails.
- wpcom_vip_file_get_contents() caches the result and returns the last cached copy when a request fails. Its timeout defaults to 3 seconds, and the documentation strongly discourages a longer one.
- vip_safe_wp_remote_get() does not cache. Its timeout defaults to 1 second, and it has a fail threshold.
Finally: Check your edge and security layers
16. Check every layer in front of VIP
- Third-party CDNs must pass VIP’s required headers and respect cache purges (Host and True-Client-IP).
- Without IP headers, DDoS detection and login rate limiting will be ineffective, and IP Restrictions will not work as expected.
- Bot protection must not block legitimate readers or monitoring.
Ready? It’s election night!
If anything goes amiss, don’t hesitate to open a ticket.
You got this!