Website review, no card needed
srgseniorliving.com website review
Visit site (opens in a new tab)Reviewed 3 November 202643 issues · 93 checks
This review found 43 issues worth fixing on srgseniorliving.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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.2 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.4 s |
| Oct 24, 2026 | 4.3 s |
| Oct 31, 2026 | 4.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 135 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 131 ms |
| Jun 6, 2026 | 134 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 125 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 124 ms |
| Oct 3, 2026 | 125 ms |
| Oct 10, 2026 | 127 ms |
| Oct 17, 2026 | 126 ms |
| Oct 24, 2026 | 127 ms |
| Oct 31, 2026 | 129 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.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.9 s
4.5 s
5.2 s
Speed
Reduce unused JavaScript
7.0 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.
Use efficient cache lifetimes
3.9 s · 998 KiB50 files are served with short cache lifetimes, so returning visitors download them again (998 KiB).
Render-blocking requests
1.4 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 3.8 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 Tag Manager, Google CDN and boomchatweb.com and others), adding 21.8 MB and 2.3 s of main-thread time.
Vimeo adds 140 ms
140 msVimeo costs a phone 140 ms of main-thread work and 19.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.
Reduce unused CSS
600 ms · 132 KiBAbout 132 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.
Improve image delivery
200 ms · 511 KiB4 images could be 511 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Google Tag Manager adds 526 ms
526 msGoogle Tag Manager costs a phone 526 ms of main-thread work and 528 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 473 ms
473 msGoogle CDN costs a phone 473 ms of main-thread work and 736 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.
boomchatweb.com adds 468 ms
468 msboomchatweb.com costs a phone 468 ms of main-thread work and 266 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 348 ms. During a long task the page ignores taps.
talkfurther.com adds 292 ms
292 mstalkfurther.com costs a phone 292 ms of main-thread work and 427 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.
Minify JavaScript
150 ms · 38 KiB38 KiB could be saved by minifying JavaScript.
Legacy JavaScript
150 ms · 33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
25 KiB25 KiB could be saved by minifying CSS.
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: 11 ms
11 msYour server sent the HTML in 11 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.
First Contentful Paint: 9.3 s
9.3 sThe first text or image appears after 9.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 22.7 s
22.7 sYour largest element takes 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Senior living community in the USA”.
Time to Interactive: 29.6 s
29.6 sThe page becomes fully interactive after 29.6 s. Good is under 3.8 s.
Speed Index: 12.0 s
12.0 sVisually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 135 ms to 129 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-31, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 112 ms
112 msReal visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 488 ms
488 msReal visitors wait 488 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.8 MB in 220 requests
23.8 MBYour homepage downloads 23.8 MB in 220 requests on a phone: other files 19.3 MB (65), scripts 3.0 MB (93) and images 725 KiB (24). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (529 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.
1 image far larger than shown
333 KiB1 image is downloaded at several times the size a phone draws it, for example A9I9540-scaled.jpg at 2,560 px wide, shown at 350 px. Resized copies would save about 333 KiB.
About 6.7 g of CO₂ per visit
6.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.74 g of CO₂e: 808.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
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 (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
52 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: 52 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
Meta description is long (208 characters)
Your meta description is 208 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
146 internal links, 15 external
The homepage links to 146 pages on srgseniorliving.com and 15 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Senior Living Communities Designed to Enrich and Inspire”.
Title: 58 characters
Your title is a healthy 58 characters: “Senior Living & Retirement Communities | SRG Senior Living”.
Canonical URL set
The canonical URL is https://www.srgseniorliving.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, Organization, WebPage and WebSite.
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.srgseniorliving.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (1,464 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.srgseniorliving.com/llms.txt (8 KiB, 50 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.srgseniorliving.com/living-choices/the-club has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.srgseniorliving.com/management-services has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.srgseniorliving.com/living-choices/memory-care took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.
5 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.
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
3 broken images
3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=17501525&tm=gtm002&Ver=2&mid=c002f38d-f537-442a-8524-48f3c87a4ec7&bo=6&sid=09f388a0d76f11f1837d4db2251b1c8d&vid=09f381c0d76f11f1bd97b724a716dd14&vids=0&msclkid=N&pi=91.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
23 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
A 8-field form
Your longest form asks for 8 fields (5 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 742 words of copy
The homepage carries about 742 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “Learn More” and “Learn More About CARF”.
Analytics in place
Analytics detected: Google Tag Manager.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 2 of them by other companies (measured from a US location before any click).
45 other companies contacted
Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 srgseniorliving.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
- Hosting
- Fastly
Hiring
- Hiring
- 1 open role
- Job board
- careers page
- Careers page
- careers.srgseniorliving.com (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on srgseniorliving.com, including 21 speed issues, 4 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.