Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Explainer

How Fast Should a WordPress Site Load?

Short answer

A WordPress site should load its main content in 2.5 seconds or less for at least 75% of real visits, according to Google's Core Web Vitals targets as of November 2026. It should also respond to taps and clicks within 200 milliseconds and keep layout shifts at 0.1 or less. Check your real visitor data in PageSpeed Insights before you chase a single lab score.

Key takeaways

  • A good Largest Contentful Paint is 2.5 seconds or less, measured at the 75th percentile of real page loads.
  • A good Interaction to Next Paint is 200 milliseconds or less, and a good Cumulative Layout Shift is 0.1 or less.
  • Google judges each metric at the 75th percentile, so 3 in 4 visits must meet the target.
  • PageSpeed Insights field data covers real Chrome users over the previous 28 days, while its lab score comes from one simulated Lighthouse run.
  • A Lighthouse score of 90 or above is good, 50 to 89 needs improvement, and below 50 is poor.
  • A good Time to First Byte is 800 milliseconds or less, and a poor one is over 1,800 milliseconds.

How fast should a WordPress site load?

A WordPress site should show its main content in 2.5 seconds or less for at least 75% of real visits, as of November 2026.

That 2.5-second figure is Google's good threshold for Largest Contentful Paint, the metric that marks when the main content has likely loaded. Google's thresholds page lists the same target for every site, and WordPress sites are judged by it in the same way.

Speed is not one number. A page can show its headline fast and still feel slow when buttons ignore taps or text jumps as images load. That is why Google uses 3 metrics together, and why this guide covers all 3 before it covers fixes.

What do LCP, INP and CLS actually measure?

Largest Contentful Paint measures loading, Interaction to Next Paint measures responsiveness, and Cumulative Layout Shift measures visual stability.

Largest Contentful Paint, or LCP, reports when the largest image, text block, or video visible in the viewport finishes rendering. Google's thresholds page says LCP marks the point when the page's main content has likely loaded.

Interaction to Next Paint, or INP, looks at the delay after clicks, taps, and key presses across a whole visit. The INP guide on web.dev says a page with good responsiveness has an INP of 200 milliseconds or less. For a plain-language look at the metric, read what INP is.

Cumulative Layout Shift, or CLS, scores how much visible content moves without warning while a page loads. The CLS guide on web.dev says a good CLS score is 0.1 or less. A page passes only when all 3 metrics are good.

What counts as a good load time?

Good means LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, each at the 75th percentile of real visits.

The middle band is called needs improvement. PageSpeed Insights documentation gives the full bands, and the table below lists them.

MetricGoodNeeds improvementPoor
Largest Contentful Paint2.5 seconds or lessOver 2.5 to 4 secondsOver 4 seconds
Interaction to Next Paint200 ms or lessOver 200 to 500 msOver 500 ms
Cumulative Layout Shift0.1 or lessOver 0.1 to 0.25Over 0.25
First Contentful Paint1.8 seconds or lessOver 1.8 to 3 secondsOver 3 seconds
Time to First Byte800 ms or lessOver 800 ms to 1.8 secondsOver 1.8 seconds

First Contentful Paint marks when the first piece of content appears, and Time to First Byte marks how fast the server first answers. Time to First Byte is an experimental metric in PageSpeed Insights, not a Core Web Vital, but it still shapes LCP.

Why does Google use the 75th percentile?

Google uses the 75th percentile so that at least 3 in 4 visits meet the good threshold, which keeps a few slow visits from deciding the result.

An average hides your slowest visitors. A page with a fast average can still fail many real people on old phones or weak connections, so the 75th percentile looks at the slower end of real visits instead.

Google's thresholds page explains that the 75th percentile was picked to balance two aims. It should cover most visits, and it should not be pushed around by a small number of extreme outliers.

The same thresholds apply on mobile and desktop. Google's page notes that the thresholds are not split by device, even though phones usually find them harder to meet.

How do you check your site's real load time?

Open PageSpeed Insights, enter a page URL, and read the field data at the top before you look at the lab score below it.

