Why Your Church Needs To Update It’s Website In 2013

Steve Fogg —  January 10, 2013 — 19 Comments


In the last half of 2012 I developed our digital communications strategy for 2013. One obvious area that needed attention was our church website. One problem was looming large on the horizon in 2013.

We live in a Post-PC era

Globally PC sales are the slowest they have ever been. Tablet and smart-phone sales are rocketing. Consumer behaviour is radically shifting and the church needs to move with it.

I’ve been an advocate for the need for churches and non-profits to think ‘mobile first’ for over a year now, the long-term trends suggest that mobile usage will become the predominant way we consume web content in the future. Our own web analytics are showing that mobile web and tablet usage is increasing exponentially year on year.

Some churches were early mobile adopters and adapted a two-fold approach – a mobile site and a desktop site. That was great until tablets came along and spoilt the party. Now churches need to create a great viewing experience at multiple sizes.

Can’t we just build an app?

Many churches have started developing their own church app’s and I’m an advocate for apps. We have built one ourselves. However research shows that in the church world at least App’s are for insiders, mobile web is for outsiders. That means that if a church is on mission it should also create an experience crafted for the great commission.

Pew Research says that 60% of tablet users prefer reading news on the mobile web than via an app. While I think churches should certainly offer apps, it’s clear that having a great mobile website should be the priority.

The bottom line is that it’s not a choice between App or Web. Churches need a both/and digital communications strategy.

How do we solve this problem?

How can a church have a website that will work seamlessly on mobile/tablet and desktop in 2013? The answer is simple. Responsive designed church websites.

What is responsive design? I’m glad you asked.

Responsive design is simply when your website detects what device you are viewing from and responds accordingly. Responsive design alters the image sizes automatically and reorders the information to a predesigned order to fit the device you are viewing from.

The benefits are quite obvious: You build a website once, and it works seamlessly across thousands of different screens. Below is Starbucks for example, same site just on different devices. (You can find out more from Ethan Marcotte who was one of the original developers of this design philosophy, it’s a bit web geeky but you’ll get the drift.)


Is responsive the only answer?

For the moment my call would be absolutely yes. But remember responsive design is just a tool. It is simply a means to help you communicate across the different devices, it isn’t an end in itself. Some day, a new thing will take over. Remember flash? Same deal.

This problem obviously isn’t just confronting churches, but all non-profits and businesses will also need to respond. Many are already responding. We are half-way through rebuilding ours.

Have you seen any decent responsive designed websites? Anything to add? Comment below

If you liked this post, please say thanks by sharing it:

Related posts:

  1. What Every Pastor Needs To Know About Their Church Website
  2. Mobile Web vs Mobile Apps – Should your church invest?
  3. 7 Great Church Websites That Have Responsive Design
  4. 12 Great Examples Of Church Website Design For Easter

19 responses to Why Your Church Needs To Update It’s Website In 2013

  1. We went responsive in the middle of last year http://www.alburybiblechurch.com.au
    It was suprisingly easy, there are so many responsive wordpress and joomla templates out there so its doesnt have to be a hard or costly exercise.
    Mobile visitors make up about 20% of our site visits, and we’re from the country so Im sure its much higher in urban areas and churches that have young congregations.

    • Nice work Rowan!

      I’ve seen a quite a few themes around that are responsive too. Our stats are along similar lines to yours. I think the challenge is that even if a church adopts a responsive approach, it can still look awful. Design and usability needs to still be at the centre!

  2. I’m launching a new site for my church hopefully next week, and our biggest concern was that it be responsive. People use mobile devices to view websites, and we don’t want to hinder them from the opportunity to encounter God just because they can’t load our site on their mobile device.

  3. I totally agree with this post and “Responsive” is now the main feature I look for first when getting a WordPress template. It is much broader then just mobile growth but also about the diversity of devices and browsers (phones, tablets, laptops etc.). Anyways glad you are helping others see the importance of it.

  4. “Responsive” is definitely the way we need to move toward. Did I miss a blog about the possibility of the web at large moving toward HTML5/CSS3/JS as well? The jungle of making things compatible for all the devices and OSs out there (both for regular content and now the growing non-flash (video) platform of newest browsers) has been difficult to navigate until some of this “responsive” and HTML5 discussion has been raised. Would love to hear more…

  5. I think the goal of responsive design is good, but the result sometimes adversely affects usability. One example: Responsive design may force iPhone/iPad web page fonts to very small sizes that cannot be enlarged by pinch/zoom.

  6. Actually a responsive isn’t the only answer (“responsive” as in the CSS changes depending on the size of the viewport) — another option is to create a mobile version of your website, which can be very different to the “Desktop” version and generally lives at a separate URL from that version. It would cost more so you’d have to make sure the user base was there, but it would allow for a better user experience because, in theory, the site is designed with mobile user in mind — the whole info-architecture (not just the user interface) can be specific to a mobile device.

  7. I took the church I work at a responsive route. I am still re-doing the site and have a long way to go. Getting ready to launch more video on each ministry page and exciting features for 2013 http://www.covenantpres.com

  8. Great stuff. I’ll add another piece – there’s no need for a middle of the road solution anymore either. We’re relaunching our church site at peachtreepres.org, thinking big and small. People are either viewing on a mobile or on larger desktop screens, so we launched a 1200 wide site in November and are going to create a mobile web version next. We have an app already, but may convert that primarily to members login – not sure on the last piece yet.

  9. Steve, I think you mentioned you had some vendors/designers re: developing a responsive site. Could you please email a few to me so I can get some budget ballpark re: this? Thanks much.

  10. Steve, I realize this post is kind of old now, but I’ve a question regarding Responsive. We went responsive about March ’12 and have had great traction. But my concern now is overload. When a mobile user visits our website do they really need the ENTIRE website at their disposal, or just what a mobile user would typically look for? contact info, media, latest news/events etc. I’m trying to decide how to attack this is an upcoming website update…would love to know your thoughts. :D

    • Hi Jonathan, I don’t this is a responsive issue. It’s a priority issue. What is the most important things you want people to know about balanced with what areas of your site are people visiting?

      If we don’t tell them what’s important, then by default nothing becomes important.” -Dawn Nicole Baldwin –

      If you can look at your analytics that will tell you one side of the story and you/and your leadership will need to determine the other side of the coin.

      Hope that helps! Don’t forget to subscribe via email or RSS… I’ve got lots of web posts coming up.

Leave a Reply


Text formatting is available via select HTML. <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>