Website review, no card needed

thenaturalwash.com logo

thenaturalwash.com website review

Visit site (opens in a new tab)Reviewed 3 November 202642 issues · 90 checks

This review found 42 issues worth fixing on thenaturalwash.com, 14 of them high impact, across 90 checks. The most urgent: 9,404 HTML elements. 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
3.1 s1.7 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
559 ms322 msMay 16Oct 31483 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026363 ms
May 23, 2026352 ms
May 30, 2026349 ms
Jun 6, 2026362 ms
Jun 13, 2026387 ms
Jun 20, 2026405 ms
Jun 27, 2026416 ms
Jul 4, 2026424 ms
Jul 11, 2026420 ms
Jul 18, 2026418 ms
Jul 25, 2026419 ms
Aug 1, 2026409 ms
Aug 8, 2026426 ms
Aug 15, 2026454 ms
Aug 22, 2026478 ms
Aug 29, 2026532 ms
Sep 5, 2026456 ms
Sep 12, 2026439 ms
Sep 19, 2026440 ms
Sep 26, 2026434 ms
Oct 3, 2026459 ms
Oct 10, 2026481 ms
Oct 17, 2026484 ms
Oct 24, 2026482 ms
Oct 31, 2026483 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 thenaturalwash.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thenaturalwash.com at 1.1 s1.1 s
  2. thenaturalwash.com at 2.2 s2.2 s
  3. thenaturalwash.com at 3.3 s3.3 s
  4. thenaturalwash.com at 4.4 s4.4 s
  5. thenaturalwash.com at 5.6 s5.6 s
  6. thenaturalwash.com at 6.7 s6.7 s
  7. thenaturalwash.com at 7.8 s7.8 s
  8. thenaturalwash.com at 8.9 s8.9 s

Speed

14 to fix58
  • 9,404 HTML elements

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

  • Main-thread work: 8.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (shiprocket.in, Amazon Web Services and Facebook and others), adding 2.3 MB and 2.0 s of main-thread time.

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 58

    58/100

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

  • Use efficient cache lifetimes

    828 KiB

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

  • Render-blocking requests

    650 ms

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

  • Improve image delivery

    450 ms · 197 KiB

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

  • 20 long tasks on the main thread

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

  • shiprocket.in adds 456 ms

    456 ms

    shiprocket.in costs a phone 456 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.

  • Facebook adds 331 ms

    331 ms

    Facebook costs a phone 331 ms of main-thread work and 283 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.

  • Amazon Web Services adds 335 ms

    335 ms

    Amazon Web Services costs a phone 335 ms of main-thread work and 83 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.

  • pages.dev adds 215 ms

    215 ms

    pages.dev costs a phone 215 ms of main-thread work and 623 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.

  • Shopify adds 235 ms

    235 ms

    Shopify costs a phone 235 ms of main-thread work and 403 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 CSS

    83 KiB

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

  • Duplicated JavaScript

    54 KiB

    54 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    49 KiB

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

  • Minify JavaScript

    12 KiB

    12 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: 23 ms

    23 ms

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

Core Web Vitals

9 to fix67
  • 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 INP: 657 ms

    657 ms

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

  • Time to Interactive: 24.9 s

    24.9 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

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

  • Tap response (INP) got 35% slower for real visitors

    +35%

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

  • Real-user TTFB: 860 ms

    860 ms

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

  • 4 images without width and height

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.7 s

    1.7 s

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

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

    -31%

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 5.4 MB in 321 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 321 requests on a phone: scripts 2.2 MB (70), images 2.1 MB (113) and other files 675 KiB (95). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

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

    1.53 g

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

2 checks passed
  • 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

8 to fixGoogle 8790
  • 15 tap targets too small

    15 tap targets are too small or too close together to hit reliably with a finger.

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

  • Positive tabindex

    3 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

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

  • 67 form fields without a label

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

  • 40 links without text

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

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

2 checks passed
  • Every image has alt text

    All 196 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 7 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 9288
  • Meta description is long (185 characters)

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

  • 7 links crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • 245 internal links, 45 external

    The homepage links to 245 pages on thenaturalwash.com and 45 external pages.

6 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “Buy Natural Skin Care Products Online | TNW - The Natural Wash”.

  • Canonical URL set

    The canonical URL is https://www.thenaturalwash.com/.

  • Structured data in place

    Structured data found: Organization 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://www.thenaturalwash.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 (4,808 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix65
  • 2 linked pages are broken

    Your homepage links to https://www.thenaturalwash.com/collections/all-packs-masks and https://www.thenaturalwash.com/collections/all-spf-range, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 8 pages without a meta description

    https://www.thenaturalwash.com/pages/festive-special-basket, https://www.thenaturalwash.com/collections/all-products-manual, https://www.thenaturalwash.com/collections/all-serums, https://www.thenaturalwash.com/collections/all-toners, https://www.thenaturalwash.com/collections/skin-protection-moisturizers and https://www.thenaturalwash.com/collections/all-face-oil and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.thenaturalwash.com/pages/festive-special-basket, https://www.thenaturalwash.com/collections/all-products-manual, https://www.thenaturalwash.com/collections/combo, https://www.thenaturalwash.com/collections/new-arrival, https://www.thenaturalwash.com/collections/best-seller and https://www.thenaturalwash.com/collections/all-toners and 2 others 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 (of 109 found) and read each the way a search engine does.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 7 third-party cookies

    7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) ReferenceError: gtag is not defined”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 2,589 words of copy

    The homepage carries about 2,589 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy 3 Products @ 699” and “SHOP”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Buy 3 Products @ 699” and “Shop By Concern”.

  • 58 short forms

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

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Analytics and 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, Meta Pixel and Microsoft Ads 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.

  • 33 cookies set on arrival

    33

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

  • 42 other companies contacted

    Loading the homepage contacts 42 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 thenaturalwash.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on thenaturalwash.com, including 23 speed issues, 3 SEO issues and 1 conversion gap. 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