Start with the automatic baseline
WP Rocket applies automatic features and default settings when enabled. Before changing advanced options, test representative pages and record a baseline in PageSpeed Insights or another repeatable test.
This makes it easier to identify whether a later change actually helped and which setting caused a regression.
Recommended optimization sequence
WP Rocket's current guidance highlights Remove Unused CSS, deferred JavaScript, Delay JavaScript Execution, LazyLoad, missing image dimensions, font preloading, self-hosted Google Fonts, preload links, and optional CDN configuration as additional optimizations.
Enable features in small groups rather than switching everything on at once.
- File Optimization: CSS first, then JavaScript
- Media: LazyLoad and image-dimension settings
- Preload: links and cache-related options
- CDN: configure only when you actually use one
- Database: back up before cleanup
See the current product details and offer directly from WP Rocket.
View WP Rocket →Test for breakage
Aggressive CSS and JavaScript changes can affect menus, sliders, forms, checkout behavior, consent tools, and above-the-fold rendering. Test logged-out pages on mobile and desktop and verify ecommerce flows before leaving changes live.
Settings are not universal
There is no single “best WP Rocket settings” profile for every site. Theme code, plugins, ad scripts, analytics, consent tools, and hosting all change the result. Use the settings as a controlled experiment, not a magic preset.