If you have spent any time on Google Search Console, you have seen three acronyms that sound more engineering than ministry: LCP, INP, CLS. Together they make up what Google calls Core Web Vitals, and in 2026 they quietly shape two things every church cares about — whether your site ranks in search, and whether the family finding your livestream actually sticks around to click it.
We want to demystify them, because most church websites we audit have the same few fixable issues.
What Google Is Actually Measuring
Google measures real visits to your site from real phones and browsers. Not a test in a lab — the experience your neighbor has on a five-year-old Android in a cell-signal-weak sanctuary parking lot.
LCP (Largest Contentful Paint) is how quickly the biggest visible thing on a page loads. For most church homepages, that is the hero image or banner video. Good is under 2.5 seconds.
INP (Interaction to Next Paint) is how quickly the page responds when someone taps something. Menu, giving button, event signup. Good is under 200 milliseconds.
CLS (Cumulative Layout Shift) measures whether things jump around as the page loads. You have felt this when you go to tap "Give" and an ad or banner shoves the button out of your finger's path. Good is under 0.1.
Why It Matters for a Ministry
Two reasons. First, Google uses these numbers as a ranking signal. A fast, stable site gets a small but meaningful lift in search, which matters because over 70% of people looking for a new church start online.
Second, and more importantly, these numbers track very closely to real human frustration. A visitor whose page took six seconds to load, then bounced them out of the giving button with a late-loading image, is not going to try again. That is a donation, a first-time guest, or a prayer request you never got.
The Usual Suspects on Church Sites
After auditing a lot of ministry websites, the slow ones tend to share the same pattern.
Oversized hero images. A 6 MB photo of your sanctuary at golden hour is beautiful and devastating for LCP. Most churches we work with cut their home page weight by more than half simply by resizing and using modern formats like WebP or AVIF.
Autoplay video backgrounds. They look cinematic on a MacBook. On a phone with one bar, they hurt LCP, drain battery, and often never play. If you want motion, a short looping WebM under 1 MB is usually plenty.
Too many fonts and embedded widgets. Every Google Font family is a network request. Every embedded calendar, chat bubble, and giving widget is JavaScript that runs before your visitor can tap anything. We often find sites carrying three live chat tools, two analytics scripts, and a giving widget that has not been used since 2023.
Layout jumps from late-loading elements. Ads, announcement banners, and cookie consent popups that appear after the page has rendered are the most common cause of high CLS. Reserving space for them in the layout fixes it almost every time.
What Actually Moves the Numbers
You do not need an engineering team. You need a small list of disciplined decisions.
- Compress and resize every image before uploading. Target hero images under 200 KB and content images under 100 KB.
- Pick one font family, two weights maximum. Host it through your CMS or via a
font-display: swapdeclaration so text shows immediately. - Audit third-party scripts once a quarter. If a widget is not earning its seat, remove it.
- Reserve space for anything that loads late, especially announcement banners and embedded media. Your developer can add a
min-heightoraspect-ratiorule in a few minutes. - Test on a real mobile device on a slower connection, not just your desktop. Chrome DevTools has a throttling mode that simulates this honestly.
A Simple Monthly Check
Every month, pop your homepage into PageSpeed Insights and read the real-world section. If all three vitals are green, celebrate and move on. If one is red, fix that one. Do not try to perfect everything at once — that is how churches get exhausted and give up on their own websites.
Speed is not vanity. It is hospitality in code. A fast, steady site tells the visitor that the community on the other side of the screen took care to welcome them before they even arrived.
If your Core Web Vitals are flashing red and you are not sure where to start, let us take a look. We tune ministry websites for the people who will use them, not for the benchmarks.