Speed
Test before turning on, scripts that wait, top of the page first, Cloudflare, database and memory.
What it is
Besides the cache, the Speed screen has the optimizations that speed things up the most — and you can test them in your own browser before turning them on for everyone. It also shows how many visits get the page ready, what weighs on the database, how much memory the site uses and the heaviest plugins.
How to use it
- In Speed → Test before turning on, click "Test first" on the optimization you want (scripts on first interaction, critical CSS, only draw what is on screen, preload the next page). The site opens in test mode only for you, with a bar at the bottom.
- Browse, open the menu, use the form and the chat. If everything works, click "All good — turn on for everyone"; if something breaks, "Something broke — turn off". Visitors see nothing until you approve.
- For critical CSS, first click "Generate the critical CSS": your browser opens the home page, a post and a page and keeps only the styles of what shows before scrolling. When the theme or Elementor change, the screen tells you to generate it again.
- In "Scripts that wait for the first touch", read the home page and choose script by script. Chat and heatmaps wait; Analytics, Tag Manager and Pixel do not (so no visit or ad conversion is lost), unless you choose so.
- If your site is behind Cloudflare, paste in the Cloudflare card a token with the "Zone → Cache Purge" permission and the zone ID. Every edited page is also cleared there.
- In "What weighs on the database" and "Memory and server", click Analyze. Leftovers of deleted content go with 1 click; tables of removed plugins and heavy plugins are only pointed out, with what to do.
Common problems
I turned on scripts on first interaction and the menu or chat is slow.
Test again: in "Scripts that wait for the first touch", set the menu or chat script to "Never wait". jQuery, Elementor, sliders and the cart already never wait.
Critical CSS did not make the site faster.
On pages built with Elementor the gain is small: Elementor's own CSS keeps loading first, on purpose, so the layout never breaks. The gain shows on theme posts and pages (in our test, the main image showed up 38% sooner).
Cloudflare says "Authentication error".
The token lacks the "Zone → Cache Purge" permission for that domain, or the zone ID is wrong. Create a custom token with only that permission and check the ID on the domain's Overview page.
The panel says the host limits memory.
Copy the ready-made text from the Memory and server card and send it to your host's support. The plugin never goes above the limit the host locks.
If something goes wrong
If something stops working after turning an optimization on, turn it off in the Speed screen (or use "Undo last change"). The memory adjustment in wp-config.php has its own Undo button. If even the dashboard won't open, see the Emergency exit page.
Didn't find the answer? Ask in the WordPress.org support forum.