Skip to content
MAXIMEJEAN.
All articles

PERFORMANCE

Your website is slow on mobile: what should you fix before rebuilding?

Images, videos, forms and useful metrics: how to prioritize mobile improvements without sacrificing design.

The customer’s experience matters

Open your website on a phone using an ordinary connection. Is the service understandable before the animations finish? Does the quote button stay in place? Can someone enter their contact details without zooming or losing what they typed?

These observations are a more useful starting point than chasing a perfect score. The goal is to keep what makes your business recognizable while reducing obstacles to a real inquiry.

Three metrics worth understanding

Core Web Vitals cover loading of the main content (LCP), responsiveness to interactions (INP) and visual stability (CLS). web.dev’s good thresholds are 2.5 seconds, 200 milliseconds and 0.1 respectively, assessed at the 75th percentile of visits.

A laboratory test and real-visitor data do not tell exactly the same story. A lightly visited site may lack field data. Use a test to find leads, then check the actual journey; do not present one result as every customer’s experience.

Look for unnecessary work

Start with images: does their size match where they appear? Then consider videos. A presentation film can have a place without immediately downloading every version. Elements lower on the page can often wait.

List widgets and scripts accumulated over time. Each tool should have a current purpose. Removing an unused tool may help; removing a feature customers use simply to gain points does not.

Improve without losing personality

Prepare two lists: essential elements to preserve and slowdowns to address. For each change, check appearance, interactions, forms and keyboard navigation. Also ask what happens when a video fails to load.

A useful upgrade produces a simpler, more reliable journey. Google notes that good Core Web Vitals do not guarantee a top position. A website must also answer the visitor’s need. Design, content and performance belong in the same conversation.

Sources and further reading

Sources checked September 11, 2026. Practical recommendations are our synthesis; platforms may change.