Website review, no card needed

chewandheal.com logo

chewandheal.com website review

Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 78 checks

This review found 32 issues worth fixing on chewandheal.com, 11 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

Real-visitor load time (LCP)75th percentile, phones
2.2 s1.2 sMay 16Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 15, 20261.5 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.4 s
Oct 3, 20261.6 s
Oct 10, 20261.8 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
134 ms91 msMay 16Oct 3129 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026103 ms
May 23, 2026108 ms
Jun 6, 2026104 ms
Jun 13, 202696 ms
Jun 20, 202696 ms
Jun 27, 2026108 ms
Jul 11, 2026113 ms
Sep 5, 2026112 ms
Sep 12, 2026120 ms
Sep 19, 2026121 ms
Sep 26, 2026128 ms
Oct 3, 2026129 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 chewandheal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. chewandheal.com at 0.6 s0.6 s
  2. chewandheal.com at 1.2 s1.2 s
  3. chewandheal.com at 1.8 s1.8 s
  4. chewandheal.com at 2.4 s2.4 s
  5. chewandheal.com at 3.0 s3.0 s
  6. chewandheal.com at 3.6 s3.6 s
  7. chewandheal.com at 4.2 s4.2 s
  8. chewandheal.com at 4.8 s4.8 s

Speed

9 to fix61
  • Reduce unused JavaScript

    2.4 s · 542 KiB

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

  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    1.3 s · 213 KiB

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

  • Improve image delivery

    300 ms · 743 KiB

    25 images could be 743 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Mobile performance score: 61

    61/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, bestfreecdn.com and rechargecdn.com and others), adding 1.7 MB and 471 ms of main-thread time.

  • Shopify adds 230 ms

    230 ms

    Shopify costs a phone 230 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.

  • Main-thread work: 2.0 s

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

  • 1,594 HTML elements

    The page has 1,594 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    150 ms · 37 KiB

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

  • Minify JavaScript

    120 ms · 40 KiB

    40 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    120 ms · 18 KiB

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

  • 4 long tasks on the main thread

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

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 16.1 s

    16.1 s

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

  • Time to Interactive: 16.5 s

    16.5 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Speed Index: 7.0 s

    7.0 s

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

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

    +22%

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

  • 29 images without width and height

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

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

    +15%

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

5 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 61 ms

    61 ms

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

Images and page weight

2 to fix60
  • Page weight: 17.1 MB in 247 requests

    17.1 MB

    Your homepage downloads 17.1 MB in 247 requests on a phone: media 13.1 MB (1), images 1.9 MB (53) and scripts 1.3 MB (87). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    51 KiB

    1 image is downloaded at several times the size a phone draws it, for example Faire_logo_black.png at 5,692 px wide, shown at 110 px. Resized copies would save about 51 KiB.

  • 1 image in older formats

    1 image (205 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 2 images below the first screen load straight away

    2 images further down the page (227 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.9 g of CO₂ per visit

    4.86 g

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

Accessibility

6 to fixGoogle 8793
  • 19 text elements with low contrast

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

  • 4 tap targets too small

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

  • 7 images without alt text

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

  • 13 links without text

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

  • 1 form field without a label

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

1 checks passed
  • 55 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • Meta description is short (48 characters)

    Your meta description is only 48 characters: “Chew + Heal Tasty Supplements That Actually Work”. 70 to 160 characters is enough to sell the click.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/logo-510-06.png")”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • One H1 headline

    Your <h1> is empty.

  • 88 internal links, 20 external

    The homepage links to 88 pages on chewandheal.com and 20 external pages.

5 checks passed
  • Title: 36 characters

    Your title is a healthy 36 characters: “Tasty Supplements That Actually Work”.

  • Canonical URL set

    The canonical URL is https://chewandheal.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://chewandheal.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,056 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://chewandheal.com/pages/rescue-partnerships, https://chewandheal.com/collections/functional-treats, https://chewandheal.com/collections/digestive-health, https://chewandheal.com/collections/soft-chew-supplements, https://chewandheal.com/collections/liquid-supplements and https://chewandheal.com/collections/powdered-supplements and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://chewandheal.com/pages/contact-us and https://chewandheal.com/pages/rescue-partnerships 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 40 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    16 of 18 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
  • No analytics detected

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

  • About 832 words of copy

    The homepage carries about 832 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: “SHOP NOW” and “BUY ON AMAZON”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop Now”, “Subscribe” and “Shop Amazon”.

  • 3 short forms

    3 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, 5 customer or partner logos and a star rating.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email 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
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 26 other companies contacted

    Loading the homepage contacts 26 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 chewandheal.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 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Bnb App Amazon Buy Now Button · Pagefly Ai Page Builder · Klaviyo Email Marketing Sms · Seal Subscriptions · Judge Me Reviews · Session Recording Now · Ecomsend · rechargecdn.com · electricsms.com · goaffpro.com · pandect.es · bestfreecdn.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

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on chewandheal.com, including 15 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