Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My website takes forever to load

Short answer

A slow site is usually either a slow server (the first byte of the page takes long to arrive) or a heavy page (large images and scripts after it arrives). Measure one page with Google's free tools to see which, because the cure is different, then bring me the numbers.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • My own pages take several seconds to open and customers complain.
  • The home page is fine but the shop, search or admin is slow.
  • It was fast at launch and slowed down as more products or plugins were added.
  • It is slow at certain hours, such as evenings or after a campaign.
  • It is fast on my laptop and slow on a phone.

Why does this happen?

  1. The server is slow to answer

    Time to first byte is the time between starting to load a page and the first byte of the response arriving. web.dev calls 0.8 seconds or less good and anything above 1.8 seconds poor, as a rough guide. Slow connection setup and slow backend processing both raise it.

  2. The page is heavy after it arrives

    Google's Core Web Vitals measure how fast the main content shows (Largest Contentful Paint, 2.5 seconds or less), how quickly the page reacts (Interaction to Next Paint, 200 milliseconds or less) and how stable it is (Cumulative Layout Shift, 0.1 or less). Large images and scripts push these over the limit.

  3. The backend does too much work per page

    Database queries, plugins and external calls run on every visit. When one is slow, the page waits for it, and a request that waits too long can end in a timeout.

  4. A script or query runs past its limit

    A script that takes too long can be stopped by the server, and a database query can wait on another one holding a lock.

What can I do about it today?

  1. Measure one page, not the feelingOpen Google's free PageSpeed Insights, paste your slowest page address and save the result. Do it for the home page and one inner page.
  2. Note when it is slowWrite down the times of day, which pages, and whether it affects mobile only. Patterns point to causes.
  3. Ask what changedNew plugins, a bigger catalogue, a campaign, a hosting plan change or a new developer's edits. Do not remove plugins or change settings on a live site to see what happens.
  4. Do not buy a bigger server yetA larger plan can hide a problem for a while and cost more. Find the slow part first.
  5. Gather access names, not passwordsKnow who hosts the site and who controls the domain, so the work can start quickly when you decide.

When should I bring someone in?

  • The slow part is the server's first response, not the page weight.
  • It gets worse as traffic or data grows, or customers abandon checkout.
  • Your developer has tried and cannot say what is slow.

How do I handle it?

  1. Measure first, on a copy where possibleI record server response time and page load separately, so I know whether to look at the backend or the page.
  2. Back up before I touch productionA backup is taken before any change on the live site.
  3. Fix the biggest cause firstHeavy images, slow queries, missing caching or an undersized server, in the order the measurements justify. Technical detail is on the linked fix pages.
  4. Measure again and show youI repeat the same tests and give you before and after readings in plain language. I cannot promise a score, because that also depends on your visitors' devices and networks.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Does a slow site hurt my Google ranking?

Core Web Vitals are Google's measures of loading, interactivity and stability, so pages that meet them offer a better visitor experience. I cannot promise a ranking change, since Google decides that.

Is my hosting the problem?

Sometimes. If the first byte arrives slowly even for a simple page, the server or its backend is a suspect. If it arrives quickly but the page then takes long, the page weight is.

Can I fix it with a plugin?

A caching plugin can help, but stacking plugins can slow a site further. Measure before and after any change.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.