Website review, no card needed
jesuspost.com website review
Visit site (opens in a new tab)Reviewed 16 November 202616 issues · 68 checks
This review found 16 issues worth fixing on jesuspost.com, 3 of them high impact, across 68 checks. The most urgent: 30 text elements with low contrast. 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
89BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
777 KiB3 images could be 777 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
700 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.
3 third-party services on the page
3 third-party services load with your homepage (IPONWEB, visitor-speed.com and Google Fonts), adding 176 KiB and 41 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
31 KiB2 files are served with short cache lifetimes, so returning visitors download them again (31 KiB).
Minify JavaScript
28 KiB28 KiB could be saved by minifying JavaScript.
Reduce unused JavaScript
21 KiBAbout 21 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
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.
3 checks passed
Mobile performance score: 98
98/100Your mobile performance score is 98. That is in Google's “good” band (90 and up).
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 84 ms of it running JavaScript. That is comfortably low.
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
5 checks passed
Time to Interactive: 3.7 s
3.7 sThe page is fully interactive after 3.7 s.
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Jesus Post”.
Speed Index: 2.0 s
2.0 sVisually, the page fills in at 2.0 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 4 ms
4 msScripts block the page for only 4 ms while loading. Good is under 200 ms.
Images and page weight
2 images in older formats
2 images (816 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
2 images below the first screen load straight away
2 images further down the page (504 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
3 images far larger than shown
71 KiB3 images are downloaded at several times the size a phone draws them, for example y5vxxwxs178untodd14b3l6q at 1,000 px wide, shown at 324 px. Resized copies would save about 71 KiB.
About 0.3 g of CO₂ per visit
0.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.33 g of CO₂e: 39.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.1 MB in 18 requests
1.1 MBYour homepage downloads 1.1 MB in 18 requests on a phone: images 922 KiB (4), fonts 106 KiB (3) and HTML 78 KiB (2). That is a lean page.
Accessibility
30 text elements with low contrast
30 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
23 internal links, 2 external
The homepage links to 23 pages on jesuspost.com and 2 external pages.
7 checks passed
Meta description: 109 characters
Your meta description is 109 characters: “Daily Christian news, inspiration and resources for a new generation of believers navigating a complex world.”.
One H1 headline
Your main headline reads: “Faith.Truth.Perspective.”.
Title: 39 characters
Your title is a healthy 39 characters: “Jesus Post — Faith. Truth. Perspective.”.
Canonical URL set
The canonical URL is https://jesuspost.com/.
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://jesuspost.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://jesuspost.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (425 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share 2 titles
/ and https://jesuspost.com/jesuspost all use the title “Jesus Post — Faith. Truth. Perspective.”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://jesuspost.com/articles-christ-church, https://jesuspost.com/articles-parents-prayer-children, https://jesuspost.com/articles-388-millions-christians-persecution and https://jesuspost.com/articles-fellowship-india use the same meta description. A description written for each page earns more clicks.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 9 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 9 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 362 words of copy
The homepage carries about 362 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join Newsletter”.
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Subscribe” and “Subscribe Free”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 1 of them by other companies (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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 jesuspost.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Celeste SAS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 16 issues on jesuspost.com, including 3 speed issues, 1 SEO issue and 2 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.