Website review, no card needed

caboodles.com logo

caboodles.com website review

Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 76 checks

This review found 31 issues worth fixing on caboodles.com, 10 of them high impact, across 76 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
886 ms671 msMay 23Nov 7712 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026759 ms
May 30, 2026732 ms
Jun 6, 2026728 ms
Jun 13, 2026737 ms
Jun 20, 2026741 ms
Jun 27, 2026777 ms
Jul 4, 2026814 ms
Jul 11, 2026847 ms
Jul 18, 2026861 ms
Jul 25, 2026811 ms
Aug 1, 2026768 ms
Aug 8, 2026738 ms
Aug 15, 2026734 ms
Aug 22, 2026757 ms
Aug 29, 2026774 ms
Sep 5, 2026778 ms
Sep 12, 2026795 ms
Sep 19, 2026744 ms
Sep 26, 2026737 ms
Oct 3, 2026741 ms
Oct 10, 2026696 ms
Oct 17, 2026734 ms
Oct 24, 2026713 ms
Oct 31, 2026718 ms
Nov 7, 2026712 ms
Real-visitor tap response (INP)75th percentile, phones
80 ms61 msMay 23Nov 775 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202670 ms
May 30, 202669 ms
Jun 6, 202670 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202671 ms
Jul 4, 202673 ms
Jul 11, 202677 ms
Jul 18, 202678 ms
Jul 25, 202671 ms
Aug 1, 202670 ms
Aug 8, 202668 ms
Aug 15, 202666 ms
Aug 22, 202667 ms
Aug 29, 202668 ms
Sep 5, 202668 ms
Sep 12, 202669 ms
Sep 19, 202668 ms
Sep 26, 202666 ms
Oct 3, 202667 ms
Oct 10, 202663 ms
Oct 17, 202666 ms
Oct 24, 202670 ms
Oct 31, 202671 ms
Nov 7, 202675 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 caboodles.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. caboodles.com at 0.6 s0.6 s
  2. caboodles.com at 1.1 s1.1 s
  3. caboodles.com at 1.7 s1.7 s
  4. caboodles.com at 2.2 s2.2 s
  5. caboodles.com at 2.8 s2.8 s
  6. caboodles.com at 3.3 s3.3 s
  7. caboodles.com at 3.9 s3.9 s
  8. caboodles.com at 4.4 s4.4 s

Speed

5 to fix67
  • Render-blocking requests

    1.8 s

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

  • Use efficient cache lifetimes

    1.1 s · 132 KiB

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

  • Mobile performance score: 67

    67/100

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

  • Improve image delivery

    431 KiB

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

  • Shopify adds 20 ms

    20 ms

    Shopify costs a phone 20 ms of main-thread work and 598 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 (Clarity, truevaultcdn.com and Klaviyo and others), adding 982 KiB and 363 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 64 KiB

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

  • 1 long task on the main thread

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

  • Legacy JavaScript

    19 KiB

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

  • Reduce unused CSS

    10 KiB

    About 10 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 12.2 s

    12.2 s

    Your largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Blue bag with branded Caboodles small keychain hanging. Nex…”.

  • Time to Interactive: 12.3 s

    12.3 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Speed Index: 4.6 s

    4.6 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

8 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 LCP: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 436 ms

    436 ms

    Real visitors wait 436 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 40 ms

    40 ms

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

Images and page weight

2 to fix81
  • Page weight: 2.9 MB in 228 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 228 requests on a phone: images 1.4 MB (30), other files 813 KiB (116) and scripts 575 KiB (65). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    CAB-Keychain_with_lipgloss-banner-mobile_ver1.jpg 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).

  • 1 image in older formats

    1 image (368 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.

  • About 0.8 g of CO₂ per visit

    0.81 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 97.8 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

4 to fixGoogle 9194
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 20 images without alt text

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

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 2 links without text

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

1 checks passed
  • 45 automated accessibility rules passed

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

6 to fixGoogle 8574
  • Title is short (24 characters)

    Your title is only 24 characters: “Caboodles® Official Site”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 10 H1 headlines

    There are 10 <h1> headlines (“Mini Size, Major Cute”, “Mini Size, Major Cute” and “Everybody Loves an On-The-Go Girl®”). One clear main headline is easier for people and search engines.

  • Meta description is long (186 characters)

    Your meta description is 186 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 with vague text

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

  • 111 internal links, 10 external

    The homepage links to 111 pages on caboodles.com and 10 external pages.

3 checks passed
  • Canonical URL set

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.caboodles.com/pages/campus-brand-ambassador-page and https://www.caboodles.com/collections/all-products have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.caboodles.com/pages/campus-brand-ambassador-page has 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 33 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187060205&Ver=2&mid=c99d673c-dfc7-413e-a41b-7f750d37e21a&bo=3&sid=a64e7ee0dc1411f19fc6879bad2db99e&vid=a64e9980dc1411f1a01933e65adf9e12&vids=0&msclkid=N&pi=918639831&l.

  • 12 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Replace_with_Variable_Revenue_Function is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 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 345 words of copy

    The homepage carries about 345 words of visible text.

3 checks passed
  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop All Collections”, “Shop All Classic Cases” and “Shop By Series”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 21 cookies set on arrival

    21

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

  • 35 other companies contacted

    Loading the homepage contacts 35 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 caboodles.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 · redirectify.app · cart-bot.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
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 31 issues on caboodles.com, including 9 speed issues, 6 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
caboodles.com website review: scores and fixes