Website review, no card needed

millersmerrymanor.com logo

millersmerrymanor.com website review

Visit site (opens in a new tab)Reviewed 3 November 202635 issues · 87 checks

This review found 35 issues worth fixing on millersmerrymanor.com, 12 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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.5 s1.3 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.3 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.5 s
Aug 29, 20261.4 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.5 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
89 ms73 msMay 16Oct 3180 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202676 ms
May 23, 202677 ms
May 30, 202680 ms
Jun 6, 202681 ms
Jun 13, 202679 ms
Jun 20, 202680 ms
Jun 27, 202678 ms
Jul 4, 202675 ms
Jul 11, 202676 ms
Jul 18, 202675 ms
Jul 25, 202675 ms
Aug 1, 202678 ms
Aug 8, 202678 ms
Aug 15, 202678 ms
Aug 22, 202679 ms
Aug 29, 202677 ms
Sep 5, 202675 ms
Sep 12, 202679 ms
Sep 19, 202683 ms
Sep 26, 202686 ms
Oct 3, 202687 ms
Oct 10, 202685 ms
Oct 17, 202682 ms
Oct 24, 202680 ms
Oct 31, 202680 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 millersmerrymanor.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. millersmerrymanor.com at 0.8 s0.8 s
  2. millersmerrymanor.com at 1.7 s1.7 s
  3. millersmerrymanor.com at 2.5 s2.5 s
  4. millersmerrymanor.com at 3.4 s3.4 s
  5. millersmerrymanor.com at 4.2 s4.2 s
  6. millersmerrymanor.com at 5.0 s5.0 s
  7. millersmerrymanor.com at 5.9 s5.9 s
  8. millersmerrymanor.com at 6.7 s6.7 s

Speed

9 to fix50
  • Use efficient cache lifetimes

    2.3 s · 3.5 MB

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

  • Reduce unused CSS

    1.2 s · 159 KiB

    About 159 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    900 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.

  • Reduce unused JavaScript

    450 ms · 204 KiB

    About 204 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Minify CSS

    450 ms · 54 KiB

    54 KiB could be saved by minifying CSS.

  • Improve image delivery

    418 KiB

    9 images could be 418 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, bc0a.com and Google Analytics and others), adding 1.6 MB and 166 ms of main-thread time.

  • bc0a.com adds 36 ms

    36 ms

    bc0a.com costs a phone 36 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.

  • 2 long tasks on the main thread

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

  • Minify JavaScript

    36 KiB

    36 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    26 KiB

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

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 175 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 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: 8.6 s

    8.6 s

    Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.1 s).

  • Speed Index: 7.7 s

    7.7 s

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

  • Time to Interactive: 9.4 s

    9.4 s

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

  • Cumulative Layout Shift: 0.318

    0.318

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

  • Real-user TTFB: 986 ms

    986 ms

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 2 images without width and height

    2 images 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-31, real Chrome visitors' tap response (inp) went from 76 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 80 ms

    80 ms

    Real visitors wait 80 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.4 s

    1.4 s

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

  • Total Blocking Time: 11 ms

    11 ms

    Scripts block the page for only 11 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 5.1 MB in 54 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 54 requests on a phone: images 4.2 MB (28), scripts 383 KiB (8) and fonts 269 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 11 images below the first screen load straight away

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

  • 9 images far larger than shown

    317 KiB

    9 images are downloaded at several times the size a phone draws them, for example Home_Page_–_Millers_Senior_Living_Community_Assisted_Living. at 1,280 px wide, shown at 318 px. Resized copies would save about 317 KiB.

  • About 1.4 g of CO₂ per visit

    1.43 g

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

6 to fixGoogle 8992
  • 8 text elements with low contrast

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

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • No H1 headline

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

  • Meta description is long (217 characters)

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

  • 10 links with vague text

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 60 internal links, 7 external

    The homepage links to 60 pages on millersmerrymanor.com and 7 external pages.

5 checks passed
  • Title: 59 characters

    Your title is a healthy 59 characters: “Senior Rehabilitation and Healthcare | Miller's Merry Manor”.

  • Canonical URL set

    The canonical URL is https://millersmerrymanor.com/.

  • Structured data in place

    Structured data found: WebPage.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://millersmerrymanor.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

1 to fix98
  • 7 pages share a meta description

    https://millersmerrymanor.com/about/history, https://millersmerrymanor.com/about/news, https://millersmerrymanor.com/about/testimonials, https://millersmerrymanor.com/about/community-outreach, https://millersmerrymanor.com/about/faqs and https://millersmerrymanor.com/rehab-services/real-life-rehab and 1 other use the same meta description. A description written for each page earns more clicks.

  • 11 pages slow to respond

    https://millersmerrymanor.com/about/testimonials, https://millersmerrymanor.com/about/community-outreach, https://millersmerrymanor.com/about/faqs, https://millersmerrymanor.com/rehab-services, https://millersmerrymanor.com/rehab-services/real-life-rehab and https://millersmerrymanor.com/rehab-services/physical-therapy and 5 others 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.

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

1 to fixGoogle 10093
  • 5 small tap targets

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

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

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 524 words of copy

    The homepage carries about 524 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: “Contact Us” and “Schedule a Tour”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Schedule a Tour” and “Apply Now”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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
  • 2 trackers load before any consent

    2

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

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on millersmerrymanor.com, including 17 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