Why is my website slow to respond?
When you open a page, the first thing that happens is a wait: your browser asks the server for the page and the server has to build it and send it back. That wait is the server response time, and it sits in front of everything else on the page. Under half a second feels instant. Over a second, people notice. Over two, they start to leave.
Why it matters
Nothing can appear until the page itself arrives, so a slow response delays every image, every button and every word. Google measures it as Time to First Byte and it feeds directly into the Core Web Vitals scores used for ranking. It also compounds: a site that takes a second to answer takes a second on every page a visitor opens, so a five-page visit wastes five seconds of their patience.
What usually causes it
- Cheap shared hosting, where hundreds of sites compete for one server.
- A content management system rebuilding the whole page from the database on every visit.
- Too many plugins, each adding its own work to every request.
- A server on the other side of the world from your visitors.
- No caching, so nothing is ever reused.
How to check
Our free check measures how long your home page took to start arriving and reports it in milliseconds. For more detail, Google's PageSpeed Insights lists "Reduce initial server response time" when it is a problem.
How to fix it
Caching is nearly always the biggest win. It means the server keeps a ready-made copy of each page and hands it out instead of rebuilding it, which can turn a two-second response into a tenth of a second. On WordPress a caching plugin does this; good hosts do it at the server level too. After that, look at the host: moving from budget shared hosting to a decent managed host is often the single most effective change a small business can make. Finally, remove plugins you no longer use. Each one is code that runs on every visit.
Not sure how your own site does on this? Run the free check: it takes about twenty seconds and reports on this and thirty other things.