Website review, no card needed

heritageofgreenhills.com logo

heritageofgreenhills.com website review

Visit site (opens in a new tab)Reviewed 3 November 202644 issues · 86 checks

This review found 44 issues worth fixing on heritageofgreenhills.com, 15 of them high impact, across 86 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
3.7 s2.9 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.6 s
May 30, 20263.6 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 8, 20263.6 s
Aug 29, 20263.1 s
Oct 31, 20263.0 s

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 heritageofgreenhills.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. heritageofgreenhills.com at 1.2 s1.2 s
  2. heritageofgreenhills.com at 2.4 s2.4 s
  3. heritageofgreenhills.com at 3.6 s3.6 s
  4. heritageofgreenhills.com at 4.7 s4.7 s
  5. heritageofgreenhills.com at 5.9 s5.9 s
  6. heritageofgreenhills.com at 7.1 s7.1 s
  7. heritageofgreenhills.com at 8.3 s8.3 s
  8. heritageofgreenhills.com at 9.5 s9.5 s

Speed

12 to fix22
  • Reduce unused JavaScript

    8.3 s · 1.5 MB

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

  • Render-blocking requests

    2.8 s

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

  • Use efficient cache lifetimes

    1.4 s · 254 KiB

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

  • Mobile performance score: 22

    22/100

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

  • Main-thread work: 5.6 s

    A phone's processor spends 5.6 s on main-thread work while loading, 3.5 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 (instabot.io, Google Tag Manager and Google CDN and others), adding 13.9 MB and 2.3 s of main-thread time.

  • instabot.io adds 719 ms

    719 ms

    instabot.io costs a phone 719 ms of main-thread work and 11.5 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.

  • Improve image delivery

    350 ms · 735 KiB

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

  • Font display

    800 ms

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

  • Google Tag Manager adds 623 ms

    623 ms

    Google Tag Manager costs a phone 623 ms of main-thread work and 816 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 CDN adds 574 ms

    574 ms

    Google CDN costs a phone 574 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    52 KiB

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

  • Reduce unused CSS

    44 KiB

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 18 ms

    18 ms

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

Core Web Vitals

10 to fix0
  • 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 CLS: 0.70

    0.70

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

  • Largest Contentful Paint: 23.6 s

    23.6 s

    Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 18.2 s

    18.2 s

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

  • Time to Interactive: 93.6 s

    93.6 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.371

    0.371

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

1 checks passed
  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

Images and page weight

2 to fix63
  • Page weight: 18.8 MB in 184 requests

    18.8 MB

    Your homepage downloads 18.8 MB in 184 requests on a phone: other files 12.7 MB (32), scripts 3.1 MB (64) and images 2.2 MB (30). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

    6 images further down the page (501 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images in older formats

    5 images (477 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 5.3 g of CO₂ per visit

    5.32 g

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

8 to fixGoogle 9091
  • 7 text elements with low contrast

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

    All page content should be contained by landmarks: 18 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.

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

  • 6 links without text

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

  • 2 form fields without a label

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 8576
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (87 characters)

    Your title is 87 characters, so Google will cut it off around 60: “Independent Senior Living & Personal Care Serving the Shillington & Reading Areas in PA”.

  • Meta description is long (173 characters)

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

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 98 internal links, 10 external

    The homepage links to 98 pages on heritageofgreenhills.com and 10 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://heritageofgreenhills.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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://heritageofgreenhills.com/sitemap_index.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 (772 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://heritageofgreenhills.com/llms.txt (2 KiB, 15 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://heritageofgreenhills.com/resident-satisfaction-survey is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://heritageofgreenhills.com/our-team, https://heritageofgreenhills.com/reviews, https://heritageofgreenhills.com/resident-benefit-fund, https://heritageofgreenhills.com/golf-outing, https://heritageofgreenhills.com/heritage-casino-night and https://heritageofgreenhills.com/resident-satisfaction-survey and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://heritageofgreenhills.com/about, https://heritageofgreenhills.com/our-team, https://heritageofgreenhills.com/reviews, https://heritageofgreenhills.com/resources-qa, https://heritageofgreenhills.com/careers and https://heritageofgreenhills.com/resident-benefit-fund and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://heritageofgreenhills.com/golf-outing, https://heritageofgreenhills.com/resident-satisfaction-survey, https://heritageofgreenhills.com/lifestyle, https://heritageofgreenhills.com/amenities, https://heritageofgreenhills.com/dining and https://heritageofgreenhills.com/photo-gallery-2 and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

  • 1 low-resolution image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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 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 668 words of copy

    The homepage carries about 668 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: “Call Us At: (484) 269-5100” and “Schedule a Tour”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Call Us At: (484) 269-5100”, “Contact Us” and “Schedule a Tour”.

  • Social proof on the page

    Social proof on the homepage: 22 testimonial or review blocks and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel 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
  • 4 trackers load before any consent

    4

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

    12

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 heritageofgreenhills.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 Tag Manager

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 heritageofgreenhills.com, including 22 speed issues, 4 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