pauw.com website review

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

About 402 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (odoo.com, Clarity and Klaviyo and others), adding 1,001 KiB and 640 ms of main-thread time.

odoo.com costs a phone 222 ms of main-thread work and 568 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.

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

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

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

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

6 KiB could be saved by minifying CSS.

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 13.4 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 24.3 s. Good is under 3.8 s.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 14.0 MB in 285 requests on a phone: media 7.9 MB (1), images 3.4 MB (56) and scripts 1.4 MB (71). Under 2 MB keeps phones on slow connections fast.

SET_8-01-LR_c1ba8698-72c5-4951-8eb7-72e71cd1315d.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 further down the page (40 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 3.96 g of CO₂e: 474.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 buttons have no accessible name, so screen readers announce just “button”.

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

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Structured data found ((untyped)) but with 8 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

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

The homepage links to 686 pages on pauw.com and 0 external pages.

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.

https://pauw.com/nl-us/pages/vrouwen, https://pauw.com/nl-us/collections/nieuwe-vrouwen-producten, https://pauw.com/nl-us/pages/lookbook-aw26, https://pauw.com/nl-us/pages/back-to-work-edit, https://pauw.com/pages/components and https://pauw.com/nl-us/pages/tonal-looks-edit and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://pauw.com/pages/components, whose canonical is https://pauw.com/nl-us/pages/components. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://pauw.com/nl-us/collections/nieuwe-vrouwen-producten, https://pauw.com/nl-us/pages/lookbook-aw26, https://pauw.com/nl-us/pages/back-to-work-edit, https://pauw.com/nl-us/pages/tonal-looks-edit, https://pauw.com/nl-us/collections/new-arrivals-blazers and https://pauw.com/nl-us/collections/new-arrivals-broeken-1 and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Large scripts ship without source maps.

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

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 424 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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