In this guide · 8 sections
Core Web Vitals in plain English
Core Web Vitals are Google's three measures of how a page feels to a real visitor. The targets below are from Google's web.dev guide to Web Vitals:
| Metric | What it measures | Good score | What it feels like when it fails |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How quickly the main content, usually the hero image or headline, appears | 2.5 seconds or less | A blank or half-loaded page on mobile data |
| INP (Interaction to Next Paint) | How quickly the page responds when someone taps or clicks | 200 milliseconds or less | Buttons and menus that lag or seem broken |
| CLS (Cumulative Layout Shift) | How much the layout moves while loading | 0.1 or less | You go to tap a button and it jumps away |
Google assesses these at the 75th percentile of real page loads, on mobile and desktop separately. In practice that means your site has to be fast for most visitors on ordinary phones and networks, not just on your office Wi-Fi.
How to test your site (free)
- Go to PageSpeed Insights (pagespeed.web.dev) and enter your home page address. Then test your most important pages too: a service page, a product page, the contact page.
- Look first at the field data section ("Discover what your real users are experiencing"). This is real visitor data from Chrome users. If your site has too little traffic, you will only see the lab test.
- Read the lab test below it. It runs one simulated load on a mid-range phone and lists specific problems, such as "Properly size images" or "Reduce unused JavaScript".
- In Google Search Console, open the Core Web Vitals report to see which groups of pages are failing over time. If you have not set up Search Console yet, do it now; it is free.
- Write down the scores before you change anything, so you can prove the fixes worked.
Don't chase a perfect 100 in the lab score. Passing the three Core Web Vitals in field data, and a page that feels fast on your own phone over 4G, matter far more than the number.
The usual causes, and the fix for each
On small business websites, almost all slowness comes from a short list of causes:
| Cause | Metric it hurts | Fix |
|---|---|---|
| Huge photos uploaded straight from a camera or phone | LCP | Resize to the size actually displayed, compress, and use WebP or AVIF where the platform supports it |
| Hero slider or background video at the top | LCP | Replace with one compressed image; load video only on demand |
| Too many plugins (WordPress) or apps (Shopify) | LCP, INP | Remove anything unused; each one can add scripts to every page |
| Chat widgets, pop-ups, trackers and review widgets | INP, LCP | Keep only those you use; load them after the page or on interaction |
| Images and embeds without set dimensions | CLS | Give images, videos and ad slots a fixed width and height |
| Web fonts loading late | CLS, LCP | Use fewer font weights, host them locally, preload the main one |
| Slow or overloaded hosting | LCP | Turn on caching and a CDN; move hosts if the server itself is slow |
| Heavy page builder theme | All three | Use a lighter theme, or rebuild key pages with simpler layouts |
A fix order that works
Work from the cheapest, safest change to the most involved, and test after each step:
- Back up the site (or duplicate the Shopify theme) before touching anything.
- Fix images: resize, compress and convert the biggest ones, starting with whatever appears at the top of the home page.
- Lazy-load images further down the page, but never the main image at the top, which should load straight away.
- Remove what you don't use: plugins, apps, old tracking codes, unused fonts and sliders.
- Turn on caching and a CDN where your platform allows it (most WordPress hosts offer both; Shopify and Wix include a CDN).
- Tame third-party scripts: delay chat, pop-ups and trackers until after the page has loaded or until the visitor interacts.
- Fix layout shifts: set dimensions on images and embeds, and reserve space for banners.
- Re-test the same pages in PageSpeed Insights and compare with your notes. Field data in Search Console takes a few weeks to update.
Platform notes: WordPress, Shopify and Wix
WordPress
You control the most and can break the most. A good caching plugin, image compression, and removing page-builder bloat usually give the biggest wins. Check your hosting plan as well: cheap shared hosting can be the real bottleneck. Keep everything updated afterwards, since speed plugins need updates too.
Shopify
Shopify handles hosting and the CDN. Slowness usually comes from the theme and apps. Uninstalling an app may leave its code in your theme files, so check the theme after removing apps. Test a copy of a newer, lighter theme if yours is several years old.
Wix
Hosting is fixed, so focus on what you put on the page: fewer animations, compressed images, fewer embedded widgets and shorter pages.
Does speed affect your Google ranking?
Yes, but it is one factor among many. Google's Core Web Vitals documentation says it highly recommends good Core Web Vitals for success in Search, and that they align with what its core ranking systems seek to reward. It also says, in its page experience guidance, that Search always seeks to show the most relevant content, even if the page experience is sub-par; a great page experience helps most when lots of helpful content is competing for the same search.
For a small business the bigger effect is often on customers. A visitor on mobile data who waits for a slow page may simply go back to the search results and call a competitor. Speed fixes usually pay off in enquiries before they show up in rankings.
If your site is fast but still not showing on Google, the cause is more likely technical SEO: missing page titles, pages blocked from indexing, no sitemap, or a site that was recently moved without redirects. Our website migration checklist covers the redirect side.
Do it yourself or get help?
Image compression and removing unused plugins or apps are well within reach for most owners, and they fix a large share of problems. Theme code, caching rules and script loading are where it is easy to break checkout or forms.
Our Speed & SEO Fix (S$390, 3 days) includes a before and after PageSpeed report, image compression and lazy loading, caching and script clean-up, fixes to titles and headings, and Search Console with a sitemap. To keep it fast after that, the Care plan (S$129/month) covers monthly updates, daily backups and up to an hour of small changes. You can also run a free domain check to look at HTTPS and email set-up at the same time.
Frequently asked questions
Google's targets are Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of real page loads.
Phones have slower processors and often slower connections, and PageSpeed Insights tests mobile on a simulated mid-range phone. Large images, heavy themes and third-party scripts hurt far more on mobile.
No. The lab score is a diagnostic tool. Aim to pass the three Core Web Vitals in real user data and for the site to feel fast on an ordinary phone. A score in the 90s is great but not required.
It can help, since Google says good Core Web Vitals align with what its ranking systems reward, but relevance and useful content matter more. The more immediate gain is fewer visitors leaving before the page loads.
PageSpeed Insights lab results change straight away. Field data in Search Console is based on real visits over a rolling period, so expect a few weeks before the report reflects your fixes.