Get my free demo
Articles · No. 2 of 5

Built for a Desktop in 2012

Most first-time guests meet your church on a phone. A site designed for a desktop in 2012 meets them with pinching, zooming, and slow pages.

By Mike Edens · · 10 min read

The screen your guest is actually holding

When your church's website was built, it was probably designed the way most websites were designed then. On a desktop screen, in an office, by someone looking at a wide monitor. The layout assumed room to spread out. The menus assumed a mouse. The photos assumed bandwidth to spare.

Your guest is not sitting in that office. She is standing in her kitchen on Saturday night, phone in one hand, checking whether your church has a service she can get her family to in the morning. Or he is in the passenger seat on the drive across town, trying to confirm the address. Or she has just moved here, knows no one, and is comparing two churches in two browser tabs, both of them pinched and zoomed into fragments because neither site was made for the screen she is holding.

This is the second pain point in Tov's series, and it is the most mechanical of the five. The device changed. A great many church websites did not. This article sets out what actually changed, with numbers that can be checked, and then makes the pastoral case that designing first for the phone in a guest's hand is a form of meeting people where they are.

The phone became the front door

The honest version of the device numbers needs one distinction kept clear. Worldwide, mobile is the clear majority. In North America, it is roughly half.

StatCounter, which tracks device use across its global network, put mobile at 59.88 percent of web use worldwide in October 2026, against 38.49 percent for desktop. For North America in the same month, StatCounter put desktop at 52.8 percent and mobile at 47.2 percent (StatCounter Global Stats, October 2026). So no honest writer should claim that most American web traffic is already mobile. The accurate claim is nearly as strong. Close to one in two visits in North America is on a phone now, and the guest a church most hopes to reach, a younger family new to the area, is the person most likely to be in that mobile half.

Ownership tells the same story from the other side. Pew Research Center reports that 98 percent of U.S. adults own a cellphone of some kind and 91 percent own a smartphone, up from 35 percent in Pew's first smartphone survey in 2011 (Pew Research Center, Mobile Fact Sheet, 2026). More telling for a church, 16 percent of U.S. adults are smartphone only internet households, meaning they own a smartphone but do not subscribe to home broadband. Among adults ages 18 to 29, that share is 24 percent. For one in six adults, and one in four young adults, there is no desktop fallback waiting at home. If your site fails on their phone, it does not fail onto a bigger screen. It fails completely.

Church specific research confirms the website itself is in the middle of the search. Lifeway Research's 2023 study of Protestant church switchers found that 37 percent relied on church websites in their search for a new congregation, and movers relied on them at 40 percent. Among switchers first introduced to their church through its website, the facts they rated most helpful were practical ones: beliefs and mission at 67 percent, location at 66 percent, and worship times at 64 percent (Lifeway Research, 2023). Practical facts, needed quickly, very often on a phone, in the middle of an ordinary day. That is the use case a 2012 desktop design serves worst.

Slow is a decision guests make for you

A desktop era site does not only look wrong on a phone. It often loads like a desktop era site, heavy with large images, a slideshow built for a wide screen, and code layered over a decade of good intentions.

Google's research on mobile speed is old enough that it should be dated when it is quoted, and it is still the traceable benchmark. In its mobile page speed benchmarks, published in March 2017 from 2016 Google Analytics data, Google reported that 53 percent of mobile visits are abandoned if a page takes longer than three seconds to load. In the same research, as load time rose from one second to seven seconds, the probability of a mobile visitor bouncing rose 113 percent (Google, Think with Google, 2017). Those figures are nearly a decade old, and readers should know it. What has changed since is not human patience. Phones got faster and expectations rose with them. A site that was merely slow in 2017 reads as broken in 2026.

Google now publishes the targets it wants sites to meet, in its Core Web Vitals guidance. A page should load its main content within 2.5 seconds, respond to interaction in under 200 milliseconds, and hold its layout steady enough that buttons do not move while a guest is trying to tap them, a measure Google calls Cumulative Layout Shift, with a target under 0.1 (Google Search Central, Core Web Vitals). A guest will never know these terms. She will know that the Plan a Visit button jumped just as she touched it and opened the wrong page. She will know that the service time took nine seconds to appear. She will draw the natural conclusion about how much the church expected her.

