Guide · Website speed
Speed up your website: PageSpeed and Core Web Vitals explained in plain language.
A slow website costs your visitors’ patience and, in some cases, visibility on Google. This guide explains in plain terms what PageSpeed Insights tells you, what LCP, INP and CLS mean, which values Google rates as “good” and which slowdowns to tackle first.
- Google thresholds verified
- Lab vs. field data explained
- Slowdowns by priority
- Last updated: October 2026
Why loading time matters.
People who open a website usually want a quick answer: a phone number, an offer, an appointment. If the screen stays blank, content jumps while loading or a button only reacts after a pause, it feels unprofessional – and many visitors go back to the search results.
Google pays attention too: according to Google Search Central, Core Web Vitals are used by its ranking systems – but relevance comes first. A fast page with weak content will not overtake a slower one that answers the question better, and good values do not guarantee top positions. So speed is not a ranking trick, but part of a good first impression.
How to read PageSpeed Insights.
PageSpeed Insights is Google’s free measuring tool. It delivers two kinds of results that are often confused.
Field data comes from real Chrome users (the Chrome User Experience Report) and shows how fast your page actually was over the previous 28 days. What counts is the 75th percentile: three out of four page views must meet the threshold for a value to be rated “good”. The Core Web Vitals report in Google Search Console is based on this data as well.
Lab data comes from a simulated test with Google’s Lighthouse tool, in the mobile view with a throttled connection. It produces the performance score from 0 to 100: 90 and above is good, 50 to 89 needs improvement, below 50 is poor. Lab data helps with troubleshooting, but it does not show what your visitors really experience.
Two things often cause confusion: smaller websites frequently have no field data at all, because there are too few Chrome visits. And the score varies by a few points from test to test. So look at the trend and the mobile results rather than a single value.
The three Core Web Vitals – and what “good” means.
Google sums up the loading experience in three metrics. All three are measured at the 75th percentile, separately for mobile and desktop. The thresholds come from web.dev, Google’s developer platform (as of October 2026):
- LCP – Largest Contentful Paint (loading): When does the largest visible element appear, usually a header image or a large heading? Good: up to 2.5 seconds. Poor: over 4 seconds.
- INP – Interaction to Next Paint (responsiveness): How quickly does the page visibly react to a tap, a click or opening a menu – throughout the whole visit? Good: up to 200 milliseconds. Poor: over 500 milliseconds. INP replaced the older FID metric on 12 March 2024.
- CLS – Cumulative Layout Shift (stability): How much does content move while loading – like the button that slides away just as you tap it? Good: up to 0.1. Poor: over 0.25.
Anything in between needs improvement. Aim for all three in the green – especially on mobile.
The most common slowdowns – and how to fix them.
The causes are rarely exotic. They are listed in the order we usually tackle them: first whatever achieves a lot with little effort.
- 1. Images that are too large. Photos straight from a camera or smartphone are often many times larger than needed. Cropping, compressing and serving suitable sizes for different screens is often a big lever for LCP.
- 2. Missing modern image formats. At comparable quality, WebP and AVIF usually produce considerably smaller files than JPEG or PNG. Images further down should only load when needed (lazy loading) – but not the header image, which should appear right away.
- 3. Too many plugins and scripts. Every plugin, slider, chat widget and tracking tool adds code the browser must load and run, which mainly hurts responsiveness (INP). Remove what is unused and load the rest later.
- 4. Weak hosting. If the server is slow to respond, even good image optimisation only helps so much. Overloaded servers or outdated server software show up exactly here.
- 5. Web fonts. Many font styles from third-party servers delay text display and can cause layout shifts. Better: a few styles in WOFF2 format on your own server – usually also the cleaner choice under the GDPR.
- 6. Missing caching. Without caching, the server rebuilds every page on every request and the browser keeps re-downloading files. Page caching, sensible cache lifetimes for images, CSS and JavaScript and, if needed, a CDN speed up delivery.
Often overlooked: images, videos and embedded elements need fixed width and height values. The browser then reserves the space from the start and nothing jumps – an easy win for CLS.
What you can do yourself – and when a professional makes sense.
Some things you can tackle without coding knowledge:
- Test your home page, service pages and contact page with PageSpeed Insights and note the mobile values
- Resize new images before uploading and save them as WebP
- Remove plugins, widgets and tracking codes that nobody uses any more
- Keep your CMS, theme and plugins up to date
- Track real-visitor values in the Search Console Core Web Vitals report
It gets harder when the slowdown is built into the foundation: a heavy page builder, a theme full of unused code, scripts that block each other, or hosting that can no longer keep up. Plugins that promise to make “everything faster” then often achieve little. If the values do not move despite your efforts, an outside view is worth it.
Our portfolio shows that very good values are achievable: according to our case study, AAA HostPro reaches 100/100 on Google PageSpeed. How we make existing websites faster without rebuilding them straight away is explained under Website optimization. To see where your website stands today, start with the free website check.
Frequently asked questions.
Do I need a PageSpeed score of 100?
No. The score is a lab value and a helpful indicator, not a goal in itself. What matters more is that your Core Web Vitals are in the green for real visitors. Google considers 90 or above good – the last few points rarely make a noticeable difference to visitors.
Why does PageSpeed Insights show no field data for my website?
Field data comes from the Chrome User Experience Report and only appears once there are enough real Chrome visits. Smaller websites often do not reach that. Then go by the lab data and check later whether Search Console shows values.
Why is the score different every time I test?
Lab tests depend on server load, network and external scripts, which behave slightly differently every time. Variations of a few points are normal. Test several times and look at the trend.
Do Core Web Vitals affect my Google ranking?
Yes, Google uses them in its ranking systems. Relevance and helpful content take priority, though. Good values do not guarantee top positions – but slow pages risk visitors leaving before they see what you offer.
Do I need a new website to make it faster?
Usually not. Many slowdowns such as oversized images, unnecessary plugins or missing caching can be fixed on the existing website. A rebuild only pays off when the technology itself is the problem.
Want your website to be noticeably faster?
I will look at your website and tell you honestly where the slowdowns are and what can be improved with reasonable effort.
