Website review, no card needed

pollyheilmealey.com logo

pollyheilmealey.com website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 85 checks

This review found 39 issues worth fixing on pollyheilmealey.com, 13 of them high impact, across 85 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 pollyheilmealey.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix52
  • Reduce unused JavaScript

    8.2 s · 1.3 MB

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

  • Render-blocking requests

    6.0 s

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

  • Reduce unused CSS

    2.1 s · 341 KiB

    About 341 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.

  • Improve image delivery

    450 ms · 3.5 MB

    3 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • 8 third-party services on the page

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

  • Mobile performance score: 52

    52/100

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

  • Use efficient cache lifetimes

    750 ms · 160 KiB

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

  • Google CDN adds 531 ms

    531 ms

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

  • Legacy JavaScript

    300 ms · 44 KiB

    Polyfills for old browsers add 44 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: 3.0 s

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

  • Google Maps adds 175 ms

    175 ms

    Google Maps costs a phone 175 ms of main-thread work and 457 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.

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 122 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).

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

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

4 to fix63
  • First Contentful Paint: 12.9 s

    12.9 s

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

  • Largest Contentful Paint: 35.8 s

    35.8 s

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

  • Time to Interactive: 37.7 s

    37.7 s

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

  • Speed Index: 12.9 s

    12.9 s

    Visually, the page fills in at 12.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
  • Total Blocking Time: 193 ms

    193 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 10.1 MB in 185 requests

    10.1 MB

    Your homepage downloads 10.1 MB in 185 requests on a phone: images 6.2 MB (18), scripts 2.5 MB (109) and other files 706 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 2.9 g of CO₂ per visit

    2.86 g

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

3 checks passed
  • 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

8 to fixGoogle 7989
  • 5 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 1 image without alt text

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 5 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

5 to fixGoogle 8583
  • Title is long (123 characters)

    Your title is 123 characters, so Google will cut it off around 60: “Abundant Health & Wellness Center | Dr. Polly Heil-Mealey | Naturopath and Certified Irid…”.

  • Meta description is long (289 characters)

    Your meta description is 289 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • 3 links with vague text

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

  • 40 internal links, 14 external

    The homepage links to 40 pages on pollyheilmealey.com and 14 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Dr Polly Heil Mealey”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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://pollyheilmealey.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://pollyheilmealey.com/disclaimer, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a meta description

    https://pollyheilmealey.com/optin-ninja/consumer-awareness-guide-for-naturopath has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://pollyheilmealey.com/optin-ninja/consumer-awareness-guide-for-naturopath has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://pollyheilmealey.com/optin-ninja/consumer-awareness-guide-for-naturopath 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.

  • 1 page slow to respond

    https://pollyheilmealey.com/optin-ninja/consumer-awareness-guide-for-naturopath took over 3 s to send its HTML from our server.

  • 14 internal pages checked

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

4 checks passed
  • 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 1 page that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 12 small tap targets

    12 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “n[e] is not a function”.

  • 3 distorted images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 8 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.

  • About 739 words of copy

    The homepage carries about 739 words of visible text.

6 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “GET STARTED”, “CONTACT US” and “REQUEST AN APPOINTMENT”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 18 cookies set on arrival

    18

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

  • 15 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2020.

Stack

CMS
WordPress
Framework
React
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
WP Engine

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on pollyheilmealey.com, including 15 speed issues, 5 SEO issues and 3 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