Plugin how-tos · Guide
How to Configure WP Rocket for Core Web Vitals
Short answer
To configure WP Rocket for Core Web Vitals, turn on page caching and preloading, then enable Remove Unused CSS, Load JavaScript deferred, LazyLoad and Add missing image dimensions. Add Delay JavaScript execution last, one change at a time, and check each page in PageSpeed Insights after every change. Aim for LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
Key takeaways
- Good Core Web Vitals targets are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less at the 75th percentile.
- WP Rocket turns on page caching and preloading when you activate it, so most of the setup is in the File Optimization and Media tabs.
- Remove Unused CSS and Delay JavaScript execution give the largest gains and cause the most breakage, so turn each on alone and check your pages.
- Add missing image dimensions and LazyLoad protect CLS, but never lazy-load the hero image that sets LCP.
- WP Rocket Single costs $59.95 per year for 1 website as of November 2026, with the same features on every plan.
What are Core Web Vitals and what scores should you aim for?
Core Web Vitals are 3 metrics that measure loading, interactivity and visual stability, and the good targets are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
The 3 metrics are Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). Web.dev defines them as the subset of Web Vitals that apply to all web pages and appear across Google tools.
LCP measures loading speed. It reports the render time of the largest image, text block or video visible in the viewport, and web.dev says a good LCP is 2.5 seconds or less, while a poor LCP is greater than 4.0 seconds.
INP measures interactivity, or how fast a page responds when a visitor clicks, taps or types. CLS measures visual stability, or how much page content moves while it loads.
A page passes when it meets all 3 targets at the 75th percentile of page loads, split by mobile and desktop. That means 3 out of 4 real visits must hit the target, not just one fast lab run.
What do you need before you configure WP Rocket?
You need a live WordPress site, an active WP Rocket licence, a backup, and a baseline PageSpeed Insights report for your slowest pages.
WP Rocket is a premium-only plugin sold on its own site, with no free version. Single costs $59.95 per year for 1 website as of November 2026, Plus costs $119.95 per year for 3 websites, and Multi costs $299.95 per year for 50 websites.
Every plan includes the same features, according to WP Rocket pricing.
Take a backup before you change performance settings. File Optimization changes can hide menus, break sliders and stop forms, and a backup lets you undo a change in minutes.
Run PageSpeed Insights on your home page and your 2 or 3 slowest pages first, and save the LCP, INP and CLS numbers. Use PageSpeed Insights for the lab numbers, and check Search Console later for the field numbers from real visitors.
Check your hosting first if LCP is slow because the server is slow. WP Rocket cannot fix a weak server, so read the WordPress hosting requirements before you spend time on plugin settings.
Allow 30 to 60 minutes for the full setup, plus time to check pages after each risky change. The safe settings take about 10 minutes, while Remove Unused CSS and Delay JavaScript execution need the rest of the time for checking.
How do you turn on page caching and preloading in WP Rocket?
Page caching and preloading are already on when you activate WP Rocket, so your first job is to confirm they work and then clear and preload the cache.
Page caching saves each page as an HTML file, so WordPress does not run PHP and database queries for every visit. WP Rocket's own docs say page caching is activated automatically by default.
Preload visits your pages in the background and builds those cache files before a real visitor arrives. WP Rocket's docs list preloading among the settings to leave on, and preload runs again each time the cache is cleared.
Follow these steps:
- Go to Settings, then WP Rocket, and open the Dashboard tab.
- Click Clear and preload cache in the top admin bar or on the dashboard.
- Wait for the preload to finish, then visit your home page in a private browser window.
- Open the page source and look for the WP Rocket footer comment that confirms the page came from cache.
If your host already caches pages, WP Rocket's cache folder may stay empty. That is a host conflict, not a WP Rocket fault, and the comparison in WP Rocket vs host caching explains which layer should do the work.
How do you fix a slow LCP with WP Rocket?
Fix a slow LCP by cutting server time with cache and preload, then making the largest element load first and keeping it out of LazyLoad.
Find your LCP element first in PageSpeed Insights. It is often a hero image, a large heading block or a video poster image, and the fix depends on which one it is.
Use this table to match each cause to a WP Rocket setting.
| LCP cause | WP Rocket setting | Where to find it |
|---|---|---|
| Slow server response | Page caching and preload | Dashboard, on by default |
| Large hero image | LazyLoad off for that image, preload fonts | Media tab, Image and Media |
| Render-blocking CSS | Optimize CSS delivery, Remove Unused CSS | File Optimization tab |
| Render-blocking JavaScript | Load JavaScript deferred | File Optimization tab |
| Slow fonts | Preload fonts, Self-host Google Fonts | Media tab, Fonts |
WP Rocket detects the LCP image and keeps it out of LazyLoad on its own in current versions. If PageSpeed Insights still lists the hero image under lazy loading, exclude that image file by name in the Media tab.
Preload fonts helps when text is the LCP element and a web font holds it back. WP Rocket's docs list Preload fonts and Self-host Google Fonts among the Media settings to turn on, and both reduce the wait for above-the-fold text.
A content delivery network helps visitors far from your server. RocketCDN is WP Rocket's own add-on, and its free plan covers up to 3 pages with 10 points of presence and unlimited bandwidth, according to WP Rocket docs.
How do you remove render-blocking CSS and JavaScript?
Turn on Optimize CSS delivery with Remove Unused CSS, and turn on Load JavaScript deferred, in the File Optimization tab.
Render-blocking files are CSS and JavaScript that the browser must process before it can show content. They delay LCP, so removing them from the first paint is one of the largest wins in WP Rocket.
For CSS, go to Settings, then WP Rocket, then File Optimization, and turn on Optimize CSS delivery. Choose Remove Unused CSS, which keeps only the CSS each page uses and puts it inline, instead of loading full stylesheets first.
For JavaScript, turn on Load JavaScript deferred in the same tab. WP Rocket's docs say this adds the defer attribute and a data-rocket-defer attribute to JavaScript files, so the browser renders the page first and loads scripts later, as described in WP Rocket docs.
Turn on Minify CSS files and Minify JavaScript files too. Minification removes spaces and comments from files, which makes them smaller without changing what they do.
Turn on one CSS change and one JavaScript change at a time, then save and check the page. If a style or script breaks, you will know which setting caused it.
How do you use Delay JavaScript execution without breaking your site?
Turn on Delay JavaScript execution last, after the safer settings work, and use its One-click exclusions and Safe Mode when a widget, form or slider stops working.
Delay JavaScript execution holds back all JavaScript files and inline scripts until the visitor moves the mouse, touches the screen, scrolls or presses a key. WP Rocket's docs describe it as the most effective JavaScript optimisation it offers, and note that it applies only on cached or optimised pages.
It helps INP and the PageSpeed diagnostics for JavaScript execution time. WP Rocket's docs say PageSpeed warns when JavaScript execution takes more than 2 seconds and fails it when it takes longer than 3.5 seconds, so delaying heavy scripts can move a page under those limits.
Follow these steps:
- Go to Settings, then WP Rocket, then File Optimization.
- Turn on Delay JavaScript execution and save.
- Clear and preload the cache.
- Check every interactive page: menus, sliders, popups, forms, carts and chat widgets.
- If something stays blank until you scroll, open the One-click exclusions list and tick the plugin or service that owns it.
Safe Mode for Delay JavaScript Execution excludes inline scripts added with the WordPress wp_add_inline_script() function. Turn it on first if you want a gentler start, then turn it off later only if INP still needs help.
Note that Combine JavaScript files turns off when Delay JavaScript execution is on. That is by design, so scripts load in the correct order, according to WP Rocket docs.
How do you fix layout shift (CLS) with WP Rocket?
Turn on Add missing image dimensions and LazyLoad in the Media tab, and use Remove Unused CSS so above-the-fold content appears with its styles in place.
CLS happens when content moves after it first appears. Common causes are images without width and height, web fonts that swap late, and CSS that arrives after the text.
Add missing image dimensions tells the browser how much space to reserve for each image before it loads. WP Rocket's docs say it sets a static dimension for images, so no layout shift happens even if the images are lazy-loaded, as explained in WP Rocket docs.
Turn on LazyLoad for images, and for iframes and videos, in the Media tab. LazyLoad loads below-the-fold images only when the visitor scrolls near them, which cuts the first load and leaves space for the content above the fold.
Do not lazy-load images above the fold. WP Rocket's docs warn that LazyLoad on above-the-fold images without dimensions causes shift when the image finally loads, so exclude the logo and hero image if you see that warning.
Remove Unused CSS also helps CLS, because above-the-fold content gets its styles at once instead of waiting for a full stylesheet. If Remove Unused CSS cannot run on your site, WP Rocket's docs say to use Load CSS Asynchronously instead, though that can cause a brief flash of unstyled content.
How do you improve INP with WP Rocket?
Improve INP by delaying heavy JavaScript, deferring the rest, and removing plugins and scripts that add long tasks to the main thread.
INP is the time from a click, tap or key press to the next paint after the browser responds. Long JavaScript tasks block that response, so the page feels slow even when it looks loaded.
Delay JavaScript execution is the main WP Rocket tool for INP, because it keeps heavy scripts off the main thread until the visitor interacts. Load JavaScript deferred is the second tool, because it lets the page render before scripts run.
PageSpeed also flags files with more than 20KB of unused code under Reduce unused JavaScript. WP Rocket cannot delete that unused code, but Delay JavaScript execution can hold those files back until they are needed.
If you want the full definition and the 200 millisecond target in one place, read What is INP? before you chase the number.
A page builder can add a lot of JavaScript too, so check Elementor performance settings if your site uses Elementor.
Reduce the number of plugins that load JavaScript on every page. Each extra script adds work to the main thread, and no cache setting can remove work that the browser still has to do.
How do you check that your Core Web Vitals improved?
Run PageSpeed Insights on the same pages after each change, wait for Search Console field data, and compare the same 3 numbers each time.
PageSpeed Insights gives a lab score at once, which is useful right after a change. Run it on the same URL, on mobile first, because mobile scores are usually lower and mobile traffic is where the 75th percentile matters most.
Search Console gives field data from real visitors in its Core Web Vitals report. That data takes about 28 days to settle after a change, so do not expect the report to turn green the day you change a setting.
Check these items after each change:
- LCP is 2.5 seconds or less on mobile in PageSpeed Insights.
- INP is 200 milliseconds or less, or the lab proxy for it has fallen.
- CLS is 0.1 or less, with no shift listed in the diagnostics.
- Menus, sliders, forms and carts still work on desktop and mobile.
- No new console errors appear in Chrome DevTools.
If a score gets worse after one change, turn that change off and recheck. A single setting can help one metric and hurt another, and the field data in Search Console is the final judge.
What mistakes should you avoid?
Do not turn on every setting at once, do not lazy-load above-the-fold images, and do not judge the result from one lab run.
Turning on Remove Unused CSS and Delay JavaScript execution together is the most common mistake. When a page breaks, you cannot tell which setting caused it, so you end up turning both off and losing both gains.
Lazy-loading the hero image is the second mistake. It delays the LCP element itself, so LCP gets worse instead of better, even though the total page weight falls.
Leaving Delay JavaScript execution on without checking analytics, ads and chat widgets is the third mistake. Those scripts may load late or miss early visits, so exclude them with One-click exclusions if your reports show missing events.
Skipping the mobile check is the fourth mistake. A desktop score can pass while the mobile score fails, and the 75th percentile is measured separately for mobile and desktop, so always check mobile first.
Finally, do not add a second caching plugin or a second CSS and JavaScript optimiser on top of WP Rocket. Two tools that minify, defer or delay the same files will fight each other, and the fix is to pick one tool for each job.
Frequently asked questions
How long does it take to configure WP Rocket for Core Web Vitals?
Allow 30 to 60 minutes for a typical site. The safe settings take about 10 minutes, while Remove Unused CSS and Delay JavaScript execution need the rest of the time for checking menus, sliders, forms and carts on desktop and mobile after each change.
Should I turn on Remove Unused CSS and Delay JavaScript execution at the same time?
No. Turn on one at a time and check your pages after each change. Both settings give large gains and both can break layouts or interactive elements, so enabling them together makes it hard to tell which one caused a problem.
Will WP Rocket fix Core Web Vitals on slow hosting?
Only in part. WP Rocket cuts work on your site with caching, preloading and smaller files, but it cannot fix a slow server. If server response time is the main cause of a slow LCP, you need faster hosting or a better hosting plan first.
Why did my site break after I turned on Delay JavaScript execution?
A script that your page needs at once was held back until the first interaction. Use the One-click exclusions list for the plugin or service that owns it, or turn on Safe Mode, then clear the cache and check the page again.
How soon will Search Console show better Core Web Vitals?
Field data takes about 28 days to settle, because Search Console groups real visits over time. PageSpeed Insights shows lab results at once, which is useful for checking a change, but the Search Console report is the one that reflects real visitors.
Do I need RocketCDN as well as WP Rocket?
Not always. A CDN helps visitors who are far from your server, and RocketCDN is WP Rocket's own add-on for that job. If most visitors are near your server and LCP is already under 2.5 seconds, a CDN may add little, so check your scores first.
Sources
- Web Vitals web.dev
- Largest Contentful Paint (LCP) web.dev
- Delay JavaScript execution WP Rocket Knowledge Base
- Load JavaScript deferred WP Rocket Knowledge Base
- Cumulative Layout Shift WP Rocket Knowledge Base
- Find the best settings for your site WP Rocket Knowledge Base
- WP Rocket Pricing WP Rocket
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
