Website review, no card needed

tenzotea.co logo

tenzotea.co website review

Visit site (opens in a new tab)Reviewed 20 November 202620 issues · 58 checks

This review found 20 issues worth fixing on tenzotea.co, 6 of them high impact, across 58 checks. The most urgent: page weight: 7.8 MB. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
3.1 s1.6 sMay 30Nov 142.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.8 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.8 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.3 s
Sep 19, 20262.1 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.2 s
Nov 7, 20262.2 s
Nov 14, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
194 ms127 msMay 30Nov 14186 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026145 ms
Jun 6, 2026145 ms
Jun 13, 2026142 ms
Jun 20, 2026154 ms
Jun 27, 2026150 ms
Jul 4, 2026149 ms
Jul 11, 2026143 ms
Jul 18, 2026145 ms
Jul 25, 2026145 ms
Aug 1, 2026141 ms
Aug 8, 2026144 ms
Aug 15, 2026141 ms
Aug 22, 2026135 ms
Aug 29, 2026145 ms
Sep 5, 2026162 ms
Sep 12, 2026181 ms
Sep 19, 2026182 ms
Sep 26, 2026168 ms
Oct 3, 2026161 ms
Oct 10, 2026143 ms
Oct 17, 2026171 ms
Oct 24, 2026171 ms
Oct 31, 2026164 ms
Nov 7, 2026171 ms
Nov 14, 2026186 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

2 to fix100
  • Tap response (INP) got 23% slower for real visitors

    +23%

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

  • Real-user TTFB: 985 ms

    985 ms

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 186 ms

    186 ms

    Real visitors wait 186 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: 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 22% faster for real visitors

    -22%

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

Images and page weight

3 to fix53
  • Page weight: 7.8 MB

    7.8 MB

    Your homepage downloads 7.8 MB on a phone, 4.3 MB of it images (55%). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Tenzo_Tea_-_HP_Hero_-_Mobile_-_V2_1.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).

  • 3 images far larger than shown

    118 KiB

    3 images are downloaded at several times the size a phone draws them, for example 2_5b1ecefc-76f0-4e98-b476-f2cc3b1f56aa.png at 390 px wide, shown at 80 px. Resized copies would save about 118 KiB.

  • 1 image in older formats

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

    2.20 g

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

Accessibility

8 to fix87
  • <svg> elements with an img or image role must have alternative text (76 elements)

    <svg> elements with an img or image role must have alternative text: 76 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 7 text elements with low contrast

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

  • 4 tap targets too small

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

  • 24 images without alt text

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

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

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

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

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

  • 5 links without text

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

3 to fix86
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Not Your Average Matcha” and “Not Your Average Matcha”). One clear main headline is easier for people and search engines.

  • Meta description is long (320 characters)

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

  • 151 internal links, 4 external

    The homepage links to 151 pages on tenzotea.co and 4 external pages.

5 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “Tenzo Matcha | Organic Matcha Green Tea Powder”.

  • Canonical URL set

    The canonical URL is https://tenzotea.co/.

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 6 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 6 pages that loaded have a <title>.

Best practices

1 to fix93
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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.

  • About 1,875 words of copy

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

6 checks passed
  • Clear next step on the first screen

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

  • 33 calls to action

    The homepage has 33 calls to action, for example “Shop Now”, “Shop Now Shop Now” and “Shop Matcha”.

  • 34 short forms

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

  • Social proof on the page

    Social proof on the homepage: 107 testimonial or review blocks, a star rating and “100K+ Happy Customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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
  • 9 trackers load before any consent

    9

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

  • 24 cookies set on arrival

    24

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 tenzotea.co, 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 · snapchat.com · cloudfront.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

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on tenzotea.co, including 2 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