On a desktop monitor everything feels fast; on a phone, over an ordinary connection, the same site takes so long that visitors hit back before the first image appears. That is almost never bad luck — it has a specific, findable cause. Here are the seven we hit most often, in the order worth checking them.

1. Images that are far too heavy

The most common cause by far. A photo taken with a phone camera is several megabytes; a mobile browser has to pull it over a weak connection before it can paint anything. A product or portfolio page often carries dozens of them at once.

Fix: resize images to the size actually displayed on the page, prefer modern compressed formats (WebP or AVIF) over plain JPEG, and add loading="lazy" to everything below the fold so it is not fetched during page open.

2. Too many fonts, loaded blocking

Every font is a separate file, and until it arrives the text either stays invisible or jumps. A site loading several families for headings, Latin and Persian text can spend whole seconds on fonts alone on a phone.

Fix: at most two font families, only the weights actually used, and font-display: swap so the text shows immediately. For Persian, light open-source faces like Vazirmatn are a sensible pick.

3. Third-party scripts

Analytics, support chat, social buttons, ads — each one comes from someone else’s server, and if that server is slow, everyone waits for it. A single heavy analytics tool can add seconds on its own.

Fix: list every third-party tool on the page and ask which ones are actually needed today. Remove the rest, and load what remains with defer or async so text and images get painted first.

4. Slow or oversold hosting

If the server takes a long time to start answering (TTFB), no amount of on-page optimization covers for it. Cheap shared hosting splits its resources among hundreds of sites; during busy hours your site waits in line.

Fix: measure the server response time (Google’s PageSpeed Insights, or any TTFB tool). If the answer is slow before anything else loads, upgrading or moving the host comes before any redesign.

5. Bloated themes and plugins

On WordPress, every plugin brings its own code, requests and settings. Sites that installed plugins for years usually carry dozens that no longer do anything.

Fix: go through the active list; anything you cannot identify, deactivate carefully and then remove. Keep the theme updated, and delete the trial themes left behind from experiments.

6. No caching

Without caching, every visit means the server does the work again and the browser downloads the same files again. On mobile, where the connection changes by the minute, that means an unstable experience.

Fix: give static files explicit browser cache lifetimes, and add a server-side cache or CDN if you can. When files are updated, change their versioned names so visitors are not stuck with old copies.

7. Uncompressed CSS and JS

Readable source is good for development; the shipped files should be minified. Comments, whitespace and dead code all survive into production otherwise.

Fix: your build tool (Vite, or your WordPress optimization plugin) should minify and bundle the output. Delete code that has not run in months.

How to measure

Without measurement, optimization is guesswork:

  • Google PageSpeed Insights — the mobile report, with a list of specific problems.
  • Chrome DevTools → Network, in mobile throttling mode — see exactly what downloads and how heavy it is.
  • This site: run the free site check on your own address — it runs in your browser and writes down whatever it is allowed to read.

Where to start

In our order — most effect, least cost first:

  1. Compress and downsize the images.
  2. Remove unnecessary third-party scripts.
  3. Turn caching on.
  4. Measure server response; move hosts if needed.
  5. Only then touch structure and theme.

If the site is still slow after all of that, the problem lives in the site’s structure itself — which is when you have to choose between repair and rebuild.