Website review, no card needed

capricommunities.com logo

capricommunities.com website review

Visit site (opens in a new tab)Reviewed 28 October 202641 issues · 93 checks

This review found 41 issues worth fixing on capricommunities.com, 16 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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
1.4 s1.3 sMay 9Oct 241.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.4 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
106 ms93 msMay 9Oct 2495 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202698 ms
May 16, 2026101 ms
May 23, 2026101 ms
May 30, 2026104 ms
Jun 6, 2026103 ms
Jun 13, 2026104 ms
Jun 20, 2026103 ms
Jun 27, 202697 ms
Jul 4, 2026100 ms
Jul 11, 2026102 ms
Jul 18, 2026104 ms
Jul 25, 2026104 ms
Aug 1, 2026103 ms
Aug 8, 202697 ms
Aug 15, 202695 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202697 ms
Sep 12, 2026101 ms
Sep 19, 2026103 ms
Sep 26, 2026102 ms
Oct 3, 2026100 ms
Oct 10, 202697 ms
Oct 17, 202695 ms
Oct 24, 202695 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 capricommunities.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. capricommunities.com at 0.4 s0.4 s
  2. capricommunities.com at 0.8 s0.8 s
  3. capricommunities.com at 1.1 s1.1 s
  4. capricommunities.com at 1.5 s1.5 s
  5. capricommunities.com at 1.9 s1.9 s
  6. capricommunities.com at 2.3 s2.3 s
  7. capricommunities.com at 2.6 s2.6 s
  8. capricommunities.com at 3.0 s3.0 s

Speed

14 to fix28
  • Reduce unused JavaScript

    3.3 s · 1.7 MB

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

  • Render-blocking requests

    3.4 s

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

  • Improve image delivery

    1.5 s · 568 KiB

    5 images could be 568 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 28

    28/100

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

  • Main-thread work: 8.9 s

    A phone's processor spends 8.9 s on main-thread work while loading, 4.9 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 (YouTube, Google Tag Manager and talkfurther.com and others), adding 3.3 MB and 3.5 s of main-thread time.

  • YouTube adds 810 ms

    810 ms

    YouTube costs a phone 810 ms of main-thread work and 979 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 764 ms

    764 ms

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

  • talkfurther.com adds 699 ms

    699 ms

    talkfurther.com costs a phone 699 ms of main-thread work and 439 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.

  • Use efficient cache lifetimes

    50 ms · 646 KiB

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

  • Google CDN adds 601 ms

    601 ms

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

  • Reduce unused CSS

    340 ms · 182 KiB

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

  • 20 long tasks on the main thread

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

  • Google Maps adds 245 ms

    245 ms

    Google Maps costs a phone 245 ms of main-thread work and 317 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.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 72 but mobile only 28. 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: 5 ms

    5 ms

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

Core Web Vitals

8 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.

  • Largest Contentful Paint: 14.9 s

    14.9 s

    Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “enjoy life”.

  • Time to Interactive: 31.6 s

    31.6 s

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

  • Total Blocking Time: 2.7 s

    2.7 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Speed Index: 10.0 s

    10.0 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

4 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (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.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 5.5 MB in 172 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 172 requests on a phone: scripts 3.5 MB (70), images 923 KiB (21) and fonts 454 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Age-is-a-Matter-of-Mind.jpg 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 far larger than shown

    68 KiB

    1 image is downloaded at several times the size a phone draws it, for example TopChoice_microsites-Logo-03-696x1024.png at 390 px wide, shown at 74 px. Resized copies would save about 68 KiB.

  • 1 image in older formats

    1 image (207 KiB) is 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.56 g

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

Accessibility

7 to fixGoogle 9292
  • 13 text elements with low contrast

    13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (12 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9286
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Wisconsin Senior Living | Retirement Communities Milwaukee & Madison”.

  • Meta description is long (188 characters)

    Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 11 links with vague text

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

  • 74 internal links, 7 external

    The homepage links to 74 pages on capricommunities.com and 7 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “enjoy life”.

  • Canonical URL set

    The canonical URL is https://www.capricommunities.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.capricommunities.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://www.capricommunities.com/llms.txt (195 KiB, 640 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 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.

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

Best practices

3 to fixGoogle 6976
  • 3 broken images

    3 images failed to load on a phone, for example https://jelly.mdhv.io/v1/star.gif?pid=owJ96ZNX1B5HFF3fDvBkgwdpdtzt&src=mh&evt=hi.

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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_TUNNEL_CONNECTION_FAILED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    6 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 701 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Schedule a Tour”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Schedule a Tour”, “Contact” and “Schedule A Tour”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 29 other companies contacted

    Loading the homepage contacts 29 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 capricommunities.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

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 41 issues on capricommunities.com, including 22 speed issues, 3 SEO issues 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

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