pray.com website review

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

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

Your mobile performance score is 72 (desktop: 97). Pages that score under 90 lose visitors before the first paint.

The page has 2,960 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

8 images could be 162 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

1 third-party service load with your homepage (Amplitude Mobile Analytics), adding 28 KiB and 18 ms of main-thread time.

Desktop scores 97 but mobile only 72. A gap that wide usually means heavy scripts and images that hit phones hardest.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 92 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

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

Your title is only 19 characters: “Discover | Pray.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 408 pages on pray.com and 10 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

https://www.pray.com/gift is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://www.pray.com/discover all use the title “Discover | Pray.com”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.pray.com/discover/be257d4a-f0a7-4133-a6a6-9d1dd0424b32, whose canonical is https://www.pray.com/series/nehemiah-alliance/be257d4a-f0a7-4133-a6a6-9d1dd0424b32. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 10 trust badges. 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 2,312 words of visible text.

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

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.

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