Why is my website slow the first time I open it?

The first time you open your website after a while, it takes ages — ten, twenty, thirty seconds of blank screen or spinner. Open it again and it's instant. If that's the pattern, your site probably isn't slow. It was asleep, and you caught it waking up.

This one specific symptom — slow the first time, fast every time after — has one common cause, and it's not a bug you introduced.

Your host put it to sleep

Many hosting plans, especially free ones, save resources by pausing an app that hasn't had visitors for a while. When the next person shows up, the host has to start it back up before it can answer — and that startup, called a cold start, is the wait you're seeing. Once it's running, everyone gets the fast version until it goes quiet again.

Which hosts do this

If your site or its database is on a free or hobby plan, this is likely the culprit. The big ones each have their own version and their own timer:

Render spins a free web service down after about fifteen idle minutes. Supabase pauses a free database after a week of no activity. Railway and Neon do similar. The mechanics — and how to reduce the waking — are laid out host by host in how to keep a free backend awake.

What you can do about it

You have three honest options, depending on how much the slow first load actually matters:

Live with it if the site is a side project and an occasional slow start is fine. Keep it awake with a small automated "ping" that visits the site every few minutes so it never idles long enough to sleep — though on some plans that can bump into other limits. Upgrade to a paid tier that never sleeps, which is the honest fix if a fast first load genuinely matters to real visitors.

On Render specifically, you can see this happening — whether your service is cold right now and how long that first request really takes:

If it's slow every time instead

If your site is slow on every load, not just the first, this isn't sleep — it's a real performance issue (heavy images, a slow database query, too much loading up front). And if it's not slow but fully unreachable, that's a different problem again: my website is down — how to fix it.

Know the difference between slow and gone

Here's the catch with a sleepy site: "slow to wake" and "actually down" look identical to a visitor, and you can't tell which is happening if you're not watching. A monitor checking from outside measures how long your site takes to respond and tells you when a wake-up has turned into a real outage.