pandatea.de website review

16 images could be 283 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

8 third-party services load with your homepage (TikTok, Klaviyo and Shopify and others), adding 1.3 MB and 607 ms of main-thread time.

About 530 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Shopify costs a phone 89 ms of main-thread work and 455 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.

174 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SUPER COFFEE”.

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

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

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

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

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

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

The first text or image appears after 2.2 s on a phone. Good is under 1.8 s.

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

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

Your homepage downloads 7.4 MB in 500 requests on a phone: images 4.2 MB (161), scripts 1.7 MB (102) and other files 1.0 MB (198). Under 2 MB keeps phones on slow connections fast.

calendrier-1b.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).

1 image is downloaded at several times the size a phone draws it, for example detox-xmas_500x.jpg at 500 px wide, shown at 143 px. Resized copies would save about 15 KiB.

1 image further down the page (75 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 dropdown has no label.

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

Interactive controls must not be nested: 4 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.

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

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

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

Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.

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

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

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

There are 2 <h1> headlines (“” and “Détox & Ventre Plat”). One clear main headline is easier for people and search engines.

The homepage links to 574 pages on pandatea.de and 8 external pages.

https://www.pandatea.fr/pages/lp-noel, https://www.pandatea.fr/products/super-coffee-cacao, https://www.pandatea.fr/collections/nouveautes and https://www.pandatea.fr/products/pastilles-hydratation are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.pandatea.fr/pages/lp-noel, https://www.pandatea.fr/pages/abonnement and https://www.pandatea.fr/products/pastilles-hydratation have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pandatea.fr/pages/abonnement has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Error: <path> attribute d: Unexpected end of attribute. Expected number, "…6.556ZM11.2871 ".”.

Large scripts ship without source maps.

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

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 1,362 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

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

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