paopaokombucha.com website review

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

5 third-party services load with your homepage (iubenda, Shopify and tncapp.com and others), adding 328 KiB and 1.1 s of main-thread time.

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

iubenda costs a phone 960 ms of main-thread work and 127 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.

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

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

About 52 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.

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

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

About 56 KiB of JavaScript is downloaded but never used 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.

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

4 KiB could be saved by minifying JavaScript.

Your largest element takes 8.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 9.2 s. Good is under 3.8 s.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.4 MB in 222 requests on a phone: images 967 KiB (11), other files 752 KiB (89) and scripts 544 KiB (111). Under 2 MB keeps phones on slow connections fast.

Lattine_di_kombucha_Pao_Pao_assortite.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).

5 images further down the page (312 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 0.68 g of CO₂e: 81.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Scrollable region must have keyboard access: 6 elements on the page fail this check, rated serious by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 2 <h1> headlines (“Pào Pào Kombucha” and “Kombucha artigianale italiano, vivo e premiato”). One clear main headline is easier for people and search engines.

The homepage links to 51 pages on paopaokombucha.com and 1 external page.

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

https://www.paopaokombucha.com/collections/b2b and https://www.paopaokombucha.com/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.paopaokombucha.com/pages/contact, https://www.paopaokombucha.com/collections/b2b, https://www.paopaokombucha.com/customer_authentication/redirect, https://www.paopaokombucha.com/collections/all and https://www.paopaokombucha.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.paopaokombucha.com/collections/kombucha, https://www.paopaokombucha.com/pages/contact, https://www.paopaokombucha.com/collections/b2b, https://www.paopaokombucha.com/customer_authentication/redirect, https://www.paopaokombucha.com/collections/all and https://www.paopaokombucha.com/products/pao-pao-kombucha-scatola-mista and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.paopaokombucha.com/pages/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage has only about 195 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Meta Pixel (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

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