Chykalophia Docs

The most common causes of a slow website, explained in plain English — from oversized images to slow hosting to too many plugins.

Most slow websites have the same handful of problems. Understanding what they are helps you have informed conversations with your web team — and sometimes fix things yourself. This guide ranks the culprits by how much they typically affect speed.

Quick summary

In our experience the usual culprits are unoptimized images, too many third-party scripts, poor-quality hosting, plugin bloat, and no caching. Most of these are fixable without rebuilding the site.

The most common causes, ranked by impact

1. Unoptimized images

This is the most common cause we see. A photo straight off a phone is often several megabytes. Your page might only display it at 400 pixels wide — but if the page links to the original file rather than a resized copy, every visitor downloads the whole thing.

The fix: compress and resize images before uploading, and serve them in modern formats. Google's own guidance is that formats like WebP and AVIF "may provide better compression than PNG or JPEG", so the file is smaller and takes less time to download.

See Images & page speed for a full guide.

2. Too many third-party scripts

Every time you add something to your site — a chat widget, a cookie consent popup, a Facebook pixel, a Google Tag Manager tag, a heatmap tool — you are adding a third-party script: one hosted on somebody else's domain. Each one makes an extra trip to an external server, and Google's documentation is blunt that these "can significantly affect your page load performance".

There is no magic number of scripts. What matters is how much work they make the browser do. Google's own yardstick for "too much" has been third-party code that ties up the browser for 250 milliseconds or more — one heavy script can cross that line while a dozen light ones do not.

The tricky part is that these scripts are often added by marketing teams or through integrations, and nobody keeps count. A test in PageSpeed Insights will show you which external services are loading and what each one costs you.

3. Slow or shared hosting

Your hosting is the server that stores and sends your website files. A cheap shared hosting plan puts your site on a server alongside many other sites, sharing its processor, memory and network capacity. When those sites get busy, yours can slow down too.

Hosting shows up in Time to First Byte — how long before the browser receives anything at all. Google's guidance is that most sites should aim for 0.8 seconds or less, and because TTFB comes before every other loading measurement, a slow server drags the rest down with it. Two otherwise identical sites can score very differently just because of hosting.

4. No caching

Caching means storing a ready-made copy of your page so it can be sent quickly without being rebuilt from scratch on every visit. Without caching, your server has to regenerate the page every time someone visits — even if nothing has changed.

WordPress's own performance documentation points people at caching first, on the basis that it gives "the biggest benefit for the smallest hassle". If your site has no caching, that is the quick win.

5. Too many plugins (WordPress)

Every active plugin runs code. Some plugins are lightweight and well-written. Others load large libraries of JavaScript and CSS even on pages where they are not used.

The number of plugins matters less than their quality. A handful of well-coded plugins can be lighter than two or three badly built ones. But plugin bloat is a real issue on many WordPress sites.

6. Render-blocking resources

Some CSS and JavaScript files must fully load before the browser can display anything. These are called "render-blocking" resources — in Google's speed test they are specifically stylesheets, and scripts in the page's head with no defer or async attribute. They make your page appear blank or slow to show content.

Fixing render-blocking resources is a developer task — it involves inlining the handful of styles needed for the first view and loading the rest later. If PageSpeed Insights flags render-blocking requests, it is worth discussing with us.

7. No CDN

A CDN (Content Delivery Network) stores copies of your site's files in data centers around the world. Without one, every visitor's request goes to a single server — potentially on the other side of the country (or world).

Read more in How a CDN speeds up your site.

8. Web fonts loaded inefficiently

Web fonts (like Google Fonts) add personality to your site — but they also require extra downloads. If they are not loaded carefully, they can delay when text appears or cause text to jump from one font to another.

9. Autoplay video

A video set to play automatically (especially in a background "hero" section) is a far larger download than the images around it, and it downloads whether the visitor cares about it or not. Even a well-compressed one adds real load time.

If you have autoplay video, make sure it is properly compressed. Google's guidance is to supply both WebM and MP4 versions: WebM files are much smaller, and MP4 is the fallback for browsers that do not support WebM.

10. Outdated software

WordPress releases regularly ship performance work. Version 6.9, for example, "includes a broad set of performance enhancements", among them a better Largest Contentful Paint. Plugin and theme authors do the same. Staying current is part of good site maintenance, and it is a security measure as well: WordPress's own hardening guide notes that attacks target old and outdated plugins and software.

Read more in Software updates explained.

How to find what is slowing your specific site

Run your page through PageSpeed Insights and read the list of suggestions below the scores. It names the specific problems on your specific pages, usually with an estimate of what fixing each one would save. Google renames and reorganises that part of the report from time to time, so read whatever list sits under the numbers rather than hunting for a particular heading.

Common questions

My site was fast when it launched. Why is it slow now?

Speed degrades over time as content is added, plugins accumulate, and scripts are added by marketing tools. A site that launched fast two years ago may now be carrying twice the weight. A periodic performance audit catches this.

Can I just install a speed plugin to fix everything?

Caching and optimization plugins (like WP Rocket or LiteSpeed Cache) make a real difference and are worth using. But they cannot fix everything — they cannot make a 10 MB image small, replace a slow hosting server, or remove scripts added by external tools. They work best as part of a broader approach.

Which of these should I fix first?

Start with images — usually the biggest gain and the easiest to fix. Then check your hosting. Then look at third-party scripts. PageSpeed Insights will rank the fixes for your specific site, so let it set the order if you are unsure.

Need a hand?

If you're stuck, email support@chykalophia.com and we'll help. Include your website address and a screenshot if you can.

What slows websites down