Why this matters
By the end of this guide you'll be able to measure how fast your church website actually loads on a phone, find the two or three things dragging it down, and fix the most common one yourself in under an hour. No developer, no new software, no budget.
What blocks most churches isn't the fix. It's not knowing where to look. The site was set up years ago by a volunteer, nobody has touched the speed since, and it feels slow but nobody can say why. This guide gives you a way to see it plainly.
At a glance
- Plan on about an hour, and most of that is waiting for images to re-upload.
- The single most common cause we see in church homepage reviews is oversized photos, a hero image saved straight off a camera at full resolution.
- A free test from Google tells you your real load time and points at the biggest problems, no guessing.
- If the site is slow even with small images and a clean homepage, the problem is your hosting, and that's a different conversation.
What you need before you start
- The login for whatever builds your church website (Squarespace, WordPress, Wix, Subsplash, or similar).
- A phone and a laptop, so you can see the difference between the two.
- About an hour of quiet time, ideally not right before Sunday.
- No paid tools. Everything here uses free tests.
The step-by-step
Step 1: Measure your real load time
Open PageSpeed Insights (Google's free tool) on your laptop and paste in your church homepage address. Look at the mobile score first, because that's what a first-time guest sees on their phone. Write down the number and the load time in seconds. This is your starting point, so you can tell if your changes helped.
If the tool won't load your page, your site may be blocking automated tests. In that case, just time it yourself: open the homepage on your phone on cell data, not the church wifi, and count.
Step 2: Find the heavy images
In the PageSpeed results, scroll to the section that lists what's slowing the page down. Nine times out of ten in the church homepages we review, the top items are images that are far larger than they need to be. A photo can be five or ten megabytes when it only needs to be a few hundred kilobytes. The tool names the exact files.
If the report is full of code warnings you don't understand, ignore them for now. Start with the images. That's where the time goes.
Step 3: Shrink the images
Download the oversized photos, run them through a free tool like Squoosh or TinyPNG, and re-upload the smaller versions in place of the originals. Aim to get each photo under a few hundred kilobytes. Most of the time you can't see the difference on screen, but the page loads far faster.
If your builder has a built-in image feature, use it, but check the result. Some builders still serve the full-size file even after you crop it visually.
Step 4: Cut what the homepage doesn't need
Look at your homepage the way a first-time guest would. Every autoplay video, embedded map, live social feed, and sermon player adds load time. Keep the ones that help someone decide to come on Sunday. Remove or move the rest to their own pages.
If a plugin or widget was added and never used, delete it. Unused add-ons still load in the background and slow everything down.
Step 5: Test again and compare
Run PageSpeed Insights on the same homepage again and compare the mobile number to what you wrote down in Step 1. Then open the site on your phone on cell data and feel the difference yourself. The number matters less than whether the page shows up before you'd give up waiting.
If the score barely moved after you fixed the images, the slowdown is somewhere you can't reach from the editor. Go to the next step.
Step 6: Decide if it's a hosting problem
If your images are small, your homepage is lean, and it's still slow, the problem is likely your hosting or your platform. Some cheap hosting plans and some all-in-one church platforms are simply slow, and no amount of editing fixes that. At that point the honest answer is to switch platforms, which is a bigger decision than an afternoon of cleanup.
Don't spend weeks tuning a page when the real issue is the plumbing underneath it. Confirm it's hosting, then plan the move rather than fighting the symptoms.
Quick audit checklist
- Mobile PageSpeed score written down before and after.
- Every homepage image under a few hundred kilobytes.
- No autoplay video above the first screen.
- Live social feeds and embedded maps removed or moved off the homepage.
- Unused plugins and widgets deleted.
- Homepage tested on a phone on cell data, not church wifi.
- If still slow, hosting or platform confirmed as the cause.
Frequently asked questions
Why is my church website so slow on a phone but fine on my computer?
Your office computer is usually on fast wifi, and it may have the page saved from earlier visits. A first-time guest opens it fresh on cell data. Test on your phone on cell data to see what they see. Large images are the most common reason a page that feels fine on a laptop crawls on a phone.
Do I need to pay a developer to fix this?
Usually not. The most common cause, oversized images, is something a volunteer can fix in an hour with free tools. You only need help when the site is slow after the images are small and the homepage is clean, which points at hosting or the platform itself.
Would switching to a different church website builder help?
Sometimes. If you've confirmed the slowness is your hosting or platform and not your images, then yes, a faster platform helps. But switching won't fix a homepage stuffed with full-resolution photos, so do the cleanup first and switch only if the plumbing is the real problem.
Where this connects in our work
- A five-minute look at your homepage for a plain read on what's slowing your site down and what to fix first.
- See example church sites for a sense of what a fast, simple homepage looks like.
- Book a walkthrough if you want someone to look at your site with you.
Next step
If you'd like a second set of eyes on your homepage, we can take a quick look and tell you plainly what's slowing it down.