Every website is fast in the office. That is where it was built, tested and approved, on a good connection with a good machine.
Your customer is somewhere else entirely, and the gap between those two experiences is where enquiries disappear without leaving any trace. Nothing in your analytics records the person whose page never finished loading, because they never became a session.
Mobile website performance is mostly the work of closing that gap, and it starts with testing somewhere other than your desk.
Mobile Website Performance: Why Slow Sites Lose Sales
Why mobile website performance is harder than desktop
Three compounding disadvantages.
- Slower processors. The same JavaScript takes considerably longer to parse and execute on a mid-range phone than on a laptop. This is felt as unresponsiveness rather than as loading delay.
- Variable networks. Mobile connections fluctuate in ways broadband does not, and coverage across a county like Gloucestershire is genuinely uneven between towns.
- Worse conditions. Outdoors, one-handed, in sunlight, interrupted. Patience is shorter and attention is contested.
None of these is visible from a desktop machine, which is why mobile problems persist for years in businesses that consider their website fine.
The five things that usually cause it
- Oversized images. Desktop-sized assets served to phones. Near-universal and the largest single win available.
- JavaScript. Frameworks and libraries doing work the page does not need, occupying the main thread and delaying responses to taps.
- Third-party scripts. Analytics, chat widgets, tag managers and embeds, each opening connections and executing code at moments you do not control.
- No caching strategy. Returning visitors re-download assets that have not changed, which is entirely avoidable with sensible headers.
- Autoplay video. The heaviest common default, usually replacing nothing the visitor wanted, and on a weak connection the difference between a page arriving and not.
Fixing it, in order
Images first: serve at display dimensions in modern formats, use responsive sources so phones receive smaller versions, lazy-load below the fold but never the hero.
Set explicit width and height on every image. This costs almost nothing and fixes most of the content-jumping that causes mis-taps.
Audit third-party scripts, listing every external domain and finding an owner for each. The unclaimed ones are free to remove.
Then caching, then JavaScript, which takes the most effort and comes last.
Re-measure after each change under the same conditions so you can attribute the improvement.
Forms deserve separate attention
Mobile forms fail in ways desktop forms do not.
Set correct input types so the right keyboard appears. Enable autofill. Keep fields to what routes the enquiry, since every field is harder to complete on a phone.
Validate inline rather than on submission, because a reload on a mobile connection loses entries and loses people.
The repeat visit is not the visit that matters
Most performance work gets validated on a second load, because whoever is testing has already opened the page several times.
By then the images are cached, the fonts are stored, and the scripts are parsed. The site feels quick, and the problem appears solved.
Your customer arriving from a search result has none of that. They get the full download on whatever connection they happen to have, which is the slowest experience your site offers and the one that decides whether they stay.
Test with the cache disabled every time. It is a single checkbox in the network panel, and it is the difference between measuring your own familiarity and measuring what a stranger encounters.
Test properly
A real mid-range device on mobile data, not a desktop browser window made narrow. The narrow window keeps your office connection and desktop processor and hides both problems.
Check field data in Search Console, which reports real visits rather than a simulation. Pay particular attention to Interaction to Next Paint, which is the metric most likely to look fine in testing and fail in reality.
The web.dev guidance on Core Web Vitals covers current thresholds.
Where mobile website performance and environmental impact both apply, treat them as the same lever: reducing unnecessary data transfer and processing supports a faster experience while lowering estimated digital carbon, though environmental figures remain modelled rather than directly measured.
Our sustainable web development work is tested on real devices, because that is the only test that reflects your customers.