Website review, no card needed

meredithdoench.com logo

meredithdoench.com website review

Visit site (opens in a new tab)Reviewed 12 November 202629 issues · 65 checks

This review found 29 issues worth fixing on meredithdoench.com, 11 of them high impact, across 65 checks. The most urgent: improve image delivery. 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 meredithdoench.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix54
  • Improve image delivery

    4.2 s · 908 KiB

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

  • Reduce unused JavaScript

    2.0 s · 345 KiB

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

  • Render-blocking requests

    1.2 s

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

  • Reduce unused CSS

    910 ms · 134 KiB

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

  • Mobile performance score: 54

    54/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Squarespace, sqspcdn.com and Adobe TypeKit and others), adding 2.1 MB and 499 ms of main-thread time.

  • Squarespace adds 478 ms

    478 ms

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

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 1,015 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

    150 ms · 94 KiB

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

  • 2 long tasks on the main thread

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

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

  • 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: 1.0 s

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

  • Server response: 79 ms

    79 ms

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

Core Web Vitals

5 to fix62
  • Largest Contentful Paint: 14.0 s

    14.0 s

    Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cover image Never Say Die. Woman's face reflected in water …”.

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Time to Interactive: 14.0 s

    14.0 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • Total Blocking Time: 221 ms

    221 ms

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

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

    0.024

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

Images and page weight

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

    2.3 MB

    Your homepage downloads 2.3 MB in 61 requests on a phone: images 1,015 KiB (4), scripts 862 KiB (39) and stylesheets 163 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (35 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.7 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

1 to fixGoogle 9698
  • 1 text element with low contrast

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

2 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 9275
  • No meta description

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

  • Title is short (15 characters)

    Your title is only 15 characters: “Meredith Doench”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 5 H1 headlines

    There are 5 <h1> headlines (“Some women aren’t meant to be mothers…”, “nEVER SAY DIE” and “AVAILABLE NOw”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 29 internal links, 17 external

    The homepage links to 29 pages on meredithdoench.com and 17 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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.meredithdoench.com/sitemap.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.

  • No llms.txt

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

Other pages

4 to fix78
  • 5 pages share a title

    https://www.meredithdoench.com/books, https://www.meredithdoench.com/books/rs, https://www.meredithdoench.com/books/wu, https://www.meredithdoench.com/books/lh and https://www.meredithdoench.com/new-dropdown all use the title “Reviews 1 — Meredith Doench”. 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.meredithdoench.com/books, https://www.meredithdoench.com/books/rs, https://www.meredithdoench.com/books/wu, https://www.meredithdoench.com/books/lh, https://www.meredithdoench.com/about and https://www.meredithdoench.com/events and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 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.meredithdoench.com/new-dropdown, whose canonical is https://www.meredithdoench.com/books. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

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

  • 8 internal pages checked

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

3 checks passed
  • Linked pages load

    All 8 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 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 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/versioned-site-css/5fde8836f9196c4f5f183c9c/60/5c5a…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • No form on the homepage

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

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

    The homepage carries about 776 words of visible text.

1 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 6 other companies contacted

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

1 checks passed
  • 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 meredithdoench.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
Hosting
Squarespace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on meredithdoench.com, including 13 speed issues, 4 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