Why your website is slow
Three common causes and what you can fix yourself
When a page takes a long time to load, the first thought is usually that the server is weak. Usually it is not. The server sends out the files you gave it. Three things explain most slow sites and you can fix two of them yourself, without anyone touching code.
Measure before you fix anything
Open pagespeed.web.dev, paste in your site address and choose the mobile view. Three numbers matter.
LCP shows how long it takes before the largest thing on screen is in place. Under 2.5 seconds is good, over 4 seconds is bad. Total Blocking Time shows how long the page fails to respond to a tap. Under 200 milliseconds is good. CLS shows how much the content jumps around while the page loads. Under 0.1 is good.
Write all three down. Without a starting point you will not know later whether anything changed.
1. Images go out at their original size
This is by far the most common cause. A photo taken on a phone is about 4000 pixels wide and several megabytes heavy. On the page it is shown 800 pixels wide. The browser still downloads the whole file and only then shrinks it on screen.
Ten images like that easily make a twenty-megabyte home page. On a mobile network that means several seconds of white screen.
What to do
- Before uploading, resize the image to about twice the width of the slot it appears in. For an eight hundred pixel slot, 1600 pixels is enough.
- Save it as WebP. The same image is usually 30 to 50 percent smaller than a JPEG.
- Every image below the first screenful gets
loading="lazy". Then the browser only loads them when the visitor scrolls that far. - Every image needs
widthandheighton it, otherwise the page jumps while loading.
How to check
Open the page in Chrome, press F12, choose the Network tab and reload. Sort by the Size column. Anything over 300 kB needs a look.
2. Every feature has its own plugin
A WordPress site with twenty plugins loads CSS and JavaScript from twenty different authors. Each file is a separate request and most plugins load their code on every page, including pages where they are never used. The contact form plugin loads its files in a blog post too.
On top of that each plugin usually makes its own database query. A hundred queries for one page is not unusual.
What to do
- Open the plugin list. Switch off everything whose job you cannot name. If something breaks, switch it back on.
- Sliders, animation packs and icon sets are usually the heaviest. Ask what that element actually gives you.
- If you have several plugins doing the same job, for example two SEO plugins, keep one.
How to check
The same Network tab shows the request count along the bottom. Under 50 requests is good, over 100 is a lot.
3. The text waits for the font
Google fonts load from another domain. Until the font file arrives, the browser may show no text at all for up to three seconds. The visitor looks at an empty space even though the text is already there.
What to do
- Add
&display=swapto the font request. Then the browser shows the text immediately in a system font and swaps later. - Choose two fonts, not five. Each weight of each font is usually a separate file.
- If you can, host the font on your own domain. That removes a connection to a third-party server.
What does not help
A caching plugin on its own. A good cache makes the server respond faster, but the browser still has to download the same heavy images and scripts. A heavy page stays heavy.
A more expensive hosting plan. If the problem is a six megabyte image, a faster server simply sends that image out slightly faster.
A new design on top of the old content. If the images stay the same, so does the speed.
If you would rather not do this yourself
Send us your site address. We will review it and tell you what is genuinely slow and what is merely old. The review is free and written, and we also tell you what you can fix yourself.
Want someone to look this over on your own site?
Send us the link. We will review it and tell you what can be fixed right away.
Get a review →