matchaandco.de website review

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

Google Tag Manager costs a phone 1.2 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, monkcommerce.app and Shopify and others), adding 3.2 MB and 1.8 s of main-thread time.

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

monkcommerce.app costs a phone 186 ms of main-thread work and 544 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 costs a phone 173 ms of main-thread work and 373 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.

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

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

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

Polyfills for old browsers add 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

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

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

40 KiB could be saved by minifying JavaScript.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 5.3 MB in 369 requests on a phone: scripts 3.4 MB (147), other files 986 KiB (140) and images 672 KiB (46). Under 2 MB keeps phones on slow connections fast.

MatchaOriginal_30gr_1_20x20_crop_center.png 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).

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

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

14 elements hidden from screen readers can still receive keyboard focus.

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

Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

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

Some list items are not inside a list.

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://matchaandco.com)”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 106 pages on matchaandco.de and 19 external pages.

https://matchaandco.de/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://matchaandco.de/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://matchaandco.de/products/premium-matcha-tea and https://matchaandco.de/products/premium-matcha-tee all use the title “Premium Bio-Matcha-Tee aus Japan kaufen – Matcha & CO”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://matchaandco.de/pages/satze and https://matchaandco.de/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://matchaandco.de/products/premium-matcha-tea and https://matchaandco.de/products/premium-matcha-tee use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://matchaandco.de/products/original-matcha-tea, whose canonical is https://matchaandco.de/products/originaler-matcha-tee. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://matchaandco.de/collections, https://matchaandco.de/collections/matcha-tee, https://matchaandco.de/collections/erganzungen, https://matchaandco.de/collections/teas, https://matchaandco.de/pages/satze and https://matchaandco.de/collections/zubehor and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://matchaandco.de/products/premium-matcha-tea took over 3 s to send its HTML from our server.

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

5 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

5 images are served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 564 words of visible text.

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.

Opening the homepage sets 25 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.