There is a second, quieter penalty for leaving the mobile site as the neglected copy. Since October 2023, Google's mobile first indexing is complete. Google now crawls and indexes the mobile version of a site as the primary version, using its smartphone crawler, for every site that works on mobile at all (Google Search Central Blog, October 31, 2023). Google's own best practices say it uses the mobile version of a site's content for indexing and ranking, and recommends responsive design, one site that adapts to the screen, as the pattern to use (Google Search Central, mobile first indexing). In plain terms, whatever your mobile site hides, shrinks, or drops is what Google knows about your church. A time that is present on desktop and missing on mobile is, for search purposes, a time your church does not publish.

Meeting people where they are is an old practice

None of this requires a pastor to become a technology enthusiast. It requires the older instinct that has always shaped faithful ministry: go to where the people actually are, and speak in a form they can actually receive.

Paul's missionary habit was to start in the places a town already gathered. The printed bulletin was once the new technology a church adopted so a guest could follow the service without already knowing it. The phone is simply the current version of the same question. It is where a newcomer will meet your church first, almost certainly before she meets a single member of it. A congregation that would never lock its side door and call the building welcoming will sometimes publish a website that is effectively locked on the device most guests carry, and never notice, because the people inside the church mostly visit the site from a laptop, if they visit it at all.

Lifeway, reporting mystery guest feedback in its piece on questions guests bring to a church website, notes that guests do not want to scroll to the bottom of a page to learn when the church meets, or dig through multiple tabs for what they need (Lifeway Research, 2019). On a phone, that digging is worse. Small tap targets, menus hidden behind icons, pages that require pinching to read. Each one is small. Together they send a message no church intends: this was not made with you in mind.

There is also a fairness point worth naming plainly. The smartphone only households in Pew's data, 16 percent of adults, are not a random slice of your town. A phone is the cheapest reliable way online, and households making hard choices about money are disproportionately the ones relying on it. A church with good news for people under financial strain should be careful that its digital front door does not work best for the households with the newest laptops. Designing for the phone first is, among other things, designing for the neighbor with the fewest options.

What phone first actually means

Phone first is not a slogan and it does not mean a smaller version of the desktop site. It means the mobile presentation is designed first, tested first, and treated as the main event.

  • One responsive site, not a separate mobile copy. A single site that adapts to the screen keeps the facts in one place, which is also what Google recommends. Separate copies drift apart, and drift is how the Facebook page ends up saying one time and the site another.
  • The essentials in the first screen. Sunday times, town, and a clear next step, readable at arm's length with no pinching, no zooming, and no hunting through a menu.
  • Tap targets a thumb can hit. Buttons sized and spaced for a finger, not a mouse pointer, and a phone number that dials when it is tapped.
  • Weight kept down. Photos compressed for a phone connection, no autoplay slideshow carrying the homepage, and the whole first screen usable within Google's 2.5 second main content target on an ordinary mobile network.
  • Tested on a real phone. Not the designer's phone alone, and not a desktop browser narrowed down. A mid range Android phone on mobile data is the honest test, because that is the honest guest.
  • Nothing important dropped on mobile. The same times, the same address, the same children's information. A shorter mobile page that quietly deletes the facts a guest came for is a worse page, however clean it looks.

A useful test any pastor can run in two minutes: hand your phone to someone who has never been to your church, open the homepage, and ask them to tell you what time Sunday service starts and where the church is. Time them, silently. If it takes more than a few seconds, or a single pinch and zoom, the site is telling you what it tells every guest.

The quiet conclusion

The desktop in the church office is no longer where your town meets your church. The meeting happens on phones, in kitchens and cars and lunch breaks, in the few minutes when a person decides whether this Sunday is the Sunday they will try. Building for that screen first is not chasing a trend. It is the ordinary work of removing obstacles between a guest and a gathering, and churches have always understood that work once they could see the obstacle.

If you want to see your church's homepage rebuilt for the phone first, with the desktop version following from it rather than the other way around, Tov will build you a free demo of your homepage, and you can judge it on your own phone before you spend anything.

Sources

Made good. Kept good.

Your homepage, rebuilt. Free.

Tell us where to send it. No call, no meeting, no account to create.

Get my free demo →