Website review, no card needed

sittercity.com logo

sittercity.com website review

Visit site (opens in a new tab)Reviewed 20 November 202623 issues · 81 checks

This review found 23 issues worth fixing on sittercity.com, 7 of them high impact, across 81 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.5 s1.4 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
166 ms148 msMay 30Nov 14152 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026154 ms
Jun 6, 2026156 ms
Jun 13, 2026162 ms
Jun 20, 2026163 ms
Jun 27, 2026164 ms
Jul 4, 2026163 ms
Jul 11, 2026161 ms
Jul 18, 2026155 ms
Jul 25, 2026153 ms
Aug 1, 2026151 ms
Aug 8, 2026150 ms
Aug 15, 2026152 ms
Aug 22, 2026153 ms
Aug 29, 2026154 ms
Sep 5, 2026154 ms
Sep 12, 2026154 ms
Sep 19, 2026154 ms
Sep 26, 2026156 ms
Oct 3, 2026159 ms
Oct 10, 2026160 ms
Oct 17, 2026159 ms
Oct 24, 2026156 ms
Oct 31, 2026154 ms
Nov 7, 2026154 ms
Nov 14, 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 sittercity.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix75
  • Reduce unused JavaScript

    1.3 s · 237 KiB

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

  • Use efficient cache lifetimes

    1.1 s · 188 KiB

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

  • Mobile performance score: 75

    75/100

    Your mobile performance score is 75. 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.

  • ctfassets.net adds 0 ms

    0 ms

    ctfassets.net costs a phone 0 ms of main-thread work and 414 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (dynatrace.com, Optanon and Sift Science and others), adding 793 KiB and 289 ms of main-thread time.

  • Improve image delivery

    150 ms · 209 KiB

    16 images could be 209 KiB 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.

  • Legacy JavaScript

    150 ms · 9 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 107 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    12 KiB

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

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

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 7.3 s

    7.3 s

    Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Smiling babysitters and children”.

  • Time to Interactive: 7.4 s

    7.4 s

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

  • Real-user CLS: 0.11

    0.11

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

  • Real-user TTFB: 813 ms

    813 ms

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

  • 20 images without width and height

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

  • Speed Index: 3.7 s

    3.7 s

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

  • Tap response (INP) held steady for real visitors

    -1%

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

7 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 161 ms

    161 ms

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

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

  • Largest content (LCP) got 33% faster for real visitors

    -33%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 57 ms

    57 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.34 g

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

4 checks passed
  • Page weight: 1.2 MB in 80 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 80 requests on a phone: images 522 KiB (52), scripts 427 KiB (13) and fonts 185 KiB (3). That is a lean page.

  • 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

3 to fixGoogle 9495
  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 1 form field without a label

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

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9291
  • 4 H1 headlines

    There are 4 <h1> headlines (“Your perfect sitter is a click away”, “Your perfect sitter is a click away” and “Find the care you need from someone you trust”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Organization, Service, SoftwareApplication and WebSite) but with 1 problem, for example “Service: no offers (price) block”.

  • No X (Twitter) card tag

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

  • 70 internal links, 7 external

    The homepage links to 70 pages on sittercity.com and 7 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Find local child, senior, & pet care providers that your family will love. Share your needs & connect with matches in y…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Sittercity: Find Local Child Care, Senior Care, & Pet Care”.

  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://storage.googleapis.com/sc-sitemap-prod/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.sittercity.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: 5 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (592 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix79
  • 3 linked pages hidden from search

    https://www.sittercity.com/onboarding/seeker, https://www.sittercity.com/bh-benefits and https://www.sittercity.com/us-babysitters are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.sittercity.com/onboarding/seeker and https://www.sittercity.com/bh-benefits all use the title “Sittercity”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.sittercity.com/onboarding/seeker and https://www.sittercity.com/bh-benefits use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.sittercity.com/onboarding/seeker and https://www.sittercity.com/bh-benefits have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 9 pages that loaded have a meta description.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

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

    The homepage carries about 470 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SIGN UP”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Sign Up”, “Join as a sitter” and “Get started”.

  • Social proof on the page

    Social proof on the homepage: a star rating and 7 trust badges.

  • Analytics in place

    Analytics detected: Segment.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 5 other companies contacted

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

2 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on sittercity.com, including 12 speed issues, 2 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