pouchi.com website review

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

Your mobile performance score is 73 (desktop: 96). Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (Shopify, pop-convert.com and useamp.com and others), adding 1.1 MB and 464 ms of main-thread time.

About 377 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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.

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

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

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

The first text or image appears after 2.2 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 3.6 MB in 399 requests on a phone: other files 1.4 MB (240), scripts 1.2 MB (124) and images 665 KiB (20). Under 2 MB keeps phones on slow connections fast.

1 image (153 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.

1 image further down the page (153 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 1.01 g of CO₂e: 120.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA commands must have an accessible name: 1 element on the page fails 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: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“POUCHI” and “Amí”). One clear main headline is easier for people and search engines.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 45 pages on pouchi.com and 6 external pages.

https://www.pouchi.com/collections/all and https://www.pouchi.com/pages/awards have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pouchi.com/collections/all-bags, https://www.pouchi.com/collections/alexia and https://www.pouchi.com/collections/essentials use the same meta description. A description written for each page earns more clicks.

https://www.pouchi.com/collections/all-bags, https://www.pouchi.com/collections/amalia, https://www.pouchi.com/collections/alexia, https://www.pouchi.com/collections/michel, https://www.pouchi.com/collections/pouchi-beauty and https://www.pouchi.com/collections/essentials and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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 171 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 Google Analytics, Google Tag Manager, Meta Pixel, Pinterest Tag and Snap Pixel (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 17 cookies (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 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.