Mobile website speed: Core Web Vitals explained simply
Why mobile speed matters, what LCP, INP and CLS measure with Google's official thresholds, how to test your website for free and how to fix the usual causes.
A fast mobile site keeps its visitors, converts better and starts with an advantage on Google, which includes the Core Web Vitals in its page experience assessment. These three metrics measure how quickly the main content appears (LCP, good at 2.5 seconds or less), how quickly the page responds to taps (INP, good at 200 milliseconds or less) and how stable the layout is (CLS, good at 0.1 or less). You can test your site in about 30 seconds with my free audit, which relies on Google's official tool.
Why does mobile website speed matter so much?
For your visitors
On a phone, people browse between two things: in a taxi, in a mall, on mobile data, sometimes with an older device. A blank page for several seconds, a button that does not respond, text that jumps just as you tap: each of these pushes people back to the results and on to the next competitor. In the UAE, where many people browse on their phone and compare several businesses before sending a WhatsApp message, that friction is costly.
For Google
Google indexes and evaluates sites primarily in their mobile version. Core Web Vitals are part of the page experience signals it takes into account. Google itself states that relevant content remains the priority: a fast but empty site will not outrank a more useful page. With comparable content, however, a good experience can make the difference.
For your sales and enquiries
A visitor who waits is a visitor who hesitates. Every contact form, every "Book" or "WhatsApp us" button must react instantly. A slow site costs enquiries you never see, because people leave before they write.
What are Core Web Vitals?
They are three metrics defined by Google to describe what a real visitor experiences.
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Time to display the largest visible element, often the main image or headline | 2.5 s or less | between 2.5 and 4 s | over 4 s |
| INP (Interaction to Next Paint) | Delay between an action (tap, click, typing) and the page's visible response | 200 ms or less | between 200 and 500 ms | over 500 ms |
| CLS (Cumulative Layout Shift) | Unexpected layout shifts while reading | 0.1 or less | between 0.1 and 0.25 | over 0.25 |
For a page to be rated "good", Google looks at the 75th percentile of real visits: at least three visits out of four must meet the threshold. INP replaced the older FID metric in March 2024; FID only measured the first interaction.
In plain terms:
- LCP: "do I quickly see what I came for?"
- INP: "when I tap a button, does something happen right away?"
- CLS: "does the page stay put, or does the text jump under my finger?"
How do I test my website speed on mobile?
With PageSpeed Insights
PageSpeed Insights (pagespeed.web.dev) is Google's free tool. Enter a page address and read two separate blocks:
- Real-user data (at the top, "Discover what your real users are experiencing"): it comes from real Chrome users' visits over the last 28 days. This is what counts for Google. A low-traffic site may not have any.
- Lab diagnostics (below, the score out of 100): a simulation on a mid-range phone with a throttled connection. It helps find causes and compare before and after a fix.
Test your homepage, but also your most visited pages: a service page or a blog post can be much slower than the homepage.
With the StrattonMB free audit
I built a free audit that queries Google's PageSpeed tool and adds 12 technical checks: HTTPS, title and description, mobile setup, structured data, image alt text, sitemap and more. Results arrive in about 30 seconds, with no sign-up. It is a good starting point to know whether speed is your real problem or whether there are others.
With your own phone
Open your site on your phone, on mobile data, off Wi-Fi. Time the display, open the menu, fill in the form, tap the WhatsApp button. This very simple test often reveals what customers actually experience.
Why is my website slow on mobile?
The causes I see most often, with their fix:
| Cause | Metric affected | Fix |
|---|---|---|
| Oversized images (multi-megabyte photos uploaded as they are) | LCP | Resize, compress, use WebP or AVIF, serve a size suited to the screen |
| Main image lazy-loaded | LCP | Load the top-of-page image with priority, lazy-load only images further down |
| Slow hosting or distant server | LCP | Quality hosting, caching, a CDN with servers close to your visitors |
| Too many plugins or third-party scripts (chat, pixels, widgets) | INP, LCP | Remove what is unused, load the rest after the page displays |
| Heavy page builder or theme | LCP, INP | Lighten the theme or rebuild key pages more simply |
| Images, videos or ads without reserved dimensions | CLS | Set width and height, reserve the space in advance |
| Cookie banner or popup that pushes content down | CLS | Show it as an overlay rather than inserting it |
| Many or heavy web fonts, including Arabic fonts | LCP, CLS | Limit the number of fonts, self-host them, include only the characters you need |
| Autoplay video at the top of the page | LCP | Replace it with an image and a play button |
Bilingual sites deserve a specific note: Arabic web fonts are often heavier than Latin ones. Load the Arabic font only on Arabic pages, and only the weights you use.
Where should I start to speed up my site?
Here is the order I follow, from the most rewarding to the most technical:
- Measure with PageSpeed Insights and note the three metrics on your main pages.
- Lighten images, especially the top one. It is often the most visible gain.
- Clean up plugins and scripts: every tool added "to try" often stays loaded on every page.
- Reserve space for images, videos and banners to stop layout jumps.
- Check hosting and enable caching.
- Measure again, then watch real-user data over the following weeks, since it updates gradually.
If your site runs on a very heavy theme or ageing technology, tweaks have limits. A redesign can then cost less than repeated patches; I cover this in my article on website redesign.
Mobile speed checklist
- Top-of-page image in WebP or AVIF, at a suitable size
- No multi-megabyte images
- Width and height set for images and videos
- Unused plugins and scripts removed
- Third-party tools (chat, analytics, pixels) loaded after display
- Two font families at most per language
- Cookie banner that does not shift content
- Caching and decent hosting
- Real test on a phone using mobile data
- LCP, INP and CLS green in PageSpeed Insights
Frequently asked questions
What PageSpeed score should I aim for?
The score out of 100 is a lab diagnostic, useful for progress. What counts for Google is Core Web Vitals measured on real visits. Aim for green on LCP, INP and CLS rather than a perfect score.
Why does my score change with every test?
Lab tests vary with server load, network and third-party scripts. Run several tests and look at the trend.
Can a WordPress site be fast?
Yes, with a light theme, few plugins, optimised images and good hosting. The problem rarely comes from WordPress alone, rather from everything added to it.
Is speed enough to rank well?
No. It adds to content, structure and reputation. A fast site that does not answer visitors' questions will not rank well.
Going further
Start by running the free audit on your site: you will know where you stand in half a minute. The sites I build are designed to be fast on mobile from day one; details are on the web and mobile development page. If the results raise questions, we can go through them together on a free discovery call.