Website review, no card needed

thecuticlelab.com logo

thecuticlelab.com website review

Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 80 checks

This review found 33 issues worth fixing on thecuticlelab.com, 10 of them high impact, across 80 checks. The most urgent: page weight: 14.2 MB in 356 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
906 ms567 msMay 16Oct 24626 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026867 ms
May 23, 2026836 ms
May 30, 2026767 ms
Jun 6, 2026733 ms
Jun 13, 2026727 ms
Jun 20, 2026683 ms
Jun 27, 2026681 ms
Jul 4, 2026687 ms
Jul 11, 2026721 ms
Jul 18, 2026785 ms
Jul 25, 2026795 ms
Aug 1, 2026796 ms
Aug 8, 2026779 ms
Sep 12, 2026764 ms
Sep 19, 2026725 ms
Sep 26, 2026642 ms
Oct 3, 2026624 ms
Oct 10, 2026608 ms
Oct 17, 2026606 ms
Oct 24, 2026626 ms
Real-visitor tap response (INP)75th percentile, phones
83 ms68 msMay 16Oct 1780 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202681 ms
May 23, 202680 ms
May 30, 202679 ms
Jun 6, 202678 ms
Jun 13, 202674 ms
Jun 20, 202671 ms
Jun 27, 202671 ms
Jul 4, 202670 ms
Jul 11, 202677 ms
Jul 18, 202678 ms
Jul 25, 202678 ms
Aug 1, 202679 ms
Aug 8, 202678 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202675 ms
Oct 3, 202676 ms
Oct 10, 202679 ms
Oct 17, 202680 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 thecuticlelab.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thecuticlelab.com at 0.4 s0.4 s
  2. thecuticlelab.com at 0.9 s0.9 s
  3. thecuticlelab.com at 1.3 s1.3 s
  4. thecuticlelab.com at 1.7 s1.7 s
  5. thecuticlelab.com at 2.1 s2.1 s
  6. thecuticlelab.com at 2.6 s2.6 s
  7. thecuticlelab.com at 3.0 s3.0 s
  8. thecuticlelab.com at 3.4 s3.4 s

Speed

6 to fix66
  • Main-thread work: 6.5 s

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

  • 5,432 HTML elements

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

  • Mobile performance score: 66

    66/100

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

  • Improve image delivery

    501 KiB

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

  • Render-blocking requests

    300 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Shopify adds 66 ms

    66 ms

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

  • Reduce unused JavaScript

    150 ms · 44 KiB

    About 44 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.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 187 ms. During a long task the page ignores taps.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, Google CDN and MailMunch and others), adding 609 KiB and 106 ms of main-thread time.

  • Reduce unused CSS

    90 ms · 24 KiB

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

  • Use efficient cache lifetimes

    27 KiB

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

  • 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: 11 ms

    11 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 6.9 s

    6.9 s

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

  • Time to Interactive: 7.0 s

    7.0 s

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

  • Speed Index: 5.2 s

    5.2 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Total Blocking Time: 205 ms

    205 ms

    Scripts block taps and scrolling for 205 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    -1%

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

7 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: 0.6 s

    0.6 s

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

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

    0.5 s

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

  • Real-user TTFB: 241 ms

    241 ms

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

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

    -28%

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

1 to fix70
  • Page weight: 14.2 MB in 356 requests

    14.2 MB

    Your homepage downloads 14.2 MB in 356 requests on a phone: media 10.9 MB (1), images 1.4 MB (38) and other files 1.2 MB (203). Under 2 MB keeps phones on slow connections fast.

  • About 4.0 g of CO₂ per visit

    4.03 g

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

9 to fixGoogle 7888
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    1 dropdown has no label.

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

  • 2 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 8573
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (15 characters)

    Your title is only 15 characters: “The Cuticle LAB”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • No favicon declared

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

  • One H1 headline

    Your <h1> is empty.

  • 149 internal links, 1 external

    The homepage links to 149 pages on thecuticlelab.com and 1 external page.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 13 pages without a meta description

    https://thecuticlelab.com/pages/scent-list-descriptions-strengths, https://thecuticlelab.com/collections/new-in, https://thecuticlelab.com/collections/reds, https://thecuticlelab.com/collections/pinks-nudes, https://thecuticlelab.com/collections/purples and https://thecuticlelab.com/collections/blues-greens and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://thecuticlelab.com/collections/dreambuild%E2%84%A2, whose canonical is https://thecuticlelab.com/collections/dreambuild%e2%84%a2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 67 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.

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

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 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

    113 of 113 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 3,595 words of copy

    The homepage carries about 3,595 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop All”, “Contact” and “Subscribe”.

  • 14 short forms

    14 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 10 cookies set on arrival

    10

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 thecuticlelab.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

Inbox · mailmunch.co · trustpilot.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
Tailwind CSS
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 33 issues on thecuticlelab.com, including 11 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