EN
Webmail

Website Speed Findings in Site AI Audit: LCP, CLS and INP

Website Speed Findings in Site AI Audit: LCP, CLS and INP

When a Site AI Audit report arrives, the speed section is often the one that surprises owners most. The site feels fine on the office computer, yet the report lists website speed findings with unfamiliar abbreviations such as LCP, CLS and INP, and a score that seems low. This guide explains what each speed finding measures, why the figures come from a phone and not from your desk, which causes are behind the typical warnings, and how to decide what to fix first. It is based on how Site AI Audit, one of the products from the Internet Solutions team, describes its speed checks.

Site AI Audit looks at four vital signs of a website: SEO, speed, security and email. Each is shown with a score and findings ranked by impact. Here we concentrate on the second one and on how to read it as an owner rather than as a developer.

What the speed section checks

The speed part of an audit asks one question: how fast does the site feel on a phone? Google measures websites with real phones, and slow pages lose visitors and rankings. The report therefore concentrates on measurements that correspond to what a visitor experiences.

CheckWhat it tells youWhy it matters
Google PageSpeed scoreAn overall score for mobile speedA quick summary of how Google’s own tool sees the page
LCP (largest contentful paint)When the main content becomes visibleVisitors judge a page by when it looks ready
CLS (cumulative layout shift)How much the layout jumps while loadingJumping content causes mis-taps and irritation
INP (interaction to next paint)How quickly the page reacts to taps and clicksA page that looks ready but responds slowly feels broken
Server response timeHow long the server takes to start answeringSlow hosting delays everything that follows
Compression and page weightWhether files are compressed and how large the page isLarge pages cost time, especially on mobile networks

In the audit timeline the speed step runs after the crawl: Google PageSpeed measures mobile speed and the Core Web Vitals, and the figures arrive in the report together with the rest. The whole audit is designed to take one to two minutes.

Why the numbers come from a phone

Most office computers are fast and connected to fast networks. Many visitors are not. They use mid-range phones on mobile networks, sometimes with a weak signal. A page that loads in a second at your desk can take five seconds in a train station. The audit reports mobile figures for exactly this reason, and so should you when you judge the result.

Google has made some of these measurements part of how it evaluates the experience of a page. The details are explained on the Google page about Web Vitals, which describes the three Core Web Vitals and the thresholds that count as good.

Reading each finding in plain words

LCP: when does the main content appear?

Largest contentful paint marks the moment when the biggest visible element, usually a hero image, a large heading or a block of text, has been drawn. According to the guidance on largest contentful paint, a time of 2.5 seconds or less is considered good. The sample report on the Site AI Audit website shows how such a finding reads: the main content appears after 4.1 seconds on mobile, which counts as slow, with the suggestion to compress the hero image to a modern format and load it first.

The usual causes are easy to list:

  • A hero image that is much larger than the screen needs.
  • Images in old formats instead of WebP or similar modern formats.
  • Scripts or styles that block the page from drawing until they have loaded.
  • A slow server that makes the browser wait before anything starts.

CLS: why does the page jump?

Cumulative layout shift measures unexpected movement of content while the page loads. You have felt it when you tried to tap a button and an advert loaded above it, pushing it away. The guidance on cumulative layout shift treats a value of 0.1 or less as good. Typical causes are images without width and height, late-loading fonts, banners and cookie notices inserted above the content, and adverts without reserved space. The fix is almost always to reserve space in advance.

INP: does the page react quickly?

Interaction to next paint measures how long the page takes to respond after a tap, click or key press. A site can load quickly and still feel sluggish if heavy scripts keep the browser busy. Common causes are too many plugins, large third-party scripts such as chat widgets, trackers and social buttons, and complex page builders. The practical approach is to remove what you do not need and to delay what is not needed at the start.

Server response time: how long before anything happens?

Before any image or style can be loaded, the server must answer the first request. If that takes a long time, every other number suffers. The causes lie on the hosting side: an overloaded or small server, missing caching, slow database queries, or a heavy theme. This is where website owners most often need a specialist. Our server administration team tunes servers for such workloads.

Compression and page weight

Text files such as HTML, styles and scripts should be compressed before they are sent, which reduces their size by a large factor. Images should be sized for the place where they appear. If the audit reports a heavy page, look first at the biggest images, then at the number of scripts.

How to decide what to fix first

The report ranks findings by impact, which is a good start. Add your own judgment by asking three questions: how many pages are affected, how much improvement is possible, and how hard is the fix?

  1. Fix global causes first. A slow server or a heavy theme affects every page, so one improvement helps everywhere.
  2. Then fix the pages that matter most. The home page, main service pages and top landing pages deserve attention before old articles.
  3. Take cheap wins on the way. Compressing a few large images or enabling compression on the server takes minutes and often produces a visible change.
  4. Leave expensive perfection for last. Gaining the last fraction of a second may cost more than it returns.

