Website review, no card needed
cloversites.com website review
Visit site (opens in a new tab)Reviewed 30 October 202638 issues · 80 checks
This review found 38 issues worth fixing on cloversites.com, 12 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.2 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 5.0 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 5.0 s |
| Aug 22, 2026 | 5.2 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.7 s |
| Sep 12, 2026 | 5.8 s |
| Sep 19, 2026 | 5.7 s |
| Sep 26, 2026 | 5.7 s |
| Oct 3, 2026 | 5.6 s |
| Oct 10, 2026 | 5.3 s |
| Oct 17, 2026 | 5.1 s |
| Oct 24, 2026 | 5.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 357 ms |
| May 16, 2026 | 404 ms |
| May 23, 2026 | 430 ms |
| May 30, 2026 | 436 ms |
| Jun 6, 2026 | 428 ms |
| Jun 13, 2026 | 411 ms |
| Jun 20, 2026 | 403 ms |
| Jun 27, 2026 | 393 ms |
| Jul 4, 2026 | 395 ms |
| Jul 11, 2026 | 401 ms |
| Jul 18, 2026 | 402 ms |
| Jul 25, 2026 | 407 ms |
| Aug 1, 2026 | 394 ms |
| Aug 8, 2026 | 380 ms |
| Aug 15, 2026 | 368 ms |
| Aug 22, 2026 | 376 ms |
| Aug 29, 2026 | 400 ms |
| Sep 5, 2026 | 397 ms |
| Sep 12, 2026 | 408 ms |
| Sep 19, 2026 | 405 ms |
| Sep 26, 2026 | 392 ms |
| Oct 3, 2026 | 395 ms |
| Oct 10, 2026 | 390 ms |
| Oct 17, 2026 | 381 ms |
| Oct 24, 2026 | 387 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
Reduce unused JavaScript
1.6 s · 776 KiBAbout 776 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Use efficient cache lifetimes
4.5 MB29 files are served with short cache lifetimes, so returning visitors download them again (4.5 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, website-files.com and Facebook and others), adding 6.1 MB and 1.0 s of main-thread time.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
website-files.com adds 208 ms
208 mswebsite-files.com costs a phone 208 ms of main-thread work and 4.8 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.
Google Tag Manager adds 436 ms
436 msGoogle Tag Manager costs a phone 436 ms of main-thread work and 580 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.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Reduce unused CSS
300 ms · 62 KiBAbout 62 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 70 ms
70 msGoogle CDN costs a phone 70 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 112 ms. During a long task the page ignores taps.
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need.
Improve image delivery
34 KiB3 images could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 64 ms
64 msYour server sent the HTML in 64 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 LCP: 4.8 s
4.8 sReal visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.3 s
4.3 sReal visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.3 s
3.3 sReal visitors wait 3.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “All-in-One Church Management Software for Streamlined Opera…”.
Time to Interactive: 17.8 s
17.8 sThe page becomes fully interactive after 17.8 s. Good is under 3.8 s.
Real-user INP: 380 ms
380 msReal visitors wait 380 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Largest content (LCP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 230 ms
230 msScripts block taps and scrolling for 230 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
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 357 ms to 387 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.07
0.07The layout barely moves while loading (CLS 0.07, good is under 0.1).
Images and page weight
Page weight: 6.5 MB in 110 requests
6.5 MBYour homepage downloads 6.5 MB in 110 requests on a phone: media 4.1 MB (1), scripts 1.9 MB (50) and fonts 237 KiB (5). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
66fea196625539b8440ffac9_Logo Type=Ministry Brands.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image below the first screen load straight away
1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.85 g of CO₂e: 221.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
SEO
Page is set to noindex
The robots meta tag says “noindex”: Google is told not to list this page at all.
Blocked from indexing
Google's crawler is blocked from indexing this page.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
34 internal links, 12 external
The homepage links to 34 pages on cloversites.com and 12 external pages.
6 checks passed
Meta description: 106 characters
Your meta description is 106 characters: “Unlock efficiency with Clover. Discover streamlined solutions for smooth business operations and payments.”.
One H1 headline
Your main headline reads: “See how one platform can amplify your church”.
Title: 65 characters
Your title is a healthy 65 characters: “Clover: Church Website Creator for Church Needs | Ministry Brands”.
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.ministrybrands.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (596 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ministrybrands.com/llms.txt (21 KiB, 40 links), a plain-text guide to the site for AI tools.
Other pages
9 pages share a meta description
https://www.ministrybrands.com/healthy-church-hub, https://www.ministrybrands.com/resources, https://www.ministrybrands.com/webinars, https://www.ministrybrands.com/ebooks, https://www.ministrybrands.com/podcasts and https://www.ministrybrands.com/church-plants and 3 others use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://www.ministrybrands.com/resources, https://www.ministrybrands.com/webinars, https://www.ministrybrands.com/ebooks, https://www.ministrybrands.com/podcasts and https://www.ministrybrands.com/blog 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 24 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
2 broken images
2 images failed to load on a phone, for example https://www.ministrybrands.com/assets/privacy-options-icon.svg.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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.
Thin social proof
Social proof on the homepage: 13 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 514 words of copy
The homepage carries about 514 words of visible text.
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Book your demo”, “Learn More” and “Book your Demo”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 5 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
28 cookies set on arrival
28Opening the homepage sets 28 cookies (measured from a US location before any click).
54 other companies contacted
Loading the homepage contacts 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 cloversites.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
- Webflow
- Analytics
- Google Tag Manager
- Hosting
- WP Engine
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on cloversites.com, including 22 speed issues, 5 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.