You already know a slow site costs money and how to measure it. The detective question remains: who did it? Here is the lineup I meet again and again, ordered by frequency. Most slow sites suffer from three or four of these at once.

Suspect #1: giant images

The crime: you shot a photo on your phone and uploaded it as is. The image: 4,000 pixels wide, 5 megabytes. It displays at 400 pixels, but the visitor downloads all 5MB. Times five images per page.

How to catch it: in the PageSpeed report, look for “Properly size images” or “Serve images in next-gen formats”.

The sentence: compression and conversion to a modern format (WebP) before every upload - or a site that does it alone. On our builds, every image is converted and resized automatically for every screen size.

Suspect #2: plugin overload

The crime: on WordPress, every plugin may add its own code files that load on every page. That gallery you installed in 2021 and forgot? Still slowing every visit, including for people who will never see a gallery.

How to catch it: inventory. How many active plugins? How many actually used?

The sentence: delete (not just deactivate) everything non-essential. Quarterly.

Suspect #3: cheap hosting

The crime: at 10 shekels a month you share a server with hundreds of sites. When the neighbor launches a campaign, you get slow. Time to first byte (TTFB) is the telltale metric.

How to catch it: if even the simplest pages are slow, suspicion rises. In PageSpeed: “Reduce initial server response time”.

The sentence: upgrade to serious hosting - or, our preferred option, a static site on a global CDN, answering from the server nearest the visitor. Faster and cheaper.

Suspect #4: third-party scripts

The crime: a chat, a Facebook pixel, a Google map, an embedded YouTube video, a reviews widget. Each is “just one line of code”, and together they are half your load time.

How to catch it: PageSpeed’s “Reduce the impact of third-party code”, with names.

The sentence: keep only what produces measurable value, and load the rest deliberately late (after the page has appeared).

Suspect #5: heavy fonts

The crime: three different fonts, four weights each, loading from an external server. Text flickers or arrives late.

The sentence: one or two fonts, only the needed weights, hosted on your own site. (This site loads one locally-hosted Hebrew font - part of its perfect 100 score.)

Suspect #6: background video

The crime: an autoplaying background video on the homepage. Looks impressive in the designer’s demo, weighs tens of megabytes, and wrecks every mobile metric.

The sentence: a good static image with a play button. Or a very short, aggressively compressed clip that loads on desktop only.

Bottom line

Slowness is almost never a mystery: it’s the same six suspects, site after site. Run a PageSpeed test, identify yours in the Opportunities list, and start with the biggest (usually: images, hosting, plugins). And if the list is long and the patches keep multiplying, it’s time to ask whether the foundation itself is right: sometimes rebuilding on a fast base costs less than two years of fixes.

Want an honest diagnosis - patch the current site or rebuild it right? Send it over ↗