For a broader view of what a team can influence, see our guide to website speed and Core Web Vitals.

A worked example

Imagine a small shop whose report shows a mobile score in the low sixties, an LCP of 4.1 seconds, a CLS of 0.18 and an INP in the warning range. The four findings share only a few root causes, so a short plan can address them.

FindingLikely causeActionEffort
LCP 4.1 secondsLarge uncompressed hero imageResize and convert to WebP, load it firstLow
CLS 0.18Images without dimensions, cookie banner above contentAdd width and height, reserve space for the bannerLow to medium
INP in warning rangeSeveral third-party scripts and a heavy page builderRemove unused plugins, delay non-essential scriptsMedium
Slow server responseNo caching on a shared serverEnable caching, review hostingMedium

After the changes, run the check again and compare. The paid plans of Site AI Audit include re-checks, so you can see whether the score moves and whether any change caused a new problem.

Common misunderstandings

  • “My site is fast for me.” Your device and network are not typical. Trust mobile measurements.
  • “A perfect score is the goal.” The goal is a site that feels fast to your visitors. A score is a guide, not a trophy.
  • “Speed is only a developer problem.” Many causes are content decisions: oversized photos, many embedded videos, too many widgets.
  • “The audit slowed down my site.” It does not. The crawler makes about three requests per second at most and follows your robots.txt rules, so it behaves like a polite visitor.
  • “Fixing speed will fix rankings.” Speed is one factor among many. It supports good rankings and conversions but does not replace relevant content.

Speed in the context of the other three areas

The report scores four areas, and speed rarely stands alone. Security findings, such as a missing redirect from HTTP to HTTPS, can add extra round trips and slow the first load. SEO findings, such as many redirects, add delays too. Email findings are unrelated to speed, but they belong in the same report because all four affect how a business appears online. For the full tour, read our article on how to read the score, findings and fix list.

When you want someone else to do the work

Not every owner wants to compress images or tune a server. Site AI Audit offers a “Fix it for me” button in the report, and the team behind it, Internet Solutions, has built and maintained websites, servers and email since 2011. We can send an estimate for the fixes. If your site needs a new base, for example a lighter theme and a properly configured hosting plan, our website development service covers design, development and hosting on our own servers.

A quick mobile test you can do yourself

Before or after an audit, try the site the way a visitor does. The test takes five minutes and teaches you more than a figure alone.

  1. Open the home page on a phone with Wi-Fi switched off, using the mobile connection.
  2. Count how long it takes before the main picture and heading appear. This is your own feeling for LCP.
  3. Scroll slowly and watch whether the content jumps. This is your own feeling for CLS.
  4. Tap a menu item and a button. Notice any delay before the page reacts. This is your own feeling for INP.
  5. Repeat on your main service or product page, not only on the home page.

You can also run Google’s own measurement for a single page in PageSpeed Insights. Compare it with the audit: if both point to the same problems, you have a reliable to-do list.

How often to measure

Speed is not a one-time achievement. Every new plugin, banner, tracking script or large photo can undo earlier work. A sensible rhythm is to run an audit after every significant change to the site, and at least once a quarter even if nothing seems to change. Keep the results in a simple table with the date, the score and the main figures. A downward trend is easier to explain and fix when you see it early, and a record of what changed on each date often points directly at the cause.

Frequently Asked Questions

What does the speed section of Site AI Audit check?

It reports the Google PageSpeed score for mobile, the Core Web Vitals LCP, CLS and INP, server response time, and compression and page weight. Findings are ranked by impact and explained in plain words.

Why is the report based on mobile speed?

Google measures sites with real phones, and many visitors use mobile networks. A site that is fast on a desktop can still feel slow on a phone, so the mobile figures are the realistic ones.

What is a good LCP value?

Google’s guidance treats 2.5 seconds or less as good. If your report shows a higher value, check the largest image on the page, the server response time and any scripts that block drawing.

Will running the audit slow my website down?

No. The crawler makes about three requests per second at most and respects the rules in your robots.txt file. You also do not need to install anything, because the site is checked from the outside.

Can I re-check after making fixes?

Re-checks are part of the paid plans. The free account runs one check and shows the report locked, while a plan unlocks the full report and allows further checks.

Can you fix the problems for me?

Yes. The report has a “Fix it for me” button, and Internet Solutions will send you an estimate for the work.

The Bottom Line

The speed findings in a Site AI Audit report translate into a few simple questions: when does the main content appear, does the page jump, does it react quickly, and does the server answer fast. Read the numbers as mobile numbers, fix global causes before page-specific ones, take the cheap wins, and re-check to confirm the effect. If you prefer to leave the technical work to specialists, our team can take over the fixes, from image optimization to server tuning. Start with the audit, then decide with facts: you can reach us through the server administration page for the server side or the website development page for a new site.