Website speed

Website speed describes how quickly your pages become visible and usable after a click, in other words the loading time from your visitors' point of view. Google measures it with three Core Web Vitals: the largest visible element should appear within 2.5 seconds (LCP), the page should respond to clicks and input within 200 milliseconds (INP), and the layout should stay stable while loading (CLS of 0.1 or less).

What we see at publishers and on customer websites

When we assess publishers in our marketplace for customers, loading time does not come first. Topical fit, real organic traffic and rankings of their own matter more. That matches Google's own view: according to its documentation, Search always tries to show the most relevant content, even if the page experience is weaker. A fast page is the advantage that counts when several pages answer a question equally well.

A second finding from our own measurement: 55.1% of the publisher homepages we checked show traces of WordPress (based on 1,898 homepages with HTML from 2,087 active publisher domains, measured on 11 November 2026). More than every second site there runs on WordPress, and with WordPress a few levers do most of the work: page caching, correctly sized images, fewer plugins and fewer external scripts. The list further down is sorted accordingly.

And one lesson from our website analyses for customers: when we measured the same page three times with Lighthouse, the LCP value differed by several seconds between runs. A single test is a snapshot. Measure several times, take the middle value and above all look at data from real visitors.

Page speed, Core Web Vitals and PageSpeed Insights

• Page speed describes how quickly a single page becomes usable for visitors.
• Website speed is the umbrella term for everything that makes your site faster, from the server to the code and the images.
• Core Web Vitals are the three metrics Google uses to rate the loading experience: LCP for loading, INP for responsiveness and CLS for visual stability. INP replaced First Input Delay (FID) in March 2024.
• PageSpeed Insights is Google's free tool for measuring them. It shows field data from real Chrome users over the last 28 days, if the page has enough visitors, and lab data from a simulated Lighthouse test.

For users and rankings, the field data counts. A page is rated good when at least 75% of page views meet the thresholds. Values above 4 seconds for LCP, 500 milliseconds for INP and 0.25 for CLS count as poor, and anything in between needs improvement. The Core Web Vitals report in Google Search Console gives you the overview for all pages of your domain, also based on real visits.

Does website speed affect SEO?

Yes, but it is not decisive on its own. Google states that Core Web Vitals are used by its ranking systems and recommends good values. In the same place it also says that good values alone do not secure top rankings, and that page experience aspects beyond Core Web Vitals do not directly help a site rank higher (Google Search Central, page experience).

The bigger effect is on people. A fast page feels reliable, visitors reach the content without waiting and leave less often, especially on mobile networks. That pays off in everything that follows: enquiries, sales and recommendations. A fast, stable server also helps crawling, because the more reliably it responds, the more pages Google can fetch.

What slows a website down

• Server and hosting: how quickly the server sends its first response (time to first byte). Slow hosting holds back every page before the browser even starts.
• Images: usually the largest files. The big image at the top is often exactly the element LCP is measured on.
• JavaScript and CSS: files that block rendering delay the first impression, and a lot of JavaScript makes clicks sluggish and worsens INP.
• Third-party scripts: tracking, chat widgets, ads and embedded videos load from other servers and cost time.
• Elements without fixed dimensions: images, banners or fonts that claim space late make the layout jump and raise CLS.
• Redirects: each one costs an extra request before the actual page loads. Point internal links straight to the final address, as explained under URL structure.

How to improve website speed and Core Web Vitals

1. Turn on page caching: serve finished HTML pages instead of building them on every request. Many hosts offer this on the server, otherwise a caching plugin helps.
2. Deliver images properly: in the size they are displayed, as WebP or AVIF and with width and height set. Lazy-load images further down the page, but load the main image at the top immediately.
3. Clear out plugins and scripts: check for every plugin and external script whether you need it and whether it has to load on every page.
4. Load JavaScript later: add scripts that are not needed for the first view with defer or async, so they do not hold up rendering.
5. Use browser caching and compression: serve images, fonts and scripts with long cache lifetimes and compress text files.
6. Keep fonts lean: few weights, self-hosted and with font-display: swap so that text is readable straight away.
7. Serve close to your visitors: a data centre near your audience or a CDN helps when your visitors are spread across countries.
8. Measure mobile first: Google uses the mobile version of your pages for indexing and ranking, so test the smartphone view before the desktop one.

Conclusion

Website speed is the foundation that lets good content work. Measure with field data, fix the big brakes in hosting, images and scripts first and do not get lost chasing the last point of a lab score. Once the technology is in place, relevant content and recommendations from other websites do more than any further millisecond. How to earn those recommendations is covered under link building, and you can find suitable publishers in the Linkbroker marketplace.

Frequently asked questions

Is page speed a ranking factor?

Yes, Core Web Vitals are used by Google's ranking systems, but relevance and content quality weigh more. Good values alone do not secure top positions, while very slow pages lose visitors regardless of rankings.

How do I improve LCP?

Make the largest element at the top, usually an image or a heading, appear as early as possible: a fast server response, a correctly sized main image that is not lazy-loaded and is requested early, and no CSS or JavaScript that holds up rendering.

How do I improve INP?

Reduce the JavaScript that blocks the browser: split long script tasks and remove or delay unnecessary plugins and third-party scripts. It also helps to respond to a click visibly right away, for example with a loading state, and do the heavy work afterwards.

Why does my Lighthouse score differ from Search Console?

Lighthouse measures a single simulated test run, while Search Console summarises real visits over several weeks. Google's assessment is based on the real visits, and the lab test helps you find the causes.

Related terms: Indexing · SEO content · Off-page SEO · Duplicate content