Mobile page speed: what actually changes visibility and conversion

Most small-business sites are not slow because of the framework. They are slow because of three images and five scripts.

SHORT ANSWER

On mobile, three Core Web Vitals metrics decide perceived quality: LCP (largest element render time), INP (interaction responsiveness) and CLS (layout stability). The usual causes of poor scores are unoptimised images, blocking third-party scripts, and no reserved height for lazily loaded elements.

  • LCP measures how long the largest visible element takes to render.
  • INP measures how responsive the page is to user interaction.
  • CLS measures unexpected layout shifts during loading.
  • WebP images with explicit width and height remove most layout shifts.
  • Third-party scripts should load asynchronously or only after interaction.
Illustration: a speed gauge and page performance bars

The order of fixes matters

Start with images: correct format, responsive variants, explicit dimensions. Usually the cheapest fix and the biggest jump in LCP and CLS.

Then third-party scripts — chats, pixels, review widgets. Each sounds harmless until you add them all up on a phone with a weak signal.

Visual effects without the cost

Animation does not have to wreck scores if it runs on transform and opacity, respects prefers-reduced-motion, and is disabled on weaker hardware.

Rule of thumb: an effect nobody notices on a phone that eats 20% of the frame budget is a cost, not a feature.

Measure on a real phone

A score from a laptop on fibre tells you nothing. Test on a mid-range phone under the conditions your customers actually use — usually on the move, one-handed, with poor signal.

  • Performance
  • Local SEO

If part of your business still feels stuck in 2005, we should probably talk.

20 minutes. No pitch deck. We'll ask about your business, you'll ask us anything, and by the end of the call you'll know whether this makes sense for you.

(Worst case: 20 minutes of free advice. We can live with that.)

Email: hello@mocne.ai