In November 2026 we measured our own homepage and found it downloaded 4.4 MB on mobile. Nobody had broken it on purpose. Images and scripts had simply piled up over a few months. After image optimisation and some cleanup it came down to 1.25 MB.
That is the most common story I see: sites rarely get slow because of one big mistake, they get slow gradually. Here is how I approach it.
Why it matters
Visitors on a phone leave if nothing appears. Google uses Core Web Vitals as one of its page experience signals. And a slow page makes everything else you do, from ads to SEO, less effective.
The three metrics to watch
LCP (Largest Contentful Paint): when the main content becomes visible. Good: under 2.5 seconds.
INP (Interaction to Next Paint): how fast the page responds to a tap or click. Good: under 200 ms.
CLS (Cumulative Layout Shift): how much the layout jumps around while loading. Good: under 0.1.
Check your own site on PageSpeed Insights. Look at the real-user data at the top if your site has enough traffic, not only the lab score.
What usually slows a site down
1. Images. On most sites I look at, this is the biggest part of the page weight. Use WebP or AVIF, serve the right size for the screen, and lazy-load what is below the fold. This was most of our own improvement.
2. Too much JavaScript loading up front. Every library, slider and animation adds to what the phone has to download and run before the page is usable. Load what is needed for the first screen first, the rest later.
3. Third-party scripts. Tracking pixels, tag managers, chat widgets. Each one can cost noticeable time. We removed our chat widget completely, because almost nobody used it.
4. Plugins (on WordPress). Each active plugin can add its own CSS and JavaScript to every page. Remove what you do not use.
5. No caching. A page rebuilt for every visitor is slower than a cached one. On WordPress, a caching plugin is usually the quickest win.
6. Web fonts. Host them yourself, load only the weights you use, and use font-display: swap.
7. Weak hosting. Cheap shared hosting is fine for very small sites, but it often becomes the bottleneck as the site grows.
Where I would start
- Measure the homepage and two or three important subpages on mobile. Save the results.
- Fix the images.
- Remove scripts and plugins nobody needs.
- Turn on caching if you do not have it.
- Measure again with the same pages.
- Only then move on to deeper developer work.
And one habit that would have saved us a few months: whenever you add something new to the site, measure before and after.
What to ask your developer
If you are ordering a new website, ask for the mobile speed results of the important pages at handover, and ask what will keep it that way afterwards. A fast site at launch is easy. Keeping it fast after a year of additions is the real test.
If you want a quick check, send me your URL. Speed is part of every website we build.

