Why this matters
A first-time guest who finds your website is doing one of two things. Either someone invited them and they are checking before they say yes, or they are looking for a church and yours came up in search. Either way, they are not browsing. They are trying to decide whether your church is worth a Sunday morning.
We have recorded a lot of these reviews. The pattern is consistent. Visitors spend 20 to 40 seconds on the homepage. They do not scroll past the first screen unless something on it gives them a reason to. They do not read paragraphs. They scan, decide, and either click "plan a visit" or leave.
Here are the five things they actually notice, ranked by how much they move the decision.
1. Service times — above the fold, or buried
This is the single biggest one. A first-time guest visiting your website is almost always trying to answer: when can I show up?
Most church homepages we look at hide service times. Not on purpose. The times are usually somewhere — in the footer, on a separate "plan a visit" page, inside a graphic, or two scrolls down behind a hero video. The problem is that the guest does not know to look there. They expect to see the time and the address in the first screen, in plain text.
The fix is small and does not need a redesign. Move the service time and address into the first screen. Put them in real text, not inside an image. If your hero is a video, overlay the times on it or put them immediately below. Test on a phone, because most of your first-time traffic is on a phone, not a desktop.
Two specifics that matter:
- Write the time in a way a person reads, not a way a designer types. "Sundays at 9 and 11 AM" reads faster than "9:00 AM | 11:00 AM."
- If you have a campus, write the address right there. Do not make the visitor click into a separate page to find it.
This single change moves more first-time-guest behavior than any redesign. We see it every week.
2. What to expect — the question behind the question
The second thing a first-time guest is trying to figure out is what showing up will feel like. They are not going to ask. They are going to look for clues. If the clues are not there, they assume the worst.
The questions in their head, roughly in order:
- How long is the service?
- What do people wear?
- Is there something for my kids? What ages?
- Where do I park? Where do I go in?
- Am I going to be put on the spot?
Most church websites answer none of these directly. They have an "about" page that talks about beliefs, and a "ministries" page that lists what the church offers internally, and somewhere a "plan a visit" page that says "we are so glad you are considering joining us."
Here is the fix. Write a single "what to expect" section, on the homepage or one click away. Answer the questions a first-time guest actually has, in plain language, in the order above. Two short paragraphs and a few bullets is enough. Do not bury it in copy about the church's heart or mission. That comes later, after the guest has decided to visit.
3. Mobile-first experience — which it will be
If you have not opened your church website on a phone in the last month, do that before you do anything else. Most first-time-guest traffic to church websites is mobile. We see this in the analytics on every review we run.
What goes wrong on mobile, in order of frequency:
- The hero image takes over the entire first screen, so service times are not visible without scrolling.
- The navigation menu is hidden behind a hamburger icon and the "give" button is buried inside it.
- A pop-up or a chat widget covers the bottom third of the screen on load.
- Tap targets are too small. Buttons sit too close together. The "plan a visit" button shares an edge with the "watch live" button.
Test it yourself. Open your homepage on your own phone. Count how many seconds it takes you to find the service time. If it is more than five seconds, your first-time guests are leaving on that step.
A separate point. Page speed matters more on mobile than on desktop, because mobile connections are slower and people give up faster. A 5 MB hero image is the most common offender we see. Run your homepage through Google's PageSpeed Insights and address whatever it flags before you assume the site needs a rebuild.
4. Tone of the homepage copy — insider or visitor
This is the one most churches do not see in their own copy, because the words feel normal to people inside the church. A visitor reading the same words feels excluded.
Insider language sounds like this:
- "Join us for life-giving worship every Sunday."
- "Experience the transformative power of community."
- "We are passionate about doing life together."
A first-time guest reads those sentences and feels nothing. The words are not specific. They do not answer a question. They sound like every other church website. The guest assumes your church is fine but not for them.
Visitor language sounds like this:
- "Sundays at 9 and 11 AM. About an hour long."
- "Wear what you would wear to lunch. We do not care."
- "We have a kids' program for newborns through fifth grade, running during both services."
Specific. Plain. Answers a question the guest had. The guest reads those sentences and thinks, "okay, I can see myself walking in there."
The test we use: read the homepage out loud, slowly. If a sentence sounds like something you would say to a friend across a table at a coffee shop, it works. If it sounds like a brochure, rewrite it.
5. Trust signals — real, recent, and human
The last thing a first-time guest is doing in those first 30 seconds is sniffing for trust. Is this a real church with real people, or is the website a placeholder no one has touched in three years?
The signals they look for:
- Photos of actual people from the church, not stock photography. They can tell the difference.
- Names. The pastor's name. The kids' director's name. A real bio with a real photo.
- Dates that are recent. The last sermon was last week, not from October 2022. The events list has something in the next month, not the next year.
- A real address, in real text, with a real phone number. Not a contact form that goes into a black hole.
The opposite signals — stock photos of a generic family at a beach, no staff page, a "latest news" item from 18 months ago — make the guest assume the church is not as active as the website suggests, even if it is.
This is a long-term hygiene issue, not a one-week fix. The simplest version: walk through the homepage and the "about" page. For every photo, ask whether it is of an actual person at your church. For every date, ask whether it is from the last 30 days. If the answer is no, replace it or remove it.
What this looks like together
A first-time-guest-friendly church homepage, in 30 seconds, says:
- We meet at this time, at this address. Here is what the building looks like.
- A service is about this long. People dress like this. Kids go here.
- The pastor is this person. Here is what they look like.
- Here is what happened last Sunday. Here is what is happening next.
That is it. No hype. No buzzwords. No videos with a slow build. Just answers to the questions in the visitor's head, in the order they are asking them.
The redesigns we do start from this list, not from a design moodboard. Get the answers above the fold first. Everything else is a refinement.
Next step
If you want a second pair of eyes on how your church website handles these five things, send us the URL. We record about 40 of these a year. You get a five-minute Loom back with notes on the homepage, service times, sermons, and giving. No call, no pitch. Start one at /church/review.