From 17+ years of hands-on engineering · 7 min read
What to Check When Your Website Is Slow
A slow website can lose enquiries and make every small task feel unreliable. The cause may be large images, the website code, the database, hosting capacity, an outside service or a combination of them. Testing in the right order prevents money being spent on changes that do not address the delay.
In this guide
Write down exactly what feels slow
A homepage that takes time to appear is different from a checkout button that waits after being pressed. One visitor on mobile data is different from every staff member seeing a slow dashboard. These details tell an engineer where to start.
Record the affected page, action, device, browser, location and approximate time. Note whether the problem is constant or occasional and whether signing in changes it. A short screen recording can be more useful than saying the whole site is slow.
Check the visible page weight
Large photographs, background video, many font files and third-party marketing scripts can delay what visitors see. Images should be supplied at sensible dimensions and modern formats. Scripts should earn their place rather than being added permanently after every campaign.
A speed report can identify large downloads, but the score is not the whole customer experience. Check the real page on an ordinary phone and connection, including the time until buttons and menus respond.
- Oversized images and video
- Too many font styles
- Advertising, chat and tracking scripts
- Visual effects that delay interaction
Separate browser delay from server delay
Sometimes the browser receives the page quickly but takes time to display it. In other cases the server waits before sending anything. Server delay may come from slow database queries, overloaded hosting, uncached work or an outside API that is not responding.
This distinction matters because moving hosts will not repair a large front-end download, and compressing images will not fix a slow database report. I measure both sides before recommending a solution.
Look for patterns in hosting and traffic
A website that slows only during campaigns or at a certain time may be reaching a hosting limit or running scheduled work. Sudden degradation can follow an update, a new plugin, unusual traffic or a failing external service. Logs and monitoring can confirm the timing.
Check available storage, memory, CPU and error records, but avoid changing several settings at once. One measured change is easier to judge and safer to reverse.
Fix the largest customer problem first
Speed work should begin with the pages and actions that matter to the business. A slow contact form or checkout deserves attention before an old article with little traffic. The first fix may be small even when the symptom feels serious.
After each change, repeat the same test and watch real usage. A good outcome is not only a higher score. Customers should see useful content sooner, complete actions reliably and encounter fewer errors.