Field data comes from the Chrome User Experience Report, known as CrUX. PageSpeed Insights documentation says it covers real users' experiences over the previous 28-day collection period.

Follow these steps for each key page:

  1. Open PageSpeed Insights and enter the full page URL.
  2. Read the mobile tab first, then the desktop tab.
  3. Note the Core Web Vitals assessment and the 75th percentile value for each metric.
  4. Compare each value with the good, needs improvement, and poor bands in the table above.
  5. Repeat the check for your home page, a popular post, and a shop or landing page.

New or low-traffic pages may have no field data. The same documentation says PageSpeed Insights then falls back to origin-level data for the whole site, and it shows nothing if the origin also lacks enough samples.

What is the difference between field data and lab data?

Field data shows what real visitors experienced over 28 days, while lab data shows one simulated Lighthouse load in a controlled setting.

Lab data is useful for debugging because it runs under fixed conditions. PageSpeed Insights documentation warns that lab data may not capture real-world bottlenecks, while field data has a smaller set of metrics.

The two can disagree, and that is normal. A page can pass its lab run and still fail in the field, or the reverse, because real visitors use many devices and networks.

FeatureField dataLab data
SourceChrome User Experience ReportLighthouse
PeriodPrevious 28 daysOne simulated load
Decides the Core Web Vitals assessmentYesNo
Best useJudging real visitor experienceFinding what to fix

Use field data to judge where you stand. Use lab data to find the cause, then re-run the lab test after each change to see if the cause moved.

What does the 0-100 Lighthouse score mean?

A Lighthouse score of 90 or above is good, 50 to 89 needs improvement, and below 50 is poor, as of November 2026.

The score comes from the lab half of PageSpeed Insights. PageSpeed Insights documentation says a green score of 90 or above is good, but it also notes that good lab data does not always mean real-user experiences are good.

The mobile lab run simulates a mid-tier Moto G4 phone on a mobile network. The desktop run uses an emulated desktop with a wired connection. That is one reason mobile scores often look much worse than desktop scores for the same page.

The score also varies from run to run. Google's documentation lists local network availability, client hardware, and resource contention as common sources of that variation, so run the test more than once before you act on a small change.

How much of a slow load comes from the server?

A slow server can use up the whole load budget before the page even starts, so check Time to First Byte first when LCP is slow on many pages.

Time to First Byte is the wait for the first byte of the HTML response. A good value is 800 milliseconds or less, and a poor value is over 1,800 milliseconds, according to the thresholds in PageSpeed Insights documentation.

WordPress builds most pages on each request unless a cache serves a saved copy. WordPress developer documentation says caching plugins store posts and pages as static files, which cuts the processing load on the server.

The same documentation says a persistent object cache saves trips to the database on every page view. Without one, the server must read site options from the database each time, which slows its response and can strain the database during traffic spikes.

If Time to First Byte is poor across many pages, test your hosting speed before you change themes or plugins. A fast theme cannot fix a server that answers slowly.

How fast should each part of a page load?

Each part has its own target, and the slowest part sets the pace for the whole page.

Start with the server, then the main image or text, then responsiveness. The list below gives the targets to aim for on each part.

  • Server response: Time to First Byte of 800 milliseconds or less.
  • First paint: First Contentful Paint of 1.8 seconds or less.
  • Main content: Largest Contentful Paint of 2.5 seconds or less.
  • Responsiveness: Interaction to Next Paint of 200 milliseconds or less.
  • Layout stability: Cumulative Layout Shift of 0.1 or less.
  • Blocking work: Total Blocking Time of 200 milliseconds or less on mobile.

Total Blocking Time adds up the blocking part of long tasks between First Contentful Paint and Time to Interactive. Chrome's Lighthouse documentation says any task over 50 milliseconds is a long task, and only the time past 50 milliseconds counts.

On mobile, Total Blocking Time of 0 to 200 milliseconds is green, 200 to 600 milliseconds is orange, and over 600 milliseconds is red.

