Website review, no card needed
matchaland.ch website review
Visit site (opens in a new tab)Reviewed 10 November 202642 issues · 87 checks
This review found 42 issues worth fixing on matchaland.ch, 17 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77C- #68,980 of 124,317 reviewed websitesbeats 39%
- #44,615 of 69,856 online storesbeats 31%
- #42,421 of 63,521 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 147 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 152 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 148 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 139 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 148 ms |
| Sep 5, 2026 | 149 ms |
| Sep 12, 2026 | 148 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 158 ms |
| Oct 24, 2026 | 162 ms |
| Oct 31, 2026 | 167 ms |
| Nov 7, 2026 | 164 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
Speed
Reduce unused JavaScript
3.5 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.7 s
A phone's processor spends 8.7 s on main-thread work while loading, 3.4 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 (Google Tag Manager, Shopify and Klaviyo and others), adding 2.7 MB and 1.6 s of main-thread time.
Use efficient cache lifetimes
900 ms · 392 KiB12 files are served with short cache lifetimes, so returning visitors download them again (392 KiB).
Render-blocking requests
950 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Improve image delivery
600 ms · 85 KiB2 images could be 85 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 476 ms
476 msGoogle Tag Manager costs a phone 476 ms of main-thread work and 687 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 272 ms
272 msShopify costs a phone 272 ms of main-thread work and 1.1 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.
2,630 HTML elements
The page has 2,630 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 149 ms
149 msKlaviyo costs a phone 149 ms of main-thread work and 330 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.
Legacy JavaScript
250 ms · 71 KiBPolyfills for old browsers add 71 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 201 ms. During a long task the page ignores taps.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Reduce unused CSS
150 ms · 31 KiBAbout 31 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.
Duplicated JavaScript
150 ms · 15 KiB15 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.6 s
21.6 sYour largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 30.8 s
30.8 sThe page becomes fully interactive after 30.8 s. Good is under 3.8 s.
Speed Index: 13.7 s
13.7 sVisually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 462 ms
462 msScripts block taps and scrolling for 462 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 147 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 624 ms
624 msReal visitors wait 624 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 6.5 MB in 507 requests
6.5 MBYour homepage downloads 6.5 MB in 507 requests on a phone: scripts 2.8 MB (136), other files 1.7 MB (284) and images 1.6 MB (55). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
36 KiB1 image is downloaded at several times the size a phone draws it, for example Breakfast_Ledge.png at 1,442 px wide, shown at 390 px. Resized copies would save about 36 KiB.
1 image below the first screen load straight away
1 image further down the page (105 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.8 g of CO₂ per visit
1.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.85 g of CO₂e: 221.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
5 buttons without a name
5 buttons have no accessible name, so screen readers announce just “button”.
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
29 images without alt text
29 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.
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.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6, h1 → h3 and h2 → h6), 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. (1 element).
<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
58 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 66 WCAG 2.2 A/AA and best-practice rules on the phone render: 58 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“”, “Starte den Tag mit grüner Energie.” and “LERNE MEHR ÜBER MATCHA”). One clear main headline is easier for people and search engines.
Meta description is long (302 characters)
Your meta description is 302 characters; Google truncates after about 160, so the end of your pitch is cut.
116 internal links, 3 external
The homepage links to 116 pages on matchaland.ch and 3 external pages.
5 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Ceremonial Matcha Grüntee aus Japan - MatchaLand Schweiz”.
Canonical URL set
The canonical URL is https://matchaland.ch/.
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://matchaland.ch/sitemap.xml.
AI search readiness
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.
3 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 (1,527 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://matchaland.ch/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://matchaland.ch/collections/vendors, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://matchaland.ch/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://matchaland.ch/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
10 pages without a meta description
https://matchaland.ch/collections/matcha-latte-sorten, https://matchaland.ch/collections/matcha-zubehor, https://matchaland.ch/collections/puree-fur-matcha-lattes, https://matchaland.ch/products/mixed-berry-matcha-protein-bar-12-stk, https://matchaland.ch/blogs/matcha-rezepte and https://matchaland.ch/customer_authentication/redirect and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://matchaland.ch/blogs/matcha-rezepte and https://matchaland.ch/customer_authentication/redirect 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 33 found) and read each the way a search engine does.
2 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343117230&Ver=2&mid=1c60b938-0d45-452d-afda-f41452c8412a&bo=4&sid=648abdb0dcb311f18c26e3adc9ebab10&vid=648ae330dcb311f199f9b77e68a0ddec&vids=0&msclkid=N&pi=918639831&l.
8 small tap targets
8 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot use import statement outside a module”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 1,014 words of copy
The homepage carries about 1,014 words of visible text.
3 checks passed
13 short forms
13 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 45 testimonial or review blocks, a star rating and 8 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity and PostHog.
Privacy and tracking
9 trackers load before any consent
9Before 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.
37 cookies set on arrival
37Opening the homepage sets 37 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.
43 other companies contacted
Loading the homepage contacts 43 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 matchaland.ch, 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 18 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · T Lab Ai Translate · Microsoft Clarity · Elevar Conversion Tracking · Assortion · Candy Rack · Klaviyo Email Marketing Sms · Gempages Builder · Judge Me Reviews · Triplewhale · Convert Experiences · Easylocation · Convert Web Pixel · Forms · Checkout Rules · rechargecdn.com · richpanel.com · digitaloceanspaces.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
- PostHog | 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 42 issues on matchaland.ch, including 17 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.