Short answer: The Speed and Core Web Vitals area of Site SEO AI Audit carries fifteen percent of the score. It combines Google PageSpeed data for mobile, including Largest Contentful Paint and layout shifts, with server checks on every page: response time, compression and page weight. Fix the server first with caching or better hosting, then compress images and scripts, set sizes for images and embeds, and re-check to see the score move.
Speed is one of the few SEO topics where the user and the search engine want exactly the same thing. A page that loads quickly keeps visitors, and Google has said for years that page experience counts in ranking. The difficulty is that speed has many causes, and tools tend to throw dozens of recommendations at you. The audit takes a different approach: six checks, each with a clear threshold, a severity and a fix, ranked by the points they could add to your score. This article explains what each one means and what to do first.
What the area measures
The home page of the product describes the area as Google PageSpeed, LCP and CLS, server response on every page, compression and page weight. The crawler reads every page it reaches, so it records the response time, the compression and the size of the HTML of each one. For the lab measurements of mobile speed, it uses Google PageSpeed, where the data is available. The result is a set of issues in the report:
| Check | Severity | Threshold |
|---|---|---|
| Mobile speed score below 50 | Kritik | PageSpeed mobile score under 50 |
| Largest Contentful Paint | Uyarı | Above 2.5 seconds |
| Layout shifts (CLS) | Uyarı | Above 0.1 |
| Slow server response | Uyarı | More than 0.8 seconds to start answering |
| No compression | Uyarı | Pages sent uncompressed |
| Heavy pages | Notice | HTML over 500 KB |
The critical issue weighs ten points before the share of pages is applied, the warnings four and the notice one. Together they make up the area score, which counts fifteen percent of the total.
Start with the server
Three of the checks concern the server, and they are usually the cheapest to fix because they affect every page at once. “Slow server response” means the server takes more than 0.8 seconds to start answering. The card advises enabling page caching or moving to faster hosting, and on WordPress, installing a caching plugin and checking your hosting plan. The explanation in the article on server response time shows what causes delays and how to find them.
“No compression” means pages are sent without gzip or Brotli, which can mean three to five times more data than necessary. This is a server setting, often a single line of configuration or a switch in the hosting panel. “Heavy pages” flags HTML over 500 KB. That is usually caused by inline data, long lists, page builders that add large amounts of markup or pagination that shows too many items at once. The guide to page weight and compression covers the fixes.
A quick way to see where you stand is to compare your report with the thresholds in the table. If the server response issue appears on most pages, you have a hosting or caching problem. If it appears on a few templates only, you have a slow query or a heavy plugin on those templates. If compression is missing, you have found the cheapest repair of all. The pattern of affected pages tells you whether to talk to your hosting provider, your developer or your content team.
Largest Contentful Paint
LCP is the time it takes for the largest visible element, usually a hero image or a large heading, to appear. The report warns when it exceeds 2.5 seconds on mobile. The usual causes are an oversized image, an image that loads late, render-blocking scripts and styles, and a slow server. The card’s advice is to load the hero image first and compress it, and to defer scripts. In practice, that means serving the image in a modern format at the right size, not lazy-loading the main image and delaying scripts that are not needed for the first screen. The LCP guide goes through the steps one by one.
Layout shifts
Cumulative Layout Shift measures how much the page jumps while it loads. You have felt it: you are about to tap a button and an advert loads above it, pushing the button down. The report warns when CLS exceeds 0.1. The fix is to reserve space. Set width and height on images, advertisements and embeds, so that the browser knows how much room to leave. Avoid inserting content above what is already on screen, and load web fonts in a way that does not move the text. The CLS guide explains the common patterns.
The mobile speed score
The critical check is “Mobile speed score below 50”. It reflects the overall PageSpeed score in the mobile test, which combines several measurements. A score under 50 means that real users on phones are likely to wait too long. The card’s advice is to compress images, use modern formats such as WebP, remove unused scripts and enable caching. On WordPress, use a caching plugin and an image optimiser. Do not chase a perfect score. Tools measure in a simulated environment, and the numbers vary from run to run, so treat them as a direction rather than an exact grade. The article on lab and field data in PageSpeed Insights explains why the numbers differ.
A worked example
A regional bakery chain has a WordPress site with 150 pages and a mobile speed score of 41. The report lists slow server response on every page, no compression, and a large hero image on the home page that delays LCP to 4.1 seconds. The developer enables page caching and compression in one afternoon. The next day, the home page hero is resized from 4,000 to 1,600 pixels wide and converted to WebP. The re-check shows a server response of 0.3 seconds, no compression issue, an LCP of 2.2 seconds and a mobile score in the sixties. The three fixes cost a few hours, and the Speed area score rose from the low forties to the high seventies.
A sensible order of work
- Server and compression. Caching, compression and hosting give the biggest gains for the least effort and help every page.
- Images. Resize, compress and convert the largest images, especially the first one on the page.
- Scripts and styles. Remove what you do not use, defer the rest, and review third-party scripts one by one.
- Layout stability. Set sizes for images, embeds and advertisement slots, and check fonts.
- Page weight. Trim heavy templates, shorten lists and simplify page builder layouts.
- Re-check. Starter, Pro and Agency include re-checks, which show how far the score moved.
For WordPress sites, the guide to caching plugins shows how to gain speed without creating SEO risks, such as caching pages that should not be cached.
Reading results with care
Speed results vary. The same page can score a few points higher or lower on two runs, because networks, servers and tools are not perfectly steady. When you compare checks, look at the direction and at the specific measurements, not at a single number. If the server response drops from 1.4 seconds to 0.4 after you enable caching, that is real progress, even if the overall mobile score shifts by a point either way. Compare like with like: do your re-check under similar conditions, and after caches have warmed up.
Why speed matters beyond ranking
It also pays to watch the weight of third-party scripts, since advertising, chat widgets, analytics and tag managers add requests that you do not control. Review them every few months: remove what nobody uses, load the rest after the first screen and check that each one still earns its place. A single forgotten script can slow every page of a site, and the report will show the effect as slow responses and a poor mobile score long before anyone remembers adding it.
Search is only one reason to care. Faster pages convert better, keep readers longer and cost less to serve. They also help automated visitors: AI crawlers and other bots read pages in bulk, and slow responses can lead them to read less of your site. If you want the wider picture, the guide to Core Web Vitals explains the three user-centred measurements and how Google uses them.
To see how your own site performs, create a free account and run your check. The free account runs one check and shows the report locked, and a plan from the pricing page unlocks every issue, the affected pages and the fixes.
Related reading
- Core Web Vitals Explained: LCP, INP and CLS in Plain Words
- Server Response Time and TTFB: How to Speed Up Your Server
- WordPress Caching Plugins: Speed Gains Without SEO Risks
The bottom line
The Speed and Core Web Vitals area rewards fast, stable pages. Fix server response and compression first, then images, scripts and layout shifts, and judge progress by the direction of repeated checks.
SSS
How much does speed weigh in the score?
Fifteen percent of the total, in the Speed and Core Web Vitals area.
What are the thresholds in the report?
LCP above 2.5 seconds, CLS above 0.1, server response above 0.8 seconds, mobile speed score below 50 and HTML over 500 KB.
Why does the score change between checks?
Speed tools measure in changing conditions. Look at the direction and at specific measurements, not at one number.
What is the quickest win?
Usually page caching and compression on the server, because they improve every page at once.
Does the audit check speed on every page?
The server checks, which are response time, compression and page size, cover every page. Mobile lab data comes from Google PageSpeed where available.


