Website review, no card needed

clovelakes.com logo

clovelakes.com website review

Visit site (opens in a new tab)Reviewed 22 October 202647 issues · 92 checks

This review found 47 issues worth fixing on clovelakes.com, 19 of them high impact, across 92 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s1.7 sMay 2Sep 51.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.2 s
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jul 4, 20262.2 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
99 ms76 msMay 2Sep 589 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202680 ms
May 9, 202680 ms
May 16, 202680 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202681 ms
Jun 20, 202681 ms
Jun 27, 202687 ms
Jul 4, 202689 ms
Jul 25, 202696 ms
Aug 1, 202695 ms
Aug 8, 202679 ms
Aug 15, 202681 ms
Aug 22, 202679 ms
Aug 29, 202681 ms
Sep 5, 202689 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

Full-page screenshot of clovelakes.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. clovelakes.com at 0.6 s0.6 s
  2. clovelakes.com at 1.1 s1.1 s
  3. clovelakes.com at 1.7 s1.7 s
  4. clovelakes.com at 2.3 s2.3 s
  5. clovelakes.com at 2.8 s2.8 s
  6. clovelakes.com at 3.4 s3.4 s
  7. clovelakes.com at 4.0 s4.0 s
  8. clovelakes.com at 4.5 s4.5 s

Speed

12 to fix25
  • Improve image delivery

    9.1 s · 3.0 MB

    16 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.1 s faster on a phone.

  • Reduce unused JavaScript

    5.2 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.

  • Mobile performance score: 25

    25/100

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

  • Main-thread work: 4.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 2.2 MB and 1.5 s of main-thread time.

  • Render-blocking requests

    900 ms

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

  • Reduce unused CSS

    600 ms · 90 KiB

    About 90 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Google CDN adds 498 ms

    498 ms

    Google CDN costs a phone 498 ms of main-thread work and 755 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.

  • Google Tag Manager adds 476 ms

    476 ms

    Google Tag Manager costs a phone 476 ms of main-thread work and 615 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.

  • Accessibe Accessibility Overlay adds 395 ms

    395 ms

    Accessibe Accessibility Overlay costs a phone 395 ms of main-thread work and 243 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

    300 ms · 18 KiB

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

  • tidio.co adds 109 ms

    109 ms

    tidio.co costs a phone 109 ms of main-thread work and 515 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.

  • 20 long tasks on the main thread

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

  • Phones get a much slower page than desktops

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

  • Use efficient cache lifetimes

    8 KiB

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

  • 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: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix100
  • 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.5 s

    8.5 s

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

  • Largest Contentful Paint: 33.0 s

    33.0 s

    Your largest element takes 33.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Lifestyle Image”.

  • Time to Interactive: 33.6 s

    33.6 s

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

  • Speed Index: 11.3 s

    11.3 s

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

  • Cumulative Layout Shift: 0.332

    0.332

    The layout shifts by 0.332 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user TTFB: 888 ms

    888 ms

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

  • Total Blocking Time: 545 ms

    545 ms

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

  • 27 images without width and height

    27 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    -4%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.09

    0.09

    For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

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

Images and page weight

4 to fix33
  • Page weight: 8.6 MB in 159 requests

    8.6 MB

    Your homepage downloads 8.6 MB in 159 requests on a phone: images 4.8 MB (59), scripts 2.2 MB (31) and fonts 1.0 MB (34). Under 2 MB keeps phones on slow connections fast.

  • 17 images far larger than shown

    2.3 MB

    17 images are downloaded at several times the size a phone draws them, for example rehab-5.jpg at 1,920 px wide, shown at 375 px. Resized copies would save about 2.3 MB.

  • 22 images in older formats

    22 images (4.4 MB) 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.

  • 11 images below the first screen load straight away

    11 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.4 g of CO₂ per visit

    2.43 g

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

Accessibility

9 to fixGoogle 7988
  • autocomplete attribute must be used correctly (6 elements)

    autocomplete attribute must be used correctly: 6 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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 (7 elements)

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

  • 10 form fields without a label

    10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 8 links without text

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

  • 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 (h1 → h3), 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7777
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 12 H1 headlines

    There are 12 <h1> headlines (“”, “Short-Term Rehab” and “Short-Term Rehab”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://redbankrehab.com/?sitemapindex.xml, so Google discovers your pages only by following links.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 36 internal links, 6 external

    The homepage links to 36 pages on clovelakes.com and 6 external pages.

4 checks passed
  • Title: 60 characters

    Your title is a healthy 60 characters: “Homepage - Clove Lakes Health Care and Rehabilitation Center”.

  • Canonical URL set

    The canonical URL is https://clovelakes.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • 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://clovelakes.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (558 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 4 linked pages are broken

    Your homepage links to https://clovelakes.com/es, https://clovelakes.com/ru, https://clovelakes.com/zh and https://clovelakes.com/services, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 8 pages without a meta description

    https://clovelakes.com/covid, https://clovelakes.com/contact, https://clovelakes.com/about, https://clovelakes.com/services-specialties, https://clovelakes.com/experiences and https://clovelakes.com/careers and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://clovelakes.com/privacy-policy and https://clovelakes.com/disclosures have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://clovelakes.com/covid has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://clovelakes.com/privacy-policy took over 3 s to send its HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

    2 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 615 words of copy

    The homepage carries about 615 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SCHEDULE A TOUR”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Learn More”, “Contact” and “Schedule a Tour”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 21 testimonial or review blocks, 2 customer or partner logos, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 clovelakes.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
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on clovelakes.com, including 21 speed issues, 5 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25