Website Suddenly Slow: What Usually Causes It and What You Can Check in Ten Minutes

A website that becomes slow overnight has usually hit one of three things: something on the site changed, the server ran out of resources, or a service the site depends on stopped answering quickly. Most of the evidence you need to tell these apart is in places you can already log in to, and you can collect it in about ten minutes without touching any code.

This guide is for an owner or manager whose developer is not available right now. If the site turns out to need engineering work, that is the kind of job covered by our web development and maintenance services.

What does it usually mean when a website suddenly becomes slow?

Sudden slowness means a specific event happened, and the fix is finding that event. Gradual slowness is different: a site gets a little heavier every month as images, plugins and data pile up, and it needs an optimization project. A sudden problem needs a timeline.

The events behind a sudden slowdown fall into seven groups:

• A traffic spike or bot traffic. A campaign, a press mention or an aggressive crawler sends more requests than the server can handle.
• A hosting resource limit. The plan's allowance for CPU, memory or connections is reached and requests start queuing.
• A new plugin, script or update. Something added or auto-updated recently does expensive work on every page.
• A failed cache. The layer that serves saved copies of pages stopped working, so every visit is rebuilt from scratch.
• A slow database. A table has outgrown its queries, or the database is short of memory or disk space.
• A third-party service timing out. A payment, chat, font or analytics service is slow, and your page waits for it.
• An attack. Someone is flooding the site, or a compromised site is spending its resources on something else.

What can I safely check in ten minutes?

You can check seven things without changing anything on the site. Write down what you see and when, because that record is what a developer will ask for first.

1. Is it slow for everyone? Open the site on your phone using mobile data instead of office Wi-Fi, then ask someone in another city or country to try. If it is slow on one network only, the problem is probably that network.
2. Read your host's status page. Hosts publish incidents there. Also check the status pages of your content delivery network and any payment or chat provider the site uses.
3. Look at the resource graphs in your hosting control panel. Find the charts for CPU, memory and connections. A line pinned at the top since the slowness began points to a traffic or resource-limit problem.
4. Check your email and billing page. Hosts usually warn you when an account hits a limit. Confirm that no invoice is overdue and the plan was not changed.
5. List what changed in the last few days. Plugin or theme updates, a new tracking tag, a product import, a mailing, a new integration. Automatic update notices count.
6. Run an outside measurement. Enter your homepage address into Google's PageSpeed Insights (pagespeed.web.dev) and save the result.
7. Log in to the admin area. Admin pages normally bypass the page cache. If the admin feels as it always did while public pages crawl, suspect the cache or a script on the public pages. If both are much slower than usual, suspect the server or the database.

How do I read a PageSpeed Insights result for a sudden slowdown?

Look at the lab test and treat the real-user section with caution. Google's documentation explains that PageSpeed Insights reports both lab and field data, and that the field data covers real users over the previous 28-day collection period. A problem that started yesterday is diluted across those 28 days and may barely show. The lab test is run fresh each time from outside your network, so it reflects the site as it is now.

The most useful number is how long the server takes to start answering. Google's web.dev guidance defines Time to First Byte as the time between starting to navigate to a page and the first byte of the response arriving, and treats 0.8 seconds or less as good and more than 1.8 seconds as poor (checked October 6, 2026). If the server takes several seconds to begin responding, the cause is on the server side: load, resource limits, cache or database. If it answers quickly but the page still takes long to finish, look at the page itself, typically a new script or a third-party service. Run the test twice, a few minutes apart.

What if I see an error instead of a slow page?

An error code narrows it down. MDN describes 503 Service Unavailable as the server not being ready to handle the request, with overload and maintenance as common causes. A 504 Gateway Timeout means a server acting as a gateway or proxy did not get a response in time from the server behind it. Take a screenshot showing the full message and the time.

What should I not do when my website is slow?

Do not change anything you cannot undo, and do not change several things at once. Each change made under pressure destroys evidence and can turn a slow site into a broken one.

Do not delete or deactivate plugins at random, restore a backup, edit configuration files, change DNS records, or run database repair tools. Do not restart the server repeatedly; a restart may hide the symptom for an hour while erasing the state a developer needed to see. Do not buy a bigger hosting plan before you know the cause, because more capacity does not fix a faulty script or a failing third-party service. Avoid refreshing the site constantly or running load-testing tools, which adds traffic to a server that is already struggling.

When should I call a developer, and what should I have ready?

Call a developer when the slowness affects everyone, persists, and your host's status page shows no incident that explains it. Call immediately if checkout or login is failing, if you see unfamiliar admin users or content, or if the traffic graphs show a flood you cannot account for. Anything involving code, the database, DNS or a backup restore belongs with them.

Have this ready:

• When the slowness started, with your time zone.
• Whether it affects every page, some pages, or only the admin area.
• Your list of recent changes, including automatic updates.
• Screenshots of the resource graphs and any error messages.
• The PageSpeed Insights results and the times you ran them.
• Emails from your host, plus working access to the hosting panel and site admin.

How do I stop my website slowing down again?

Most repeat incidents are prevented by knowing sooner and changing things more carefully. Set up uptime and response-time monitoring that alerts a person, so you hear about a slowdown from a tool and not from a customer. Keep a simple change log, and apply updates on a test copy of the site before the live one.

Ask your developer whether the hosting plan still fits the site's traffic and data; our guide to choosing cloud hosting for business applications covers what to compare. Review third-party scripts every few months and remove the ones nobody uses. If bots are a recurring cause, ask about rate limiting and a web application firewall.

Quick answers

Why is my website suddenly slow?

A website that is suddenly slow has usually had a specific event: a traffic or bot spike, a hosting resource limit being reached, a new plugin or script, a failed cache, a slow database, a third-party service timing out, or an attack. Finding what changed around the time it started is the fastest route to the cause.

How do I know if my website is slow for everyone or just me?

Open the site on a phone using mobile data instead of your usual Wi-Fi, and ask someone in another location to load it. If it is fast elsewhere, the problem is your network or device and not the website.

Does PageSpeed Insights show a slowdown that started today?

Only partly. The lab test in PageSpeed Insights is run fresh and reflects the site now, but the real-user field data covers the previous 28 days, so a slowdown that began today will hardly appear there.

Will upgrading my hosting plan fix a slow website?

Only if the cause is a resource limit. A larger plan does not fix a faulty plugin, a failed cache, an inefficient database query or a slow third-party service, so identify the cause before paying for more capacity.

Conclusion

A sudden slowdown is a timeline problem: work out when it started and what changed around then. Once you have run the checks above, leave the site as it is and pass the evidence to someone who can act on it.

If you have no developer available, you can contact Entrant Technologies and we will take a look.