Why is my site slow on mobile?

Usually because of photos that are too large and too many scripts that have to load first. Google considers a page good if the largest element is on screen within 2.5 seconds.1 Smaller photos in a modern format and scripts that load later often save you the most time.

5 min read
Updated 7 October 2026

When does your visitor see the page?

example, simulated
0 s3 s6 s Without fixeslarge photo, scripts first
2.5 sHTMLscriptsmain photo, large JPEG
0.0 s With fixesWebP, scripts later
2.5 sHTMLmain photo, WebPscripts later
0.0 s
Simulated example of the same page on a mobile connection: the time until the largest element is on screen (LCP). Google considers 2.5 seconds or less good. Top: heavy scripts and a large photo first. Bottom: a smaller photo that gets priority.

When is a site slow?

Google measures page speed with three numbers, the Core Web Vitals. A page is good if it stays under these limits for 75 per cent of visits:1

MetricWhat it tells youGood
LCPHow quickly the largest element, often the main photo, is on screen2.5 s or faster
INPHow quickly the page responds when you tap something200 ms or faster
CLSHow much the page shifts while loading0.1 or less

Google uses the Core Web Vitals in its ranking, but relevance comes first: a slow page with the best answer can still rank at the top.2 Speed matters most for your visitor, who will not wait on a phone on the go.

What makes a site slow

These are the usual suspects, with the biggest gain at the top.

  1. Large photos

    A photo straight from the camera is often several megabytes. WebP photos are 25 to 34 per cent smaller than comparable JPEGs.3

    Typical when: there is a large image at the top of every page.

  2. One size for everything

    A phone gets the same large photo as a big screen. That wastes data, especially on a slow connection.4

    Typical when: the site does not offer different sizes per screen.

  3. Wrong lazy loading

    Photos further down may load later, but the main photo at the top should not.5

    Typical when: a plugin defers all photos by default.

  4. Too much JavaScript

    Downloading and running scripts takes the most time on a phone. According to Google's V8 team, it is wise to split up large bundles.6

    Typical when: there are many plugins, sliders, chat widgets and trackers.

  5. Shifting page

    Ads, cookie banners or photos without fixed dimensions push the content away while you read.

    Typical when: elements only take their place after loading.

Measure it yourself

  1. Open Google's PageSpeed Insights and enter your address. Look at the Mobile tab.
  2. Look at LCP first. If it is above 2.5 seconds, start with the main photo.
  3. Check the Core Web Vitals report in Search Console. It is based on real visitors.
  4. Run the free website check. It measures speed on a simulated mobile connection.

How Ekkora handles it

Speed is one of the eight checks before launch, measured with Lighthouse on a simulated mobile connection. For sites with 3D, we measure with the 3D object on the page, not without it. Read more in a website with 3D.

Questions

My site is fast on my laptop. Why do customers complain?
A laptop on wifi is much faster than a phone on 4G. So always test on mobile, or with PageSpeed Insights on the Mobile tab.
Does better hosting help?
Sometimes. If the server responds slowly, you can see it right at the start of loading. But usually the gain is in photos and scripts, not in the server.
Do I need a score of 100?
No. What matters more is that your real visitors stay under the Core Web Vitals limits. A score is a snapshot in a test.

How does your site score now?

You can run six of our eight checks on your own website for free. You get the result within half a minute, in plain language.