Website review, no card needed

whitecuddles.com logo

whitecuddles.com website review

Visit site (opens in a new tab)Reviewed 11 November 202631 issues · 75 checks

This review found 31 issues worth fixing on whitecuddles.com, 9 of them high impact, across 75 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

Full-page screenshot of whitecuddles.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix58
  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 58

    58/100

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

  • Reduce unused JavaScript

    450 ms · 84 KiB

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

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • Reduce unused CSS

    150 ms · 28 KiB

    About 28 KiB of CSS is downloaded but never applied on this page. 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 69 ms. During a long task the page ignores taps.

  • Improve image delivery

    35 KiB

    6 images could be 35 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, Google Fonts and Cloudflare CDN), adding 28 KiB and 4 ms of main-thread time.

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

  • Use efficient cache lifetimes

    3 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (3 KiB).

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix45
  • Cumulative Layout Shift: 1

    1

    The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 4.7 s

    4.7 s

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

  • Time to Interactive: 5.3 s

    5.3 s

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

  • 19 images without width and height

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

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

3 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 26 ms

    26 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.38 g

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

    1.3 MB

    Your homepage downloads 1.3 MB in 119 requests on a phone: other files 619 KiB (55), images 302 KiB (34) and scripts 274 KiB (22). 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

10 to fixGoogle 7586
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 16 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 40 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: 40 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9281
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“WOW0821240209BLCLJLLLML” and “”). 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.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 33 internal links, 2 external

    The homepage links to 33 pages on whitecuddles.com and 2 external pages.

4 checks passed
  • Title: 32 characters

    Your title is a healthy 32 characters: “White Cuddles – whitecuddles.com”.

  • Canonical URL set

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

  • 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://whitecuddles.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://whitecuddles.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 (302 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix70
  • 4 linked pages are broken

    Your homepage links to https://whitecuddles.com/1619097059398_a, https://whitecuddles.com/1619758743622_a, https://whitecuddles.com/1619721748550_a and https://whitecuddles.com/1619119505478_a, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a meta description

    https://whitecuddles.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://whitecuddles.com/collections/all and https://whitecuddles.com/products/great-white-shark-stuffed-toy took over 3 s to send their HTML from our server.

  • 10 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

    3 of 9 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 “Failed to load resource: net::ERR_CONNECTION_CLOSED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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 analytics detected

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

  • Only about 186 words

    The homepage has only about 186 words of visible text; thin pages give Google and first-time buyers little to go on.

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop Now” and “Quick Buy”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 12 testimonial or review blocks and 3 trust badges.

  • Direct contact links

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

  • 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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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 whitecuddles.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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 31 issues on whitecuddles.com, including 8 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