Fix your website
Why is my website slow on phones?
Most slow business websites are slow for the same few reasons: photos uploaded at full size, too many scripts from themes, plugins, chat widgets and trackers, slow hosting, and fonts or styles that hold up the first paint. Test the page with Google PageSpeed Insights on the mobile setting, find the element it names as the Largest Contentful Paint, and fix whatever delays that element first.
Test it the way your customers see it
A page that feels quick on office fibre can feel very different on a mid-range phone using mobile data. Test the mobile version on purpose:
- Open PageSpeed Insights, enter the page address and read the Mobile tab.
- The top section shows real-visitor data from Chrome users, if Google has enough of it for your site. Many small business sites don’t, and that is normal.
- The performance score below it comes from a lab test that simulates a mobile device on a slower connection. Run it two or three times; lab results vary from run to run.
- Also try the page yourself on a phone using mobile data, not Wi-Fi.
| Metric | What it measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | How long the main content takes to appear | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds to taps and clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less |
The usual causes, and what to do
Work down this list. The first items usually make the biggest difference on small business websites.
Oversized images. Photos straight from a phone or camera are often several megabytes and thousands of pixels wide, then shown in a box a few hundred pixels across. Resize each image to the largest size it is displayed at, compress it, and use WebP where your platform allows. Let images further down the page load lazily, but never the main image at the top: it is often the Largest Contentful Paint.
Scripts you don’t need on every page. Chat widgets, social feeds, several tracking tags, sliders, pop-ups and booking widgets each add code the phone must download and run. Remove what nobody uses, and load the rest only on the pages that need it or when a visitor interacts.
From our own website: on 21 November 2026, PageSpeed Insights showed that the security check on our website form downloaded about 1.8 MB on our homepage before anyone touched the form, most of the page’s total weight. We changed it to load only when a visitor starts using the form.
Heavy themes, page builders and plugins. Multipurpose WordPress themes and page builders often load their styles and scripts on every page, whether used or not. Deactivate and delete plugins you don’t use, avoid stacking several plugins that do the same job, and replace a slider with one strong image.
Slow hosting. If PageSpeed Insights reports a slow server response time, the delay starts before your page even begins to load. Turn on page caching (most WordPress hosts provide it or allow a caching plugin), make sure your plan isn’t overloaded, and consider a content delivery network such as Cloudflare’s free plan for images and files.
Fonts and styles that block the first paint. Several font families and weights, loaded as large files, delay text appearing. Use one or two font families, WOFF2 files, and font-display: swap so text shows straight away. When we converted our own fonts from TTF to WOFF2, each file fell from 57 KB to about 12 KB.
Content that jumps. Images and embeds without set width and height push text down as they load, which raises layout shift. Give every image its dimensions.
Fix the biggest delay first
PageSpeed Insights lists its diagnostics with estimated savings. Start with the element it names as the Largest Contentful Paint and anything that delays it: a large hero image, a render-blocking stylesheet, a font, or a slow server response. Then work through unused JavaScript and image sizes. Retest after each change so you know which change helped.
Don’t chase 100. A business website that loads its main content quickly and responds to taps without delay serves customers well, even if a few lab audits remain.
When patching isn’t worth it
Sometimes every fix fights the platform: an old theme that can’t be updated, a page builder that wraps every element in layers of code, or a site built on plugins that no longer receive updates. If you would replace most of the site to make it fast, compare the cost of a rebuild with patching. See website redesign costs in Kenya.
What the Orvane scorecard checks
The website scorecard runs Google’s PageSpeed Insights mobile test on your homepage. It reports the score, Largest Contentful Paint, First Contentful Paint, Total Blocking Time, layout shift and Speed Index, and shows real-visitor Core Web Vitals when Google has them.
Mobile performance is 60% of the Speed and reliability area, or 15 of its 25 points. A lab score of 80 or more counts as passing. When it fails, the fix names the slowest element and the largest files we saw. Real-visitor data is shown for context and never replaces the lab score. See the methodology.
Common questions
Does website speed affect Google rankings?
Google says its ranking systems consider page experience, including Core Web Vitals, but that it always tries to show the most relevant content even if the page experience is poor. A fast page won’t rank for a service it never mentions. A relevant page is more likely to keep visitors if it loads quickly.
Why does my score change every time I test?
The lab test runs on Google’s servers under simulated conditions, and network timing, server load and third-party scripts vary between runs. Test two or three times and compare the metrics, not a single score.
My site is fast on my laptop. Why is the mobile score low?
The mobile test simulates a slower processor and a slower connection than a laptop on Wi-Fi. Many of your customers browse on phones, so the mobile result is the one to improve first.
Sources
- web.dev: Web Vitals, checked 21 November 2026
- web.dev: Optimize Largest Contentful Paint, checked 21 November 2026
- Google: About PageSpeed Insights, checked 21 November 2026
- Google Search Central: Understanding page experience in Google Search results, checked 21 November 2026