Website review, no card needed

sarahcrawfordphd.com logo

sarahcrawfordphd.com website review

Visit site (opens in a new tab)Reviewed 16 November 202637 issues · 78 checks

This review found 37 issues worth fixing on sarahcrawfordphd.com, 8 of them high impact, across 78 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

Full-page screenshot of sarahcrawfordphd.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix50
  • Reduce unused JavaScript

    8.3 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.3 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, Google CDN and Google Tag Manager and others), adding 3.0 MB and 1.2 s of main-thread time.

  • Mobile performance score: 50

    50/100

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

  • Reduce unused CSS

    750 ms · 110 KiB

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

  • Squarespace adds 529 ms

    529 ms

    Squarespace costs a phone 529 ms of main-thread work and 1.2 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.

  • Google CDN adds 449 ms

    449 ms

    Google CDN costs a phone 449 ms of main-thread work and 742 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.

  • Legacy JavaScript

    300 ms · 56 KiB

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

  • Main-thread work: 2.7 s

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

  • 12 long tasks on the main thread

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

  • Adobe TypeKit adds 7 ms

    7 ms

    Adobe TypeKit costs a phone 7 ms of main-thread work and 521 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.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

  • Use efficient cache lifetimes

    1 KiB

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

1 checks passed
  • Server response: 29 ms

    29 ms

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

Core Web Vitals

5 to fix48
  • Largest Contentful Paint: 19.3 s

    19.3 s

    Your largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 19.9 s

    19.9 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • Total Blocking Time: 558 ms

    558 ms

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.093

    0.093

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

Images and page weight

2 to fix81
  • Page weight: 3.5 MB in 81 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 81 requests on a phone: scripts 2.1 MB (38), fonts 548 KiB (17) and other files 479 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    S+-+Mini++-KaliMPhotos++(33+of+46).jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.0 g of CO₂ per visit

    0.99 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9691
  • 4 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (6 elements)

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

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

  • 3 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9281
  • No H1 headline

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

  • Structured data has 1 problem

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 6 links with vague text

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

  • 34 internal links, 3 external

    The homepage links to 34 pages on sarahcrawfordphd.com and 3 external pages.

5 checks passed
  • Meta description: 76 characters

    Your meta description is 76 characters: “Evidenced based, attachment focused individual and parent coaching services.”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “Sarah Angelina Gilbert, PhD, LPC”.

  • Canonical URL set

    The canonical URL is https://www.sarahangelina.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://www.sarahangelina.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (0 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.sarahangelina.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 (1,171 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix76
  • 4 pages share 2 titles

    https://www.sarahangelina.com/blog and https://www.sarahangelina.com/contact all use the title “Personalized Parent Coaching, Group Parent Coaching, and Coaching for…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://www.sarahangelina.com/about, https://www.sarahangelina.com/counseling, https://www.sarahangelina.com/consultation, https://www.sarahangelina.com/services, https://www.sarahangelina.com/pregnancy and https://www.sarahangelina.com/postpartum and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.sarahangelina.com/blog and https://www.sarahangelina.com/contact use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.sarahangelina.com/services, whose canonical is https://www.sarahangelina.com/counseling. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.sarahangelina.com/pregnancy, https://www.sarahangelina.com/postpartum and https://www.sarahangelina.com/parenting have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.sarahangelina.com/blog and https://www.sarahangelina.com/contact have 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.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/5c482a9a8f5130bb8b6c1280/132/55f0aac0e4b0f0…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Thin social proof

    Social proof on the homepage: 11 testimonial or review blocks. 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 1,098 words of copy

    The homepage carries about 1,098 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” and “SCHEDULE A FREE INTRO CALL”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact”, “Schedule a free intro call” and “Learn more”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

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.

  • 5 cookies set on arrival

    5

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

  • 11 other companies contacted

    Loading the homepage contacts 11 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 sarahcrawfordphd.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
Squarespace
Analytics
Google Analytics
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on sarahcrawfordphd.com, including 16 speed issues, 4 SEO issues and 1 conversion gap. 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