Website review, no card needed
bennyhinn.org website review
Visit site (opens in a new tab)Reviewed 27 October 202644 issues · 84 checks
This review found 44 issues worth fixing on bennyhinn.org, 16 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
71C- #100,943 of 125,389 reviewed websitesbeats 17%
- #61,458 of 70,171 online storesbeats 10%
- #2,117 of 2,942 WooCommerce storesbeats 23%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.1 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 177 ms |
| May 16, 2026 | 179 ms |
| May 23, 2026 | 216 ms |
| May 30, 2026 | 214 ms |
| Jun 6, 2026 | 214 ms |
| Jun 13, 2026 | 218 ms |
| Jun 20, 2026 | 186 ms |
| Jun 27, 2026 | 186 ms |
| Jul 4, 2026 | 190 ms |
| Jul 11, 2026 | 190 ms |
| Jul 18, 2026 | 191 ms |
| Jul 25, 2026 | 190 ms |
| Aug 1, 2026 | 186 ms |
| Aug 8, 2026 | 175 ms |
| Aug 15, 2026 | 165 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 158 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 169 ms |
| Sep 19, 2026 | 172 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 172 ms |
| Oct 10, 2026 | 173 ms |
| Oct 17, 2026 | 176 ms |
| Oct 24, 2026 | 177 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
Render-blocking requests
9.2 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.2 s.
Reduce unused JavaScript
4.8 s · 953 KiBAbout 953 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Improve image delivery
4.5 s · 971 KiB6 images could be 971 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.5 s faster on a phone.
Use efficient cache lifetimes
3.0 s · 368 KiB3 files are served with short cache lifetimes, so returning visitors download them again (368 KiB).
Reduce unused CSS
1.6 s · 341 KiBAbout 341 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 70). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (givecloud.co, Google Tag Manager and Google CDN and others), adding 1.2 MB and 810 ms of main-thread time.
givecloud.co adds 545 ms
545 msgivecloud.co costs a phone 545 ms of main-thread work and 539 KiB 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 345 ms. During a long task the page ignores taps.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 737 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 117 ms
117 msGoogle CDN costs a phone 117 ms of main-thread work and 351 KiB 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.
Legacy JavaScript
150 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 70 but mobile only 42. 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.
1 checks passed
Server response: 17 ms
17 msYour server sent the HTML in 17 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.
First Contentful Paint: 8.1 s
8.1 sThe first text or image appears after 8.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 22.4 s
22.4 sYour largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 22.6 s
22.6 sThe page becomes fully interactive after 22.6 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
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.
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 591 ms
591 msScripts block taps and scrolling for 591 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 177 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 159 ms
159 msReal visitors wait 159 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 112 requests
5.5 MBYour homepage downloads 5.5 MB in 112 requests on a phone: images 3.3 MB (23), scripts 1.4 MB (47) and stylesheets 381 KiB (25). Under 2 MB keeps phones on slow connections fast.
7 images below the first screen load straight away
7 images further down the page (339 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (75 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.
About 1.6 g of CO₂ per visit
1.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.55 g of CO₂e: 186.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail 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.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (81 characters)
Your title is 81 characters, so Google will cut it off around 60: “Benny Hinn Ministries - Building a legacy of faith—yesterday, today, and forever!”.
2 H1 headlines
There are 2 <h1> headlines (“Give Glory to God as we lift up the Name of Jesus…” and “SPECIAL ANNOUNCEMENT Healing Service Live with Pa…”). One clear main headline is easier for people and search engines.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
67 internal links, 20 external
The homepage links to 67 pages on bennyhinn.org and 20 external pages.
6 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Experience the life-changing power of the Gospel with Pastor Benny Hinn Ministries through teaching, healing, prayer, a…”.
Canonical URL set
The canonical URL is https://www.bennyhinn.org/.
Structured data in place
Structured data found: BreadcrumbList, 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://www.bennyhinn.org/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.bennyhinn.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.
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 (854 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
https://www.bennyhinn.org/about and https://www.bennyhinn.org/author/cngilo all use the title “About Pastor Benny Hinn - Benny Hinn Ministries”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.bennyhinn.org/intimate-worship has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.bennyhinn.org/about and https://www.bennyhinn.org/author/cngilo use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.bennyhinn.org/author/cngilo, whose canonical is https://www.bennyhinn.org/about. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://www.bennyhinn.org/about, https://www.bennyhinn.org/intimate-worship, https://www.bennyhinn.org/miracle-moments, https://www.bennyhinn.org/your-faith-walk-blog, https://www.bennyhinn.org/partnership and https://www.bennyhinn.org/products and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 12 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 “Failed to load resource: net::ERR_FAILED”.
13 distorted images
13 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
A 8-field form
Your longest form asks for 8 fields (3 required). Every extra field lowers completion.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 632 words of copy
The homepage carries about 632 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
3 calls to action
The homepage has 3 calls to action, for example “Contact”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
12 cookies set on arrival
12Opening the homepage sets 12 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.
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 bennyhinn.org, 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
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on bennyhinn.org, including 21 speed issues, 3 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.