Website review, no card needed

lssliving.org logo

lssliving.org website review

Visit site (opens in a new tab)Reviewed 29 October 202640 issues · 74 checks

This review found 40 issues worth fixing on lssliving.org, 20 of them high impact, across 74 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
2.3 s2.1 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
157 ms121 msMay 9Oct 24152 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026125 ms
May 16, 2026127 ms
May 23, 2026130 ms
May 30, 2026129 ms
Jun 6, 2026128 ms
Jun 13, 2026129 ms
Jun 20, 2026128 ms
Jun 27, 2026127 ms
Jul 4, 2026127 ms
Jul 11, 2026126 ms
Jul 18, 2026131 ms
Jul 25, 2026134 ms
Aug 1, 2026136 ms
Aug 8, 2026135 ms
Aug 15, 2026130 ms
Aug 22, 2026129 ms
Aug 29, 2026131 ms
Sep 5, 2026133 ms
Sep 12, 2026138 ms
Sep 19, 2026144 ms
Sep 26, 2026151 ms
Oct 3, 2026153 ms
Oct 10, 2026153 ms
Oct 17, 2026153 ms
Oct 24, 2026152 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 lssliving.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lssliving.org at 4.2 s4.2 s
  2. lssliving.org at 8.4 s8.4 s
  3. lssliving.org at 12.6 s12.6 s
  4. lssliving.org at 16.7 s16.7 s
  5. lssliving.org at 20.9 s20.9 s
  6. lssliving.org at 25.1 s25.1 s
  7. lssliving.org at 29.3 s29.3 s
  8. lssliving.org at 33.5 s33.5 s

Speed

12 to fix36
  • Reduce unused JavaScript

    5.6 s · 1.4 MB

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

  • Use efficient cache lifetimes

    3.0 s · 518 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 4.8 s

    A phone's processor spends 4.8 s on main-thread work while loading, 2.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 (Google Tag Manager, Google CDN and Facebook and others), adding 2.7 MB and 1.7 s of main-thread time.

  • Improve image delivery

    1.5 MB

    21 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 808 ms

    808 ms

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

    600 ms · 130 KiB

    About 130 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 383 ms

    383 ms

    Google CDN costs a phone 383 ms of main-thread work and 741 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 267 ms. During a long task the page ignores taps.

  • Vimeo adds 59 ms

    59 ms

    Vimeo costs a phone 59 ms of main-thread work and 662 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

    13 KiB

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

  • Largest Contentful Paint: 23.2 s

    23.2 s

    Your largest element takes 23.2 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Speed Index: 20.2 s

    20.2 s

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

  • Time to Interactive: 28.9 s

    28.9 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Tap response (INP) got 21% slower for real visitors

    +21%

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

  • Real-user TTFB: 922 ms

    922 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 5 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 136 ms

    136 ms

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

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

    1.3 s

    Real visitors see the first content after 1.3 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 fix43
  • Page weight: 6.5 MB in 144 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 144 requests on a phone: scripts 2.9 MB (41), images 1.9 MB (40) and fonts 1.1 MB (4). Under 2 MB keeps phones on slow connections fast.

  • 11 images far larger than shown

    861 KiB

    11 images are downloaded at several times the size a phone draws them, for example Hero_Images_Purpose_1280-x-800.webp at 5,333 px wide, shown at 390 px. Resized copies would save about 861 KiB.

  • 18 images below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.84 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8892
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 5 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 links without text

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 9285
  • No H1 headline

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

6 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “EverTrue has guided older adults for over 166 years. Explore independent living, assisted living, memory care, and at-h…”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “EverTrue | Senior Living in Missouri, Illinois, and Pennsylvania”.

  • Canonical URL set

    The canonical URL is https://www.evertrueliving.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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.evertrueliving.org/sitemap.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    10%

    A phone browser shows 538 words, but the HTML your server sends has only 56. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

  • Organization data: 6 of 6 facts

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

  • llms.txt published

    The site publishes https://www.evertrueliving.org/llms.txt (170 KiB, 532 links), a plain-text guide to the site for AI tools.

Best practices

3 to fixGoogle 7385
  • 4 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.staticfiles.io/public/fontawesome/css/font-awesome-dynamic.min.css.gz?2.5.51'…”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 538 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 cookies, 3 of them by other companies (measured from a US location before any click).

  • 42 other companies contacted

    Loading the homepage contacts 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 lssliving.org, 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
Vue.js
Analytics
Google Tag Manager
Hosting
Network Solutions Hosting

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on lssliving.org, including 21 speed issues, 3 SEO issues and 4 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