Website review, no card needed

drcuddles.com logo

drcuddles.com website review

Visit site (opens in a new tab)Reviewed 6 November 202635 issues · 78 checks

This review found 35 issues worth fixing on drcuddles.com, 7 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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.3 sMay 16Sep 121.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Sep 12, 20261.4 s

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 drcuddles.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix73
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    300 ms · 429 KiB

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

  • Improve image delivery

    100 ms · 331 KiB

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

  • 2,262 HTML elements

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

  • Main-thread work: 2.2 s

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

  • Shopify adds 101 ms

    101 ms

    Shopify costs a phone 101 ms of main-thread work and 714 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Hotjar, Shopify and Google Optimize and others), adding 1,000 KiB and 417 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 227 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    45 KiB

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

  • Legacy JavaScript

    25 KiB

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

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

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

6 to fix0
  • Fails Core Web Vitals for real visitors

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

  • Largest Contentful Paint: 9.0 s

    9.0 s

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

  • Time to Interactive: 10.1 s

    10.1 s

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

  • Real-user CLS: 0.21

    0.21

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

  • Speed Index: 4.0 s

    4.0 s

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

  • 7 images without width and height

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

5 checks passed
  • Real-user FCP: 1.3 s

    1.3 s

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

  • Largest content (LCP) got 19% faster for real visitors

    -19%

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Total Blocking Time: 89 ms

    89 ms

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

3 to fix69
  • Page weight: 3.3 MB in 288 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 288 requests on a phone: scripts 1.0 MB (109), images 1.0 MB (37) and other files 690 KiB (91). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Screenshot_2024-06-10_at_2.27.26_PM.webp 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).

  • 11 images in older formats

    11 images (569 KiB) are 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.

  • About 0.9 g of CO₂ per visit

    0.94 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8693
  • 10 text elements with low contrast

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

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • 11 links without text

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

  • 6 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 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 8588
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “ReadyRESCUE™: lifesaving tool for chocolate & oth…”). One clear main headline is easier for people and search engines.

  • Meta description is long (225 characters)

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

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

  • 39 internal links, 13 external

    The homepage links to 39 pages on drcuddles.com and 13 external pages.

6 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “ReadyRESCUE™ | When seconds count, be Ready.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, Product 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://drcuddles.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 (3,697 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix76
  • 4 pages share a title

    https://drcuddles.com/products/readyrescue%E2%84%A2-single-30-lb-and-less, https://drcuddles.com/products/readyrescue%E2%84%A2-lifesaving-home-emergency-treatment-for-chocolate-other-pet-poisons-for-pets-30-lbs-and-under-copy, https://drcuddles.com/products/readyrescue%E2%84%A2-lifesaving-home-emergency-treatment-for-chocolate-other-pet-poisons-for-pets-60-lbs-and-under-copy and https://drcuddles.com/products/readyrescue%E2%84%A2-lifesaving-home-emergency-treatment-for-chocolate-other-pet-poisons-for-pets-90-150-lbs-copy all use the title “ReadyRESCUE™: lifesaving home emergency treatment for chocolate & othe”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://drcuddles.com/blogs/blog, https://drcuddles.com/policies/shipping-policy and https://drcuddles.com/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://drcuddles.com/products/readyrescue%E2%84%A2-single-30-lb-and-less, https://drcuddles.com/products/readyrescue%E2%84%A2-lifesaving-home-emergency-treatment-for-chocolate-other-pet-poisons-for-pets-30-lbs-and-under-copy, https://drcuddles.com/products/readyrescue, https://drcuddles.com/products/readyrescue%E2%84%A2-lifesaving-home-emergency-treatment-for-chocolate-other-pet-poisons-for-pets-60-lbs-and-under-copy and https://drcuddles.com/products/readyrescue%E2%84%A2-lifesaving-home-emergency-treatment-for-chocolate-other-pet-poisons-for-pets-90-150-lbs-copy use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://drcuddles.com/products/readyrescue%E2%84%A2-single-30-lb-and-less, whose canonical is https://drcuddles.com/products/readyrescue%e2%84%a2-single-30-lb-and-less. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://drcuddles.com/collections/all and https://drcuddles.com/pages/wholesale 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 and read each the way a search engine does.

3 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://drcuddles.com/cdn/shop/t/107/assets/breadcrumb.css?v=16232' because its MIME type …”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,757 words of copy

    The homepage carries about 1,757 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: “Learn more”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop all”, “Shop up to 30lbs (1 vial)” and “Shop 30-60lbs (2 vials)”.

  • 6 short forms

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

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Microsoft Clarity and Hotjar.

  • 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
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 mores (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.

  • 19 cookies set on arrival

    19

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

  • 31 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Uppromote Affiliate · Store Locator · Forms · Ali Reviews · Affliate By Secomapp · Cornercart · trafficmanager.net · pop6serve.com · cloudfront.net

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
Tailwind CSS
E-commerce
Shopify
Analytics
Hotjar | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on drcuddles.com, including 13 speed issues, 3 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