Why Your Website Is Slow: A 10-Minute Diagnosis

Start with the score, not your gut feeling

Open PageSpeed Insights, paste your homepage URL, and wait for the report. Two numbers matter most: the mobile score and the Core Web Vitals section below it. Mobile first, because most visitors are on a phone, often on a mediocre connection, and Google ranks mobile speed separately from desktop.

Don’t panic over one weak score. Look at the three or four red items under “Opportunities” and “Diagnostics” — that list is your real to-do list for the next ten minutes.

Images: the usual biggest culprit

On most small-business sites, images account for more than half the page weight. A photo shot on a modern phone can weigh 4-6 MB straight out of the camera, and a browser will happily download all of it even if the photo is shown at 400 pixels wide.

Three quick checks:

• Are images saved as JPEG or PNG instead of WebP or AVIF? Modern formats are usually 30-50% smaller at the same visual quality.
• Is the file physically larger than the space it’s shown in? A 3000px-wide banner squeezed into a 600px slot wastes bandwidth for nothing.
• Do images below the fold load immediately, before anyone scrolls to them? They should be lazy-loaded instead.

When we rebuilt the product catalog for vareno.fun, a store shipping to 27 EU countries, converting catalog images to WebP and adding lazy loading cut the homepage weight roughly in half, with no visible quality loss.

Fonts: small file, big delay

Custom fonts are easy to add and easy to forget about. Each extra font weight — regular, bold, italic, black — is a separate file the browser must fetch before it can show readable text. On a slow connection that means a blank or flickering screen.

Check how many font files your site loads and how many of those weights the design actually uses. Two or three weights across one or two families is usually enough for any site; six or seven is a sign nobody ever cleaned up.

Also check where the fonts come from. Pulling them from an external service on every page load adds an extra round trip before text can render. Hosting the font files on your own server usually removes that step entirely.

Scripts: the invisible weight

Analytics, chat widgets, ad pixels, review plugins — each is a separate script, and each often loads scripts of its own. A page can look light and still take five seconds to become interactive because a dozen third-party tags are running in the background.

In the diagnosis report, look at “Reduce JavaScript execution time” and the list of third-party domains being loaded. Ask honestly about each one: does anyone look at this data, does anyone use this widget, was it added for a campaign eighteen months ago and simply never removed.

Building the multilingual booking flow for veyamobile.tech, covering 6 languages and 150 mobile operators, we cut load time noticeably just by deferring analytics scripts until after the main page rendered. The visitor sees the page first; tracking loads a beat later without them noticing.

What to fix first

Not everything on the report deserves equal attention. A practical order:

1. Compress and resize the three or four heaviest images — usually the hero banner and product photos.
2. Turn on lazy loading for anything below the fold.
3. Cut font weights down to what the design actually uses.
4. Remove or defer scripts nobody has checked the data on in months.
5. Re-run the test and compare against the first score.

Most sites gain more from these five steps than from a framework switch or a server upgrade. On fluxrbot.com, a neuroblog with 98 articles and 14 embedded tools, the same approach — image compression plus trimming unused scripts — raised the mobile score without touching the content pipeline itself.

A ten-minute habit, not a one-time fix

Speed drifts back down on its own. A new hero photo, a new chat widget, a new font weight added “just for this one banner” — six months later the score has quietly slipped again.

Run the same PageSpeed check once a quarter, the way you’d check a car’s oil. It takes ten minutes and tells you exactly which three things to fix, in the order they matter.

If your last redesign left you with a slow homepage and no clear reason why, that ten-minute report usually points straight at the real cause — the rest is the kind of image, font and script cleanup we do as part of any site build.