Why is my website so slow? What to check first
Your website feels slow, especially on phones? Learn how to test it like a customer, what the Core Web Vitals mean and which fixes come first.
If you are asking "why is my website so slow", the answer is rarely one thing. This guide shows you how to test your site the way a customer meets it, how to read the numbers that matter, and how to tell the usual causes apart. By the end you will know whether a clean-up is enough or whether a rebuild is the better path.
Why is my website so slow? Start by testing like a customer
Most opinions about speed come from the office computer. It has fast broadband, a big screen and a copy of your site already stored in the browser. Your customer is on a phone, on mobile data, often seeing the site for the first time.
Open your site on your phone with Wi-Fi switched off, in a private window. Count how long it takes before you can read the main text and tap a button. Do the same for two pages that matter, such as a service page and your contact page.
Then run the same pages through PageSpeed Insights, Google's free testing tool. Read the mobile result first. That is where the real problem usually shows.
What the main numbers mean
The report shows a lot of figures. Three of them, known together as Core Web Vitals, tell you most of what a business owner needs.
| What it measures | Name in the report | What your customer feels |
|---|---|---|
| How long until the main content appears | LCP | Staring at a blank page or a picture that never arrives |
| How quickly the page reacts to a tap | INP | Tapping the menu or a button and nothing happening |
| How much the layout jumps while loading | CLS | Aiming for one link and hitting another |
Each one is coloured green, orange or red. Green is fine, orange needs a look, red is something customers notice. The big score in the circle is only a summary, so do not chase it.
Below the numbers sits a list of suggestions. You do not need to fix all of them. Read the top three and note which files they name, because that tells you the cause.
The usual causes and how to tell them apart
A slow website almost always has several small problems stacked on top of each other. A site edited by several people over the years collects them without anyone noticing. Start with the cheapest fix and move down the list.
Oversized images
A photo straight from a phone is often many times larger than the page needs. If the report names large .jpg or .png files, start here. Resizing and compressing them changes nothing about the design.
Heavy themes and page builders
Many sites run on a bought theme and a drag-and-drop page builder. They are convenient, but they load a lot of code the page never uses. If the report talks about unused JavaScript or CSS, this is where it comes from.
Plugin pile-up
Every plugin added for a small feature can add files to every page. Some were installed by a past developer and no longer do anything. Switch them off one at a time and test again after each.
Third-party scripts
Chat widgets, ad tags, embedded maps, videos and tracking codes all load from other servers. If the report lists addresses that are not your own domain, look here first. Tracking that has been installed twice slows the page and doubles your numbers too.
Hosting
If even a simple page is slow, or the site slows down at certain times of day, the server may be the cause. The report shows it as a long server response time. Check it, but after the other causes, because better hosting does not shrink a heavy page.
Why speed costs you enquiries
A first-time visitor owes you nothing. If the page stays blank, they go back to the search results and tap the next one. You never find out they were there.
Google uses the same Core Web Vitals as part of how it assesses a page. Speed will not beat better content, but between two equally useful pages the faster one has an edge.
If you pay for ads, a slow landing page makes every click more expensive. You pay for a visit from someone who leaves before seeing your offer. That page is the first one to test.
A clean-up you can do this week
- Test three key pages on your phone, on mobile data, and note how long the main text takes to appear.
- Run the same pages through PageSpeed Insights and write down LCP, INP and CLS for mobile.
- Read the top three suggestions and list the files they name.
- Replace oversized images with resized, compressed versions.
- List every plugin and third-party script, and ask what each one does and who still uses it.
- Switch off what has no job, on a copy of the site if you can, and test after each change.
- If a simple page is still slow, ask your host for the server response time and the resources on your plan.
When a rebuild is the better path
A clean-up is enough when the problems are images, a few extra plugins and forgotten scripts. You fix them without touching the design, and the numbers move the same day.
A rebuild is worth weighing when the theme or page builder is the cause. Every new page inherits the same weight, and each fix tends to disappear after the next update. Over a few years, patching often costs more time than starting clean.
Decide on what a customer feels on a phone, not on the score in the circle. If the same problem keeps coming back after you fix it, that is your answer.
Frequently asked questions
How fast should my website load?
Aim for a green LCP on mobile in PageSpeed Insights. In practice, a customer should see the main text almost at once and be able to tap a button without waiting. If you find yourself counting seconds, it is too slow.
Why is my website fast for me but slow for customers?
Your computer has fast broadband and a stored copy of your site. Customers arrive for the first time, usually on a phone and on mobile data. Always test in a private window, on your phone, with Wi-Fi off.
Will better hosting fix a slow website?
Only if the server is the cause. If the problem is images, the theme or scripts, the site stays slow on any host. Check the server response time in the report before you pay for an upgrade.
Do I need a PageSpeed score of 100?
No. The score is a summary and moves between tests. What matters is green Core Web Vitals on mobile and a site that feels quick to a real customer.
The short version
Fix a slow site in order: test like a customer, read the three numbers, find the cause in the files the report names, and fix the cheap things first. Only then look at hosting or a rebuild. If you would rather the team ran the check for you, see what we offer.