cursor
h a t t a n m e d a
Get a quote
  • Websites

Website speed for owners: Core Web Vitals in plain terms

Google grades your pages on three measurements taken from real visitors: how fast the main content appears, how fast the page reacts to a tap, and how much the layout jumps around. Those three are the Core Web Vitals.

Google uses them in ranking. Its own documentation also says relevant content comes first and that chasing a perfect score may not be worth your time.

The three metrics and what counts as good

Google's Web Vitals documentation defines the metrics and the "good" marks. Its PageSpeed Insights documentation gives the cut-offs for "poor".

MetricWhat it measuresGoodPoor
Largest Contentful Paint (LCP)Loading: when the largest piece of content appears2.5 seconds or lessOver 4 seconds
Interaction to Next Paint (INP)Responsiveness: how long the page takes to react to a click, tap or key press200 milliseconds or lessOver 500 milliseconds
Cumulative Layout Shift (CLS)Visual stability: how much the layout moves while you use the page0.1 or lessOver 0.25

A page passes when 75% of visits meet the "good" mark on each of the three. Google measures phones and desktops separately. We checked Google's pages on November 15, 2026, and these were the current metrics and thresholds.

INP replaced an older metric, First Input Delay, in March 2024. An article or report that still talks about FID is out of date.

How much speed affects your ranking

Less than you may have been told. Google's page experience documentation, last updated in September 2026, says "Core Web Vitals are used by our ranking systems."

The same page says good scores do not guarantee a top position. It says Google "always seeks to show the most relevant content, even if the page experience is sub-par", and that "trying to get a perfect score just for SEO reasons may not be the best use of your time."

Google also says where speed counts. For many searches there is plenty of helpful content to choose from, and a good page experience can contribute to success there.

Our reading: speed helps most when you and a competitor answer the search about equally well, and it will not lift a thin page over a useful one. The stronger reason to fix a slow site is the customer waiting on a phone. If search is your main concern, start with content and relevance.

How to check your own site

Google gives you two free tools.

PageSpeed Insights

Go to pagespeed.web.dev, paste in a page address and wait for the report. It shows two kinds of data, and they answer different questions.

  • Field data sits at the top. It comes from real Chrome users who visited the page over the previous 28 days. Google bases the Core Web Vitals pass or fail on it.
  • Lab data sits below. Google loads your page on a simulated mid-range phone and gives a performance score from 0 to 100, where 90 or above is good. Use the score to find problems.

The 0 to 100 score comes from a lab test. Your Core Web Vitals pass or fail comes from real visitors over the previous 28 days.

The score is not one of the Core Web Vitals. Google's documentation notes that a good lab result does not mean real visitors have a good experience.

A site with few visitors may have no field data for a page. PageSpeed Insights then shows figures for the whole site. If the whole site has too few visits as well, it shows no field data, and the lab test is all you have.

The Core Web Vitals report in Search Console

Search Console uses the same real-visitor data. Its Core Web Vitals report sorts groups of similar pages into Good, Need improvement and Poor, once for mobile and once for desktop.

A group takes the status of its worst metric, and the report leaves out pages without enough data. Use the report to see which page templates are in trouble, then test one example page in PageSpeed Insights.

What makes a small business site slow

Oversized images

The HTTP Archive's 2025 Web Almanac, published in January 2026, puts the median mobile home page at about 2.6 MB, with images the largest part at 911 KB. One in ten mobile home pages carries more than 6 MB of images. A photo uploaded at full camera size is the usual culprit.

Third-party scripts

Chat widgets, analytics tags, ad pixels, video embeds and social buttons each load code from someone else's server. Your page waits on that code, and a browser busy running scripts is slow to react to a tap.

Plugins and page builders

Google's guide to server response time says WordPress performance depends on the number and quality of plugins and on the theme.

The Web Almanac's chapter on content management systems found 45% of WordPress sites passing Core Web Vitals on mobile, against 74% for Wix, and says page builders often produce heavier pages. It also says the spread among WordPress sites comes from how each one is set up more than from WordPress itself. A lean WordPress site can pass.

Cheap hosting

Google's server response guide says shared hosting is generally slower and calls hosting the first thing to consider. PageSpeed Insights reports server response time as TTFB, short for time to first byte. A TTFB of 0.8 seconds or less is good.

What to fix first

Start with whichever metric fails in your field data.

  • LCP fails: look at the largest image at the top of the page, then at server response time.
  • INP fails: remove scripts, or have a developer delay the ones you keep.
  • CLS fails: look for images, ads and embeds that load without a reserved size and push the content down.

When nothing points elsewhere, begin with images. Resizing them costs almost nothing, and they are the heaviest part of the median page.

Changing host costs more. Rebuilding a page-builder site costs the most, so leave it until the cheaper fixes have failed.

We would not pay anyone for a promise of a 100 score. Google itself says chasing a perfect score for SEO may not be the best use of your time.

What to do this week

  1. Test your home page and your two busiest landing pages in PageSpeed Insights, using the mobile results. Record the three field numbers for each page, or note that there is no field data.
  2. Open the Core Web Vitals report in Search Console and list the page groups marked Poor.
  3. Find the biggest image on your home page. Resize it to the width it displays at, compress it and upload it again.
  4. List every plugin, widget and tracking tag on the site, and remove the ones nobody uses. For the security side of old plugins, see what a hacked WordPress site looks like.
  5. Check TTFB in the report. If it is over 0.8 seconds, ask your host what caching your plan includes and what a faster plan costs.
  6. Test again after each change. The lab score moves right away. Field data covers the previous 28 days, so it catches up over about a month.

HattanMedia builds WordPress sites and looks after them once they are live, with updates, backups and monitoring. If your numbers stay poor after these steps, see our WordPress development service or contact us.

All articles

More from the blog

Websites

Is your website ADA compliant? What the law says and what to check

No federal rule defines an ADA-compliant business website. What the DOJ says, what courts cite, and five checks you can run yourself.

Websites

Why a calculator on your website can beat another page of text

A small tool that answers your customer's "what will it cost" question often brings in more enquiries than a page of text. What to build, and how.

AI

AI chatbot on your website: when it pays off and when to skip it

A chatbot helps when your site already holds the answers and someone checks its work. What a tribunal and state laws say about wrong answers.