Site SEO AI Auditod Internet Solutions

Speed Warnings in Detail: PageSpeed, Compression, Weight

22 listopada 2026Czas czytania: 8 minSEO techniczne
Speed Warnings in Detail: PageSpeed, Compression, Weight

Short answer: The Speed and Core Web Vitals area of Site SEO AI Audit has six findings. “Mobile speed score below 50” is critical. “Largest Contentful Paint above 2.5 s”, “Layout shifts (CLS above 0.1)”, “Slow server response” and “No compression” are warnings. “Heavy pages (HTML over 500 KB)” is a notice. Each has a short first fix: compress and prioritise images, set image sizes, turn on page caching, enable gzip or Brotli, and trim unused markup. Fix the cheapest ones first, then run a new check.

Speed is the area where a report can feel most technical, because the words are unfamiliar: paint, shift, response, compression. But the ideas are simple. A page should start answering quickly, show its main content soon, stay still while it loads and not carry more weight than it needs. Each finding in the report points to one of these ideas, and each has a first fix that does not require a developer in most cases. This article is a field guide to the six findings, in the order in which they are best tackled. For a summary of the area as a whole, read the speed and Core Web Vitals area. Here we go one level deeper.

How the audit measures speed

The audit uses two kinds of data. The first is Google PageSpeed for mobile, which gives a score, the Largest Contentful Paint and the Cumulative Layout Shift for the site. The second is measured by the crawler itself on every page: how long the server takes to start answering, whether the page is compressed and how large the HTML is. The area carries 15 percent of the total score. If PageSpeed data is not available for some reason, the area is scored only from the server response and page weight, so a missing PageSpeed result does not leave the area empty.

Finding Severity Trigger
Mobile speed score below 50 Krytyczny Google PageSpeed mobile score under 50
Largest Contentful Paint above 2.5 s Ostrzeżenie Main content appears after more than 2.5 seconds
Layout shifts (CLS above 0.1) Ostrzeżenie Layout shift score above 0.1
Slow server response Ostrzeżenie Server takes more than 0.8 seconds to start answering
No compression Ostrzeżenie Pages are sent uncompressed
Heavy pages Notice HTML larger than 500 KB

The mobile score, LCP and CLS come from the PageSpeed data for the site, and the compression check applies to the website as a whole. Slow server response and heavy pages are measured per page, so the report can list the affected pages for those two.

Start here: no compression

“No compression” is the cheapest speed fix there is. When a server sends pages uncompressed, visitors download three to five times more data than needed. Compression with gzip or Brotli is a server setting, switched on once and applied to every page. Many hosts offer it as a checkbox, and caching or speed plugins on WordPress often include it. After you enable it, open a page and look at the response headers: a content-encoding header with gzip or br shows that it works. The guide to page weight and compression explains the details.

Next: slow server response

“Slow server response” appears when the server takes more than 0.8 seconds to start answering on some pages. Everything else waits for that first byte, so a slow server hurts every other speed measure. Common causes are cheap shared hosting, pages built from the database at each visit, heavy plugins and no caching. The first fix in the report is to enable page caching or move to faster hosting. On WordPress, a caching plugin stores finished pages and serves them at once, which often cuts the response from seconds to milliseconds. The article on server response time and TTFB goes through the options, and the one about WordPress caching plugins warns about the risks.

Largest Contentful Paint: when the main content appears

Largest Contentful Paint measures how long it takes for the largest visible element, usually the main image or the headline block, to appear on a phone. The audit raises a warning when it is above 2.5 seconds. The usual culprit is a large hero image that loads late. The advice in the report is to load the hero image first, compress it and defer scripts. In practice, that means using a modern format such as WebP, sizing the image to the space it needs and avoiding a lazy loading rule on the first image. Fonts and heavy sliders also delay the paint, so check them as well. The explanation of Core Web Vitals shows how the measures fit together.

Layout shifts: why the page jumps

Cumulative Layout Shift measures how much the content moves while the page loads. A score above 0.1 triggers the warning. Everyone has met the effect: you are about to tap a button, an image loads above it and the button jumps away. The first fix is to reserve space: set the width and height on images, ads and embeds so that the browser knows how much room to leave. Late-loading fonts, banners that push content down and widgets that inject themselves after the page appears are the other frequent causes.