On desktop the bands are 0 to 150, 150 to 350, and over 350 milliseconds. Heavy JavaScript is the usual cause, and Chrome's page names unneeded JavaScript and wasteful code as common sources of long tasks.

Does load speed affect search rankings?

Load speed is one of many ranking signals, and relevance still comes first, so speed alone will not rank a weak page.

Google counts Core Web Vitals as part of page experience, but it has said they are one aspect among many. A fast page with thin content will not outrank a slower page that answers the search better.

That said, the effect is real for visitors. A page that loads slowly can lose readers before they see the content, even if it still ranks. Speed work pays off in reader patience as well as in search.

For the ranking side in more detail, see whether page speed affects SEO.

What makes a WordPress site slow in the first place?

The usual causes are an uncached server, heavy images, too many plugins, and a heavy theme, and each one shows up in a different metric.

WordPress developer documentation lists the main factors as the hosting setup, WordPress settings, software versions, and the number and size of images. It also says a fast, light theme performs far better than a heavy, image-laden one.

Work through the causes in this order:

  1. Caching: serve saved pages instead of building each one from scratch.
  2. Images: use fewer images, pick the right format, and use WebP where it fits.
  3. Plugins: deactivate and delete the ones you do not need.
  4. Theme: switch to a lighter theme if the current one loads a lot of unused code.
  5. Software: keep WordPress, PHP, and the database current, since newer versions bring speed fixes.

WordPress developer documentation says caching gives the biggest benefit for the smallest hassle. It also says a cache can improve speed several hundred times over for fairly static pages.

To act on the fixes in order, follow how to speed up WordPress.

What mistakes should you avoid?

The most common mistake is chasing the lab score while ignoring the field data that Google actually uses.

Avoid these traps:

  • Judging a page by one lab run instead of 28 days of field data.
  • Treating a 90-plus lab score as proof that real visitors have a fast experience.
  • Comparing mobile and desktop scores as if they used the same test conditions.
  • Adding more plugins to fix speed, which usually adds more code to load.
  • Lazy-loading the main image, which delays the very element LCP measures.

A single change rarely fixes all 3 Core Web Vitals. Fix the metric that fails in field data first, re-check it after 28 days, and only then move to the next one. For a structured setup, see how to configure WP Rocket for Core Web Vitals.

Frequently asked questions

Is 2.5 seconds fast enough for a WordPress site?

Yes, 2.5 seconds or less for Largest Contentful Paint is Google's good threshold, measured at the 75th percentile of real visits. It means at least 3 in 4 visits show the main content that fast. Faster is still better, but 2.5 seconds is the target to pass, not a limit to stop at.

Should I aim for a load time under 1 second?

Under 1 second is a fine ambition for a simple page, but it is not Google's target and many real sites cannot reach it on mobile. Aim for the good thresholds first: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less. Then improve further only where the data shows a real gain.

Why is my site slow on mobile but fast on desktop?

Mobile tests use a slower simulated phone and a mobile network, while desktop tests use an emulated desktop with a wired connection. Real mobile visitors also have weaker devices and networks. Check the mobile field data first, since it reflects what most visitors actually experience.

How long does it take for a speed fix to show in field data?

Field data covers a rolling 28-day window, so a fix takes time to appear. The lab test changes at once, which lets you confirm the fix worked, but the field numbers move slowly as old visits leave the window. Wait for a full 28-day cycle before you judge the result.

Does a fast site need a CDN?

Not always, but a CDN helps when visitors are far from your server. It mirrors static files like images across regions so each visitor downloads them from nearby. If your visitors are mostly near your server, caching and image fixes usually matter more.

Sources

  1. How the Core Web Vitals metrics thresholds were defined web.dev
  2. About PageSpeed Insights Google for Developers
  3. Optimization WordPress Developer Resources
  4. Total Blocking Time Chrome for Developers
  5. Interaction to Next Paint (INP) web.dev
  6. Cumulative Layout Shift (CLS) web.dev

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.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test