Why your church website is slow
A slow church website is usually caused by unoptimised photographs, too many plugins, cheap hosting, or scripts loaded from other sites. Photographs are the most common cause and the easiest to fix: a camera image straight from a phone can be twenty times larger than it needs to be.
How slow is too slow?
The practical threshold is 2.5 seconds on a phone for the main content to appear. Past roughly three seconds, a meaningful share of visitors leave before seeing anything.
Measure with Google PageSpeed Insights, which names the specific cause rather than only reporting a score. Test the address people actually visit, on mobile.
Are photographs the problem?
Usually. A photograph straight from a phone camera is often four to eight megabytes, while the same image displayed correctly on a website needs perhaps two hundred kilobytes.
A church homepage with six such photographs carries thirty megabytes that should be under two. On a phone connection that is the entire difference between fast and unusable.
The fix is resizing to the dimensions actually displayed and converting to WebP. Savings of 70 to 90 percent are routine and no visible quality is lost.
Could it be the plugins?
On WordPress sites, frequently. Each plugin can add its own scripts and stylesheets to every page, including pages that do not use the plugin at all.
Church sites accumulate plugins over years as different volunteers try things. Removing what is genuinely unused is free and often produces a visible improvement.
Is cheap hosting to blame?
Sometimes, and it is worth checking before spending money on it. Server response time is measurable separately; anything above roughly 600 milliseconds points at hosting or at the site doing too much work per request.
Moving hosting is worth doing when response time is genuinely the bottleneck. It is a waste when the real problem is thirty megabytes of photographs, which no hosting upgrade will fix.
Does speed affect our Google ranking?
Yes, though as a tiebreaker between comparable results rather than a dominant factor. The larger effect is on visitors, who leave slow sites.
There is a second reason that matters more than it used to: AI search crawlers work to a limited time budget per page, so slow sites are crawled less completely and are less likely to be cited.
| Cause | How to confirm | Typical fix |
|---|---|---|
| Unoptimised images | PageSpeed lists image sizes | Resize, convert to WebP |
| Too many plugins | Count active plugins | Remove unused ones |
| Slow hosting | Server response over 600ms | Move hosting |
| Third-party scripts | PageSpeed lists external requests | Remove or defer |
Work in this area
Frequently asked questions
Can we fix this ourselves?
The image problem, yes. Resizing photographs before uploading and converting to WebP needs no developer and produces the largest single improvement.
Will a caching plugin solve it?
It helps and it is not a substitute. Caching speeds up delivery of what is already there; it does not make a thirty-megabyte page smaller.
How much does a speed fix cost?
It depends on the cause. Image optimisation is usually a small job. Rebuilding a site overloaded with plugins is closer to a redesign.
Does video slow the site down?
Video hosted on your own server does, badly. Embedding from YouTube or Vimeo shifts that load to them and is almost always the right choice.
Our site is fast on desktop but slow on mobile. Why?
Because desktop connections hide oversized images that mobile connections expose. Always test on mobile; that is where most church website visits happen.
Talk it through first
A short call costs nothing and usually clarifies whether this is the right next step for your organisation.
Get in touch