Mobile speed score below 50

This is the critical one. Google PageSpeed gives the site a mobile score from 0 to 100, and below 50 is poor. The score combines many things, so the finding is a summary rather than one cause. The advice is to compress images, remove unused scripts and enable caching, which together address the usual reasons. Third-party scripts for analytics, chat, ads and tag managers are a very common cause, and the article on third-party scripts and speed explains how to find the heavy ones. Work through the warnings above first, because fixing compression, server response, the hero image and layout shifts normally raises the mobile score as well. Read the guide to PageSpeed Insights, lab data and field data if the numbers in different tools disagree.

Heavy pages

The notice “Heavy pages (HTML over 500 KB)” is about the HTML document itself, not about images. A page whose HTML is larger than half a megabyte has usually inlined a lot of data: very long lists, inline styles and scripts, page-builder markup or full product catalogues in one page. The fix is to remove inline data, split long lists with pagination or loading on demand, and clean unused markup. This is a notice, because a few heavy pages are not a disaster, but a template that makes every page heavy slows the whole site, especially on mobile.

A sensible order of work

  1. Enable compression. One setting, every page benefits.
  2. Turn on page caching. Fixes slow responses on most content sites.
  3. Fix the hero image. Compress, resize and load it first.
  4. Reserve space. Add sizes to images and embeds to stop the shifts.
  5. Remove unneeded scripts. Test each third-party tag for its value.
  6. Trim heavy pages. Clean the templates that produce the largest HTML.
  7. Run a new check. Starter, Pro and Agency include re-checks. Compare the Speed area score and the PageSpeed numbers.

Speed also helps crawlers and people. Fast pages serve people first, but they help other readers too. Crawlers have limited time and patience, and slow servers can make them visit less often. The article on page speed and AI crawlers explains why speed matters for them as well. The audit crawls politely at about three requests per second, so a slow server will show up in the report without being harmed by the check.

Plans count checks per month, as the pricing page shows, so you can fix a group of speed problems, check, and then move to the next group. Speed data can also vary from one run to the next, so judge the trend over two or three checks rather than a single number.

How to read a repeat check

Speed results are the most variable part of a report. A shared server may be busy during one check and quiet during the next, and the PageSpeed service itself can return slightly different numbers for the same page. That does not mean the audit is unreliable. It means that you should look at the direction and at the size of changes. If compression was off and is now on, the finding should disappear completely. If the server response improved after you enabled caching, the number of slow pages should drop sharply. If the mobile score moves by a few points up or down without any change on your side, treat it as noise.

A useful habit is to write down the three numbers that matter before you start: the Speed area score, the mobile score and the number of pages with a slow response. After each batch of fixes, compare them. The Earlier reports menu in My websites keeps the old reports at hand, and Pro adds a comparison between audits that shows what is new, what was fixed and what got worse. Together they turn speed work from guessing into a series of small, measurable steps.

Related reading

The bottom line

Six findings describe speed in the report. Switch on compression, add caching, fix the main image, reserve space for images and embeds, remove scripts you do not need and trim heavy pages, then run a new check and compare the Speed area score.

FAQ

Why does my PageSpeed score differ between tools?

Different tools use different devices, networks and data. The audit uses Google PageSpeed for mobile, and results can vary a little between runs.

Which speed fix gives the most for the least work?

Usually compression and page caching. Both are settings or plugins that apply to every page at once.

Does a mobile score below 50 hurt rankings?

The report explains that Google uses page experience in ranking and that slow pages lose visitors. It is a critical finding for that reason.

Are heavy pages about images?

No. The finding is about the HTML document itself being larger than 500 KB, often because of inline data, long lists or builder markup.

Which plan lists the pages with slow responses?

Any paid plan shows the affected pages. A free account runs one check and shows the report locked.

#Core Web Vitals#Page speed#SEO audit#WordPress SEO
Sprawdź własną witrynę.Czy Google widzi Twoją stronę?
Rozpocznij audyt
Internet Solutions

Więcej od naszego zespołu

Stworzone przez Internet Solutions. Wypróbuj nasze pozostałe produkty — każdy oszczędza czas na swój sposób.

internet-solutions.net ↗