Website review, no card needed
livingwaters.com website review
Visit site (opens in a new tab)Reviewed 26 October 202632 issues · 82 checks
This review found 32 issues worth fixing on livingwaters.com, 10 of them high impact, across 82 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74C- #82,636 of 117,615 reviewed websitesbeats 26%
- #52,412 of 66,923 online storesbeats 18%
- #1,473 of 2,700 WooCommerce storesbeats 39%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.8 s |
| May 16, 2026 | 6.0 s |
| May 23, 2026 | 6.2 s |
| May 30, 2026 | 6.3 s |
| Jun 6, 2026 | 6.3 s |
| Jun 13, 2026 | 6.3 s |
| Jun 20, 2026 | 6.3 s |
| Jun 27, 2026 | 6.3 s |
| Jul 4, 2026 | 6.1 s |
| Jul 11, 2026 | 6.0 s |
| Jul 18, 2026 | 5.9 s |
| Jul 25, 2026 | 5.7 s |
| Aug 1, 2026 | 5.7 s |
| Aug 8, 2026 | 5.6 s |
| Aug 15, 2026 | 5.2 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 4.9 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.6 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.7 s |
| Oct 24, 2026 | 4.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 252 ms |
| May 16, 2026 | 282 ms |
| May 23, 2026 | 312 ms |
| May 30, 2026 | 329 ms |
| Jun 6, 2026 | 339 ms |
| Jun 13, 2026 | 346 ms |
| Jun 20, 2026 | 348 ms |
| Jun 27, 2026 | 368 ms |
| Jul 4, 2026 | 352 ms |
| Jul 11, 2026 | 360 ms |
| Jul 18, 2026 | 354 ms |
| Jul 25, 2026 | 348 ms |
| Aug 1, 2026 | 379 ms |
| Aug 8, 2026 | 370 ms |
| Aug 15, 2026 | 380 ms |
| Aug 22, 2026 | 368 ms |
| Aug 29, 2026 | 313 ms |
| Sep 5, 2026 | 272 ms |
| Sep 12, 2026 | 230 ms |
| Sep 19, 2026 | 216 ms |
| Sep 26, 2026 | 206 ms |
| Oct 3, 2026 | 200 ms |
| Oct 10, 2026 | 204 ms |
| Oct 17, 2026 | 194 ms |
| Oct 24, 2026 | 188 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 87). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 110 KiBAbout 110 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 560 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 132 ms. During a long task the page ignores taps.
Reduce unused CSS
51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 87 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Improve image delivery
5 KiB1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1 checks passed
Server response: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Cumulative Layout Shift: 0.47
0.47The layout shifts by 0.47 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 6.2 s
6.2 sThe page becomes fully interactive after 6.2 s. Good is under 3.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
5 checks passed
Real-user INP: 181 ms
181 msReal visitors wait 181 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 252 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.8 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 71 ms
71 msScripts block the page for only 71 ms while loading. Good is under 200 ms.
Images and page weight
About 0.3 g of CO₂ per visit
0.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.30 g of CO₂e: 35.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.0 MB in 73 requests
1.0 MBYour homepage downloads 1.0 MB in 73 requests on a phone: scripts 508 KiB (47), images 261 KiB (11) and fonts 176 KiB (5). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
3 links inside paragraphs rely on colour alone to stand out.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
29 links without text
29 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
136 internal links, 44 external
The homepage links to 136 pages on livingwaters.com and 44 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “LivingWaters.com is an evangelism resource and training site that helps Christians share their faith (evangelism) effec…”.
Title: 49 characters
Your title is a healthy 49 characters: “Living Waters | Inspiring. Equipping. Fulfilling.”.
Canonical URL set
The canonical URL is https://livingwaters.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://livingwaters.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://livingwaters.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (849 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a meta description
https://livingwaters.com/events, https://livingwaters.com/request and https://livingwaters.com/interview-request-form use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://livingwaters.com/podcast, https://livingwaters.com/outreach/way-of-the-master, https://livingwaters.com/learn, https://livingwaters.com/events, https://livingwaters.com/request and https://livingwaters.com/interview-request-form and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://livingwaters.com/events has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'prototype')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 10-field form
Your longest form asks for 10 fields (1 required). Every extra field lowers completion.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 603 words of copy
The homepage carries about 603 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact Us”, “Speaker Request” and “Interview Request”.
Analytics in place
Analytics detected: Meta Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 11 email links.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at livingwaters.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- React
- E-commerce
- WooCommerce
- Hosting
- Cloudflare
Company
- Headquarters
- Bellflower
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on livingwaters.com, including 12 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.