Website review, no card needed

laundrysauce.com logo

laundrysauce.com website review

Visit site (opens in a new tab)Reviewed 9 November 202643 issues · 92 checks

This review found 43 issues worth fixing on laundrysauce.com, 18 of them high impact, across 92 checks. The most urgent: main-thread work: 18.1 s. 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.9 s1.4 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.7 s
May 30, 20262.8 s
Jun 6, 20262.7 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.5 s
Jul 4, 20262.4 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.1 s
Oct 24, 20261.7 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
321 ms236 msMay 23Nov 7271 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026295 ms
May 30, 2026294 ms
Jun 6, 2026292 ms
Jun 13, 2026299 ms
Jun 20, 2026302 ms
Jun 27, 2026311 ms
Jul 4, 2026311 ms
Jul 11, 2026300 ms
Jul 18, 2026300 ms
Jul 25, 2026298 ms
Aug 1, 2026303 ms
Aug 8, 2026304 ms
Aug 15, 2026299 ms
Aug 22, 2026291 ms
Aug 29, 2026281 ms
Sep 5, 2026276 ms
Sep 12, 2026269 ms
Sep 19, 2026261 ms
Sep 26, 2026255 ms
Oct 3, 2026250 ms
Oct 10, 2026246 ms
Oct 17, 2026254 ms
Oct 24, 2026258 ms
Oct 31, 2026263 ms
Nov 7, 2026271 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 laundrysauce.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. laundrysauce.com at 2.0 s2.0 s
  2. laundrysauce.com at 4.0 s4.0 s
  3. laundrysauce.com at 5.9 s5.9 s
  4. laundrysauce.com at 7.9 s7.9 s
  5. laundrysauce.com at 9.9 s9.9 s
  6. laundrysauce.com at 11.9 s11.9 s
  7. laundrysauce.com at 13.8 s13.8 s
  8. laundrysauce.com at 15.8 s15.8 s

Speed

14 to fix15
  • Main-thread work: 18.1 s

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

  • Render-blocking requests

    1.0 s

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

  • Mobile performance score: 15

    15/100

    Your mobile performance score is 15. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 4,483 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Sentry, Shopify and variantnow.com and others), adding 4.4 MB and 3.8 s of main-thread time.

  • Use efficient cache lifetimes

    500 ms · 1,008 KiB

    42 files are served with short cache lifetimes, so returning visitors download them again (1,008 KiB).

  • Reduce unused JavaScript

    150 ms · 1.2 MB

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

  • Shopify adds 717 ms

    717 ms

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

  • Sentry adds 766 ms

    766 ms

    Sentry costs a phone 766 ms of main-thread work and 39 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.

  • variantnow.com adds 602 ms

    602 ms

    variantnow.com costs a phone 602 ms of main-thread work and 120 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.

  • Google Tag Manager adds 463 ms

    463 ms

    Google Tag Manager costs a phone 463 ms of main-thread work and 509 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.

  • alia-prod.com adds 478 ms

    478 ms

    alia-prod.com costs a phone 478 ms of main-thread work and 353 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.

  • 20 long tasks on the main thread

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

  • Improve image delivery

    301 KiB

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

  • Reduce unused CSS

    150 ms · 32 KiB

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

  • Legacy JavaScript

    89 KiB

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

  • Minify JavaScript

    47 KiB

    47 KiB could be saved by minifying JavaScript.

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

    25 ms

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

Core Web Vitals

10 to fix33
  • 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.

  • Real-user CLS: 0.39

    0.39

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

  • Largest Contentful Paint: 22.1 s

    22.1 s

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

  • Speed Index: 22.9 s

    22.9 s

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

  • Time to Interactive: 51.4 s

    51.4 s

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

  • Total Blocking Time: 2.6 s

    2.6 s

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

  • Cumulative Layout Shift: 0.37

    0.37

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

  • Real-user INP: 212 ms

    212 ms

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

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

  • 28 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

4 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 719 ms

    719 ms

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

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

    -42%

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

Images and page weight

3 to fix43
  • Page weight: 12.2 MB in 696 requests

    12.2 MB

    Your homepage downloads 12.2 MB in 696 requests on a phone: images 6.5 MB (182), scripts 3.2 MB (154) and other files 1.5 MB (328). Under 2 MB keeps phones on slow connections fast.

  • 13 images far larger than shown

    1.8 MB

    13 images are downloaded at several times the size a phone draws them, for example SHOE-BAG-1_678f5920-1cea-482a-abad-6cf328fa58ae.jpg at 1,875 px wide, shown at 73 px. Resized copies would save about 1.8 MB.

  • 15 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (272 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 3.5 g of CO₂ per visit

    3.46 g

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

Accessibility

8 to fixGoogle 9489
  • 6 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 49 images without alt text

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

  • 4 form fields without a label

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

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

SEO

2 to fixGoogle 9293
  • Meta description is short (60 characters)

    Your meta description is only 60 characters: “Bold, soulful fragrances in simple-to-use, performance pods.”. 70 to 160 characters is enough to sell the click.

  • 11 links crawlers can't follow

    11 links have no real href, so search engines can't follow them.

  • 166 internal links, 14 external

    The homepage links to 166 pages on laundrysauce.com and 14 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “new fragrance”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Laundry Sauce | The World's Best Smelling Detergent”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • 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://laundrysauce.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://laundrysauce.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.

  • Opted out of AI training for 4 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

1 to fix98
  • 3 pages share a meta description

    https://laundrysauce.com/collections/all, https://laundrysauce.com/collections/bundles and https://laundrysauce.com/collections/laundry use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 9276
  • 3 broken images

    3 images failed to load on a phone, for example https://laundrysauce.com/.

  • 5 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 1,369 words of copy

    The homepage carries about 1,369 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP BY SCENT” and “SHOP NOW”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “Try again”, “Shop Now” and “Subscribe & Save”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 38 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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

1 to fix
  • 8 trackers load before any consent

    8

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

  • 57 cookies set on arrival

    57

    Opening the homepage sets 57 cookies, 1 of them by other companies (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.

  • 87 other companies contacted

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

Apps your storefront loads

Yotpo Product Reviews · Triplewhale · Onward · Userway Website Accessibility · Variant · Ignite Formerly Fueled · Checkmate · Klaviyo Email Marketing Sms · Trakt · Rivo Loyalty Rewards Referrals · Simple Bundle · Veeper Stop Coupon Leaks · rechargecdn.com · electricsms.com · govx.com · rakutenadvertising.io · amazonaws.com · 9gtb.com · influencer-hero.com · usemonocle.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
Analytics
Google Tag Manager
Hosting
Shopify

Company

Headquarters
Carefree

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on laundrysauce.com, including 24 speed issues and 2 SEO issues. 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