If Google Search Console has flagged your WordPress site for poor Core Web Vitals, you are not alone. Fewer than half of WordPress sites pass on mobile, and the reason is usually not the one people expect. Most site owners worry about JavaScript and clicks, but the data shows that most WordPress sites have a more basic problem. The main content takes too long to appear.
This guide explains what the three Core Web Vitals measure, how WordPress sites actually score, why a site can feel fast and still fail, and what fixes make the biggest difference. It is based on public data from the HTTP Archive and on the problems we see every week when we work on client sites.
What Core Web Vitals Measure
Core Web Vitals are three measurements Google uses to judge how a page feels to real visitors. Each one has a "good" limit, and Google looks at the experience of the slowest quarter of your visitors (the 75th percentile), not your best visit. That is why a page can load quickly for you on office Wi-Fi and still fail for people on mobile data.
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main content, usually a hero image or headline, appears | 2.5 seconds or less | Over 4 seconds |
| Interaction to Next Paint (INP) | How quickly the page reacts when someone taps or clicks | 200 ms or less | Over 500 ms |
| Cumulative Layout Shift (CLS) | How much the layout jumps around while loading | 0.1 or less | Over 0.25 |
INP replaced the older First Input Delay metric in March 2024, so any guide that still talks about FID is out of date. To pass, a page needs all three metrics in the "good" range.
How WordPress Sites Actually Score
The HTTP Archive tracks Core Web Vitals for millions of real websites using Chrome user data. Its Core Web Vitals Technology Report lets you compare platforms, and the WordPress numbers show a clear pattern. The figures below are for mobile visitors in August 2026.
| Mobile, August 2026 | WordPress sites | All websites |
|---|---|---|
| Pass all three Core Web Vitals | 48.7% | 53.0% |
| Good Largest Contentful Paint | 55.8% | 65.8% |
| Good First Contentful Paint | 43.6% | 58.2% |
| Good server response time (TTFB) | 23.5% | 45.8% |
Now compare that with the other two metrics. 90.8% of WordPress sites already have good INP and 87.2% have good CLS. In other words, most WordPress sites that fail are not failing because of clicks or jumping layouts. They fail because the server is slow to respond and the main content takes too long to appear.
The theme and page builder you use also play a big part. Sites built with the WordPress site editor pass at 63.7% on mobile, while sites built with Elementor pass at 36.8%. Builder sites tend to load more JavaScript too. The median Elementor site ships about 675 KB of it, compared with 374 KB for site editor sites.
| Built with (mobile, August 2026) | Pass rate |
|---|---|
| WordPress site editor (block themes) | 63.7% |
| Bricks | 55.7% |
| Beaver Builder | 54.0% |
| GeneratePress | 50.8% |
| Astra | 40.9% |
| Hello Elementor | 38.1% |
| Elementor | 36.8% |
These numbers are averages, so they do not decide the result for any single site. A well-built Elementor site can pass easily, and part of the gap comes from who builds with each tool. Still, the pattern is useful. A heavier theme or page builder means more work before a WordPress site passes.
Why Your Site Feels Fast but Still Fails
This is one of the most common questions in WordPress and SEO forums. Someone sees "poor URLs" in Search Console, their developer says "the site works fine on my phone", and nobody knows who is right. Usually both are right, because they are looking at different data.
Search Console and the top section of PageSpeed Insights show field data, which means real visits from Chrome users over the last 28 days, on all kinds of phones and connections. The score out of 100 lower down is lab data, which is one simulated test on one simulated phone. You can score 100 in the lab and still fail in the field, and the field data is what Google uses.
There are a few other reasons the numbers don't seem to add up. People ask about them often in forums, and each one can make you try to fix the wrong problem.
- "Not enough usage data". Smaller sites may not have enough Chrome visits for page-level results, so Google groups similar pages together or shows data for the whole site instead.
- Logged-in testing. When you test while logged in to WordPress, caching is often skipped and the admin bar loads, so your results look worse than what visitors get.
- Your own phone is not your visitors' phone. A new iPhone on fast Wi-Fi hides problems that visitors with a mid-range Android phone on mobile data notice immediately.
How to Fix LCP and Server Response Time
Since loading is where most WordPress sites fail, start here. LCP is made of two parts. The first is how long the server takes to send the page, and the second is how long the browser then takes to show the biggest element. With only 23.5% of WordPress sites having good server response time on mobile, the first part is often the bigger problem.
Page caching usually gives the biggest improvement. It lets the server send a ready-made page instead of building a new one for every visitor. After that, these are the fixes that usually matter most.
- Use proper hosting. Cheap shared hosting is the most common cause of slow server response we see. Moving a site to a faster host often fixes LCP without any other changes.
- Don't lazy-load the hero image. The main image at the top of the page should start loading immediately, with high priority. Lazy-loading it is one of the most common LCP mistakes.
- Replace sliders and video backgrounds above the fold. They are heavy and often make the LCP element load late.
- Serve smaller images. Use modern formats such as WebP or AVIF, at the size they are actually shown.
- Cut render-blocking files. Load only the CSS and fonts each page needs, and keep font files to a minimum.
- Use a CDN for visitors far from your server. It shortens the distance files travel.
Recent WordPress versions already help with some of this. Since WordPress 6.3, core adds high priority to the image most likely to be the LCP element and skips lazy loading for images near the top of the page. But themes, page builders and plugins can override this, so it is worth checking your own pages. Our comparison of WordPress caching plugins covers the caching side in more detail.
Failing Core Web Vitals on mobile? Our WordPress speed optimization service fixes LCP, INP and CLS without changing your design, and you get a before-and-after report.
Fixing INP and CLS
Most WordPress sites already pass these two, but when they fail, the cause is usually easy to find. INP problems almost always come from too much JavaScript running when someone taps the page. CLS problems come from things that appear late and push content around.
For INP, look at the scripts that run on every page, such as chat widgets, popups, heat-mapping tools, several analytics tags, and page builder add-ons you no longer use. Each one uses the browser's processing time when a visitor taps a menu or button. Removing one heavy third-party script often helps more than any setting in a performance plugin.
For CLS, open the page on a phone and watch it load, or check the layout shift section in PageSpeed Insights. The elements that move are usually one of these.
- Images and embeds without width and height set, so the browser doesn't know how much space to reserve.
- Cookie banners, notification bars or ads that push the page down after it has loaded.
- Web fonts that swap in and change the size of headings and menus.
How Long Before Google Sees the Change?
Many site owners do not expect this. Because field data covers the last 28 days, your Search Console report won't turn green the day after you fix something. Expect it to take about four weeks before the change fully shows up.
Once you have made the fixes, use the "Validate fix" button in the Core Web Vitals report. Google then tracks the affected pages for 28 days and tells you whether the issue is resolved. In the meantime, the lab score in PageSpeed Insights is a good way to check that your changes are working.
It is also important to understand how much speed matters for rankings. Core Web Vitals are part of Google's page experience signals, but Google has said clearly that a good page experience cannot replace useful content. A fast page with little useful information will not rank above a slower page that answers the question better. Speed helps most by stopping you from losing the visitors and rankings you already have.
Keeping Your Scores Green
Many sites that fix Core Web Vitals start failing again after some months. Someone adds a new plugin, uploads a large image or adds a marketing script for one campaign and never removes it. A year later, the site fails again and nobody knows why.
The solution is a simple routine. Check PageSpeed Insights for your key pages after every big change, review Search Console once a month, and remove plugins and scripts you no longer use. Our WordPress maintenance checklist includes these checks, and they are part of every WordPress maintenance plan we run, with a speed and Core Web Vitals tune-up built into the higher plans.
