Website review, no card needed

ipothecarystore.com logo

ipothecarystore.com website review

Visit site (opens in a new tab)Reviewed 8 November 202625 issues · 71 checks

This review found 25 issues worth fixing on ipothecarystore.com, 8 of them high impact, across 71 checks. The most urgent: main-thread work: 6.9 s. 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.7 s1.1 sMay 23Sep 262.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.3 s
May 30, 20261.4 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Aug 22, 20262.0 s
Aug 29, 20262.2 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
228 ms95 msJun 13Sep 12199 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 2026110 ms
Aug 22, 2026213 ms
Aug 29, 2026213 ms
Sep 5, 2026199 ms
Sep 12, 2026199 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 ipothecarystore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix55
  • Main-thread work: 6.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Google Tag Manager and Shopify and others), adding 883 KiB and 1.3 s of main-thread time.

  • Mobile performance score: 55

    55/100

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

  • Reduce unused JavaScript

    400 ms · 449 KiB

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

  • Render-blocking requests

    550 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

  • Klaviyo adds 429 ms

    429 ms

    Klaviyo costs a phone 429 ms of main-thread work and 189 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.

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 291 ms

    291 ms

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

  • Shopify adds 240 ms

    240 ms

    Shopify costs a phone 240 ms of main-thread work and 334 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

    38 KiB

    Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need.

  • Use efficient cache lifetimes

    32 KiB

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

  • Minify JavaScript

    28 KiB

    28 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    12 KiB

    1 image could be 12 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix51
  • Total Blocking Time: 2.4 s

    2.4 s

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

  • Time to Interactive: 10.2 s

    10.2 s

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

  • Largest Contentful Paint: 4.0 s

    4.0 s

    Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (2.0 s).

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

    +23%

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

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

    +83%

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

  • Speed Index: 4.9 s

    4.9 s

    Visually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 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.

2 checks passed
  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.52 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.52 g of CO₂e: 62.6 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.8 MB in 166 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 166 requests on a phone: scripts 974 KiB (70), other files 635 KiB (61) and images 90 KiB (8). 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

2 to fixGoogle 9296
  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 9278
  • No meta description

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

  • Title is long (89 characters)

    Your title is 89 characters, so Google will cut it off around 60: “Dr.Christine Schaffner | Medicine for the Multidimensional Human – Dr Christine Schaffner”.

  • One H1 headline

    Your <h1> is empty.

  • 40 internal links, 12 external

    The homepage links to 40 pages on ipothecarystore.com and 12 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://drchristineschaffner.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://drchristineschaffner.com/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 12 pages without a meta description

    https://drchristineschaffner.com/pages/contact, https://drchristineschaffner.com/pages/about, https://drchristineschaffner.com/pages/book-a-discovery-call, https://drchristineschaffner.com/pages/supplement-hub, https://drchristineschaffner.com/pages/for-practitioners and https://drchristineschaffner.com/pages/podcast and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://drchristineschaffner.com/pages/contact, https://drchristineschaffner.com/pages/about, https://drchristineschaffner.com/pages/for-practitioners and https://drchristineschaffner.com/pages/podcast have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 internal pages checked

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

5 checks passed
  • Linked pages load

    13 pages of 14 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.

  • 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 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Unexpected token '<'”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 740 words of copy

    The homepage carries about 740 words of visible text.

5 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Book a Discovery Call”, “Contact” and “Learn More About Dr. Schaffner”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 33 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 20 cookies set on arrival

    20

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

  • 20 other companies contacted

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

Apps on your store

Your storefront loads 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Forms · sealsubscriptions.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on ipothecarystore.com, including 15 speed issues, 3 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