Programmable

Website review, no card needed

dirteaworld.com logo

dirteaworld.com website review

Visit site (opens in a new tab)Reviewed 10 November 202631 issues · 79 checks

This review found 31 issues worth fixing on dirteaworld.com, 8 of them high impact, across 79 checks. The most urgent: page weight: 12.2 MB in 325 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

Site score

87B

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.7 s1.2 sMay 23Sep 51.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.7 s
Jun 27, 20262.8 s
Jul 4, 20263.4 s
Jul 18, 20262.5 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
163 ms87 msMay 23Oct 31154 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202696 ms
May 30, 2026101 ms
Jun 6, 2026107 ms
Jun 13, 2026106 ms
Jun 20, 2026107 ms
Jun 27, 2026106 ms
Jul 4, 2026112 ms
Aug 8, 202697 ms
Aug 15, 2026112 ms
Aug 29, 2026128 ms
Oct 3, 2026137 ms
Oct 17, 2026129 ms
Oct 24, 2026146 ms
Oct 31, 2026154 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

us.dirteaworld.com (opens in a new tab)
Full-page screenshot of dirteaworld.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix74

  • 5,756 HTML elements

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

  • Mobile performance score: 74

    74/100

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

  • Improve image delivery

    700 KiB

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

  • Render-blocking requests

    700 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, loox.io and Clarity and others), adding 901 KiB and 524 ms of main-thread time.

  • Main-thread work: 2.9 s

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

  • Klaviyo adds 181 ms

    181 ms

    Klaviyo costs a phone 181 ms of main-thread work and 638 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.

  • Use efficient cache lifetimes

    156 KiB

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

  • Reduce unused JavaScript

    151 KiB

    About 151 KiB of JavaScript is downloaded but never used on this page.

  • 5 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    26 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

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

6 to fix100

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

  • Time to Interactive: 16.5 s

    16.5 s

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

  • Largest Contentful Paint: 6.6 s

    6.6 s

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

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

    +52%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

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

6 checks passed

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.5 s

    1.5 s

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

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

    -24%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.6 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.008

    0.008

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

  • Total Blocking Time: 36 ms

    36 ms

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

Images and page weight

2 to fix60

  • Page weight: 12.2 MB in 325 requests

    12.2 MB

    Your homepage downloads 12.2 MB in 325 requests on a phone: media 7.9 MB (1), images 1.4 MB (40) and scripts 1.0 MB (113). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    24 KiB

    1 image is downloaded at several times the size a phone draws it, for example Untitled_design_68548164-8158-4815-9dc7-8ba53ab26fc5.png at 1,080 px wide, shown at 312 px. Resized copies would save about 24 KiB.

  • About 3.4 g of CO₂ per visit

    3.44 g

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

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

Accessibility

4 to fixGoogle 8895

  • 26 text elements with low contrast

    26 text elements don'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.

  • 5 links without text

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

  • Table header text should not be empty (1 element)

    Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h6, h2 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.

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

    Elements with visible text labels do not have matching accessible names. (5 elements).

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed

  • 56 automated accessibility rules passed

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

SEO

4 to fixGoogle 9279

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “DIRTEA Mushrooms for Focus, Energy, Calm | DIRTEA Functional Mushrooms”.

  • Meta description is long (165 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//us.dirteaworld.com/cdn/shop/t/2006/assets/logo.png?v=…”.

  • One H1 headline

    Your <h1> is empty.

  • 68 internal links, 9 external

    The homepage links to 68 pages on dirteaworld.com and 9 external pages.

4 checks passed

  • Canonical URL set

    The canonical URL is https://us.dirteaworld.com/.

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

  • llms.txt published

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

Other pages

5 to fix53

  • 1 linked page is broken

    Your homepage links to https://us.dirteaworld.com/collections/black-friday-2026, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://us.dirteaworld.com/pages/refer-a-friend and https://us.dirteaworld.com/pages/loyalty-rewards all use the title “DIRTEA”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://us.dirteaworld.com/pages/science, https://us.dirteaworld.com/pages/refer-a-friend and https://us.dirteaworld.com/pages/loyalty-rewards have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://us.dirteaworld.com/pages/refer-a-friend, whose canonical is https://us.dirteaworld.com/a/account/loyalty. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://us.dirteaworld.com/products/lions-mane-gummies-us, https://us.dirteaworld.com/products/tremella-gummies-us, https://us.dirteaworld.com/products/chaga-gummies-us, https://us.dirteaworld.com/pages/refer-a-friend and https://us.dirteaworld.com/pages/loyalty-rewards 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 25 found) and read each the way a search engine does.

2 checks passed

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693

  • 4 JavaScript errors while loading

    4 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

    28 of 28 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 449 words of copy

    The homepage carries about 449 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: “SUBSCRIBE & SAVE 20%” and “SHOP NOW”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “SUBSCRIBE & SAVE 20%”, “Shop All” and “Contact Us”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks, 48 customer or partner logos and 21 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity and Umami.

Privacy and tracking

1 to fix

  • 6 trackers load before any consent

    6

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

  • 34 cookies set on arrival

    34

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

  • 46 other companies contacted

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

Apps your storefront loads

Skio Subscriptions Yc S20 · Klaviyo Email Marketing Sms · Microsoft Clarity · Triplewhale · Applovin Shop Integration · loox.io · amazonaws.com · 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
Bootstrap
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 dirteaworld.com, including 13 speed issues, 4 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