Website review, no card needed

mather.com logo

mather.com website review

Visit site (opens in a new tab)Reviewed 19 November 202642 issues · 88 checks

This review found 42 issues worth fixing on mather.com, 18 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
4.1 s2.3 sMay 30Nov 143.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.0 s
Jun 6, 20263.1 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20262.8 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20263.0 s
Sep 26, 20263.2 s
Oct 3, 20263.4 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Oct 24, 20263.8 s
Oct 31, 20263.7 s
Nov 7, 20263.6 s
Nov 14, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
295 ms217 msMay 30Nov 14283 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026226 ms
Jun 6, 2026233 ms
Jun 13, 2026229 ms
Jun 20, 2026237 ms
Jun 27, 2026238 ms
Jul 4, 2026247 ms
Jul 11, 2026254 ms
Jul 18, 2026244 ms
Jul 25, 2026236 ms
Aug 1, 2026231 ms
Aug 8, 2026233 ms
Aug 15, 2026237 ms
Aug 22, 2026260 ms
Aug 29, 2026269 ms
Sep 5, 2026275 ms
Sep 12, 2026286 ms
Sep 19, 2026282 ms
Sep 26, 2026285 ms
Oct 3, 2026280 ms
Oct 10, 2026260 ms
Oct 17, 2026263 ms
Oct 24, 2026263 ms
Oct 31, 2026264 ms
Nov 7, 2026263 ms
Nov 14, 2026283 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 mather.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mather.com at 1.1 s1.1 s
  2. mather.com at 2.2 s2.2 s
  3. mather.com at 3.3 s3.3 s
  4. mather.com at 4.4 s4.4 s
  5. mather.com at 5.5 s5.5 s
  6. mather.com at 6.6 s6.6 s
  7. mather.com at 7.7 s7.7 s
  8. mather.com at 8.8 s8.8 s

Speed

10 to fix39
  • Render-blocking requests

    5.6 s

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

  • Improve image delivery

    2.7 s · 704 KiB

    7 images could be 704 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

  • Mobile performance score: 39

    39/100

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

  • Reduce unused JavaScript

    900 ms · 602 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, pcdn.co and Facebook and others), adding 3.5 MB and 881 ms of main-thread time.

  • Reduce unused CSS

    750 ms · 151 KiB

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

  • Use efficient cache lifetimes

    600 ms · 254 KiB

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

  • Google Tag Manager adds 488 ms

    488 ms

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

  • pcdn.co adds 181 ms

    181 ms

    pcdn.co costs a phone 181 ms of main-thread work and 2.4 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.

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 46 KiB

    Polyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    150 ms · 17 KiB

    17 KiB could be saved by minifying CSS.

  • Minify JavaScript

    150 ms · 17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

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

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 830 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

11 to fix33
  • 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.28

    0.28

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

  • Real-user FCP: 3.1 s

    3.1 s

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 12.0 s

    12.0 s

    Your largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SOME moments CAN’T BE DESCRIBED IN WORDS. Discovering Ways …”. Most of its time is resource load delay (5.7 s).

  • Speed Index: 16.3 s

    16.3 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Time to Interactive: 13.1 s

    13.1 s

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

  • Cumulative Layout Shift: 0.259

    0.259

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Total Blocking Time: 230 ms

    230 ms

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

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

    +19%

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

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

    +15%

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

1 checks passed
  • Real-user INP: 173 ms

    173 ms

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

Images and page weight

3 to fix53
  • Page weight: 11.1 MB in 135 requests

    11.1 MB

    Your homepage downloads 11.1 MB in 135 requests on a phone: media 7.5 MB (2), images 1.8 MB (37) and scripts 1.5 MB (56). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    306 KiB

    1 image is downloaded at several times the size a phone draws it, for example 2026_09_09_Mather_SetUp1-Gilda_0084-Edit-TEXT-1-scaled-1.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 306 KiB.

  • 2 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (439 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 3.1 g of CO₂ per visit

    3.14 g

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

Accessibility

5 to fixGoogle 8291
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

  • [role="img"] and [role="image"] elements must have alternative text (1 element)

    [role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 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

4 to fixGoogle 7778
  • No meta description

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

  • Title is short (25 characters)

    Your title is only 25 characters: “Ways to Age Well | Mather”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 63 internal links, 5 external

    The homepage links to 63 pages on mather.com and 5 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Some moments can’t be described in words.”.

  • Canonical URL set

    The canonical URL is https://www.mather.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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.mather.com/sitemap_index.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.

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

  • llms.txt published

    The site publishes https://www.mather.com/llms.txt (8 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 7 pages without a meta description

    https://www.mather.com/about-us/our-leadership, https://www.mather.com/irbicouncil, https://www.mather.com/awards, https://www.mather.com/about-us/continuwell, https://www.mather.com/category/news-press-awards/in-the-news and https://www.mather.com/category/news-press-awards/press-release and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.mather.com/agehasanswers has no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages slow to respond

    https://www.mather.com/jobs, https://www.mather.com/jobs/benefits, https://www.mather.com/about-us/our-leadership, https://www.mather.com/our-history, https://www.mather.com/irbicouncil and https://www.mather.com/awards and 8 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 27 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

2 to fixGoogle 7391
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “The source list for the Content Security Policy directive 'script-src' contains an invalid source: '*js.hsforms.net'. I…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    6 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 327 words of visible text.

5 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”, “Contact Us” and “Learn More”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

    5

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

  • 10 cookies set on arrival

    10

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 mather.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 Analytics | Google Tag Manager
Hosting
AWS

Hiring

Hiring
3 open roles
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on mather.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

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