care.com website review

About 536 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

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

A phone's processor spends 5.9 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

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

The page has 2,107 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

6 third-party services load with your homepage (Accessibe Accessibility Overlay, mPulse and Other Google APIs/SDKs and others), adding 409 KiB and 150 ms of main-thread time.

About 24 KiB of CSS is downloaded but never applied on this page.

Desktop scores 76 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Log in Connecting families with quality, local caregivers ​…”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 2.5 MB in 93 requests on a phone: scripts 1.5 MB (48), images 646 KiB (13) and fonts 233 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

Some list items are not inside a list.

5 elements have a tabindex above 0, which scrambles the keyboard order.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 78 characters, so Google will cut it off around 60: “Care.com: Find Child Care, Babysitters, Senior Care, Pet Care and Housekeeping”.

There are 3 <h1> headlines (“Sarah”, “Allexus” and “Kelly”). One clear main headline is easier for people and search engines.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 282 pages on care.com and 11 external pages.

/app/vhp/get-started declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /app/vhp/get-started all use the title “Care.com: Find Child Care, Babysitters, Senior Care, Pet Care and Hou…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/about, /about/newsroom, /about/terms-of-use, /about/privacy-policy, /c and /app/pn-business and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

/app/vhp/get-started, /about, /careers, /c, /app/pn-business/camps and /business have no <h1> headline, so visitors and search engines get no clear main topic.

/app/vhp/get-started has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/about/newsroom, /about/terms-of-use and /about/privacy-policy took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5104288&tm=gtm002&Ver=2&mid=331ca3be-9b03-4502-b001-b3778dc751d7&bo=1&sid=54aba200c5b311f19866cbf7009b4a01&vid=54abbce0c5b311f1abfa9b0bbe078712&vids=1&msclkid=N&pi=918.

2 errors were logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

12 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

5 links go through two or more redirects, for example https://www.care.com/vis/auth/login.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

care.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

care.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 561 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 30 cookies (measured from a US location before any click).

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