lds.org website review

About 721 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.0 s faster on a phone.

53 files are served with short cache lifetimes, so returning visitors download them again (615 KiB).

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

4 third-party services load with your homepage (pure.cloud, Adobe Tag Manager and New Relic and others), adding 1.3 MB and 1.1 s of main-thread time.

pure.cloud costs a phone 943 ms of main-thread work and 1.1 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

13 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

88 KiB could be saved by minifying JavaScript.

A phone's processor spends 3.1 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

12 long tasks block the main thread while loading, the longest for 256 ms. During a long task the page ignores taps.

6 images could be 52 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

Your largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Guatemala FHD Stock: Family Playing Outside”.

The page becomes fully interactive after 15.1 s. Good is under 3.8 s.

The first text or image appears after 4.7 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 802 ms for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 503 ms in total while the page loads. Good is under 200 ms.

Your homepage downloads 2.4 MB in 113 requests on a phone: scripts 1.7 MB (39), images 495 KiB (20) and fonts 133 KiB (8). Under 2 MB keeps phones on slow connections fast.

6 images further down the page (190 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.68 g of CO₂e: 81.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

8 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (2 elements).

There are 2 <h1> headlines (“God Knows and Loves You” and “God Knows and Loves You”). One clear main headline is easier for people and search engines.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 25 pages on lds.org and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.churchofjesuschrist.org/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.

https://www.churchofjesuschrist.org/welcome/common-questions has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://www.churchofjesuschrist.org/welcome/god-loves-you, whose canonical is https://www.churchofjesuschrist.org/welcome/god-loves-you?lang=eng. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.churchofjesuschrist.org/welcome/find-a-church has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.churchofjesuschrist.org/welcome/find-a-church, https://www.churchofjesuschrist.org/welcome/families-together-forever, https://www.churchofjesuschrist.org/welcome/bible-book-of-mormon-word-of-god, https://www.churchofjesuschrist.org/welcome/meet-with-missionaries, https://www.churchofjesuschrist.org/welcome/common-questions and https://www.churchofjesuschrist.org/learn/people/dallin-h-oaks/life-leadership and 1 other took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 459 words of visible text.

Opening the homepage sets 14 cookies (measured from a US location before any click).

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.