Website review, no card needed

ambercare.com logo

ambercare.com website review

Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 79 checks

This review found 34 issues worth fixing on ambercare.com, 13 of them high impact, across 79 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
3.8 s2.7 sMay 9Oct 243.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20263.0 s
Jun 13, 20263.2 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.3 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.4 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.6 s
Sep 19, 20263.7 s
Sep 26, 20263.6 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
97 ms79 msMay 9Oct 2490 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202688 ms
May 16, 202688 ms
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202686 ms
Jun 13, 202685 ms
Jun 20, 202685 ms
Jun 27, 202685 ms
Jul 4, 202683 ms
Jul 11, 202681 ms
Jul 18, 202683 ms
Jul 25, 202686 ms
Aug 1, 202687 ms
Aug 8, 202691 ms
Aug 15, 202687 ms
Aug 22, 202684 ms
Aug 29, 202685 ms
Sep 5, 202687 ms
Sep 12, 202688 ms
Sep 19, 202694 ms
Sep 26, 202695 ms
Oct 3, 202694 ms
Oct 10, 202694 ms
Oct 17, 202691 ms
Oct 24, 202690 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 ambercare.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ambercare.com at 0.4 s0.4 s
  2. ambercare.com at 0.8 s0.8 s
  3. ambercare.com at 1.1 s1.1 s
  4. ambercare.com at 1.5 s1.5 s
  5. ambercare.com at 1.9 s1.9 s
  6. ambercare.com at 2.3 s2.3 s
  7. ambercare.com at 2.6 s2.6 s
  8. ambercare.com at 3.0 s3.0 s

Speed

6 to fix48
  • Use efficient cache lifetimes

    1.8 s · 2.1 MB

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

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 48

    48/100

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

  • Improve image delivery

    150 ms · 1.3 MB

    2 images could be 1.3 MB 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.

  • Reduce unused JavaScript

    450 ms · 72 KiB

    About 72 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.

  • Reduce unused CSS

    300 ms · 33 KiB

    About 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, datatables.net and Google Analytics), adding 182 KiB and 153 ms of main-thread time.

  • Minify JavaScript

    150 ms · 11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Font display

    150 ms

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

  • 3 long tasks on the main thread

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

  • Minify CSS

    7 KiB

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

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

8 to fix67
  • 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 LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Largest Contentful Paint: 9.2 s

    9.2 s

    Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We're Here to Help You Maintain Your Health and Independenc…”.

  • Cumulative Layout Shift: 0.644

    0.644

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

  • Time to Interactive: 9.7 s

    9.7 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Speed Index: 3.5 s

    3.5 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

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

3 checks passed
  • Real-user INP: 81 ms

    81 ms

    Real visitors wait 81 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.

  • Total Blocking Time: 65 ms

    65 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 39 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 39 requests on a phone: images 1.9 MB (6), scripts 278 KiB (17) and fonts 76 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.66 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9594
  • 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.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 4 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8570
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (6 characters)

    Your title is only 6 characters: “Home -”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “We're Here to Help You Maintain Your Health and I…”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 65 internal links, 6 external

    The homepage links to 65 pages on ambercare.com and 6 external pages.

3 checks passed
  • Canonical URL set

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

  • 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://ambercare.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://ambercare.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.

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

Other pages

1 to fix95
  • 13 pages without a meta description

    https://ambercare.com/about-us-2, https://ambercare.com/mission-and-values, https://ambercare.com/booking, https://ambercare.com/hospice, https://ambercare.com/what-is-hospice and https://ambercare.com/ten-myths-about-hospice-care and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://ambercare.com/mission-and-values and https://ambercare.com/our-leadership-team took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 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 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9682
  • 1 broken image

    1 image failed to load on a phone, for example https://ambercare.com/.

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

4 to fix57
  • 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.

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

  • Only about 157 words

    The homepage has only about 157 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Request Care” and “Join Our Team”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

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.

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

  • 4 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2021.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Fiberpipe

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on ambercare.com, including 14 speed issues, 6 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