Website review, no card needed

thecypressofraleigh.com logo

thecypressofraleigh.com website review

Visit site (opens in a new tab)Reviewed 20 October 202629 issues · 83 checks

This review found 29 issues worth fixing on thecypressofraleigh.com, 12 of them high impact, across 83 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

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

How it loaded on a phone

  1. thecypressofraleigh.com at 1.0 s1.0 s
  2. thecypressofraleigh.com at 2.1 s2.1 s
  3. thecypressofraleigh.com at 3.1 s3.1 s
  4. thecypressofraleigh.com at 4.1 s4.1 s
  5. thecypressofraleigh.com at 5.1 s5.1 s
  6. thecypressofraleigh.com at 6.2 s6.2 s
  7. thecypressofraleigh.com at 7.2 s7.2 s
  8. thecypressofraleigh.com at 8.2 s8.2 s

Speed

10 to fix42
  • Reduce unused JavaScript

    8.1 s · 1.3 MB

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

  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 5.9 s

    A phone's processor spends 5.9 s on main-thread work while loading, 3.4 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, talkfurther.com and Google Tag Manager and others), adding 5.0 MB and 2.2 s of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 722 KiB

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

  • Google CDN adds 569 ms

    569 ms

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

  • talkfurther.com adds 493 ms

    493 ms

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

  • website-files.com adds 313 ms

    313 ms

    website-files.com costs a phone 313 ms of main-thread work and 2.2 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 373 ms

    373 ms

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

  • Improve image delivery

    150 ms · 67 KiB

    3 images could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    26 KiB

    About 26 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 12.1 s

    12.1 s

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

  • Largest Contentful Paint: 23.0 s

    23.0 s

    Your largest element takes 23.0 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: 26.7 s

    26.7 s

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

  • Speed Index: 13.9 s

    13.9 s

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

  • Total Blocking Time: 513 ms

    513 ms

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 94 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

    -2%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 100 ms

    100 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 352 ms

    352 ms

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

  • Cumulative Layout Shift: 0.034

    0.034

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

Images and page weight

2 to fix64
  • Page weight: 6.0 MB in 111 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 111 requests on a phone: scripts 2.8 MB (38), images 2.2 MB (19) and fonts 510 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    64eca9b2a3b5e5aafbccd218_The Cypress.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).

  • About 1.7 g of CO₂ per visit

    1.70 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 203.4 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

4 to fixGoogle 9496
  • 24 text elements with low contrast

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

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

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

  • 11 form fields without a label

    11 form fields have 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.

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Meta description is long (166 characters)

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

  • 5 links with vague text

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

  • 53 internal links, 4 external

    The homepage links to 53 pages on thecypressofraleigh.com and 4 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “The Cypress of Raleigh”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “The Cypress of Raleigh | Luxury Retirement Living NC”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness.

  • 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.thecypressofraleigh.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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (520 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.thecypressofraleigh.com/llms.txt (5 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.thecypressofraleigh.com/gallery, whose canonical is https://www.thecypressofraleigh.com/gallery/page. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 25 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.

  • 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

Google 96100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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.

  • 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 11-field form

    Your longest form asks for 11 fields (8 required). Every extra field lowers completion.

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

    The homepage carries about 472 words of visible text.

5 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “contact”, “Learn more” and “CONTACT”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 33 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on thecypressofraleigh.com, including 16 speed issues, 2 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

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
thecypressofraleigh.com website review: scores and fixes