agu.com website review

13 images could be 10.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.5 s faster on a phone.

23 files are served with short cache lifetimes, so returning visitors download them again (3.8 MB).

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

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

About 392 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.0 MB and 786 ms of main-thread time.

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

Google CDN costs a phone 214 ms of main-thread work and 733 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.

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

Google Tag Manager costs a phone 233 ms of main-thread work and 393 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.

voyado.com costs a phone 37 ms of main-thread work and 436 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 long tasks block the main thread while loading, the longest for 244 ms. During a long task the page ignores taps.

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

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

4 KiB could be saved by minifying JavaScript.

Your largest element takes 40.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Thermo fietsshirt essential heren”.

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

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

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

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

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

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

Your homepage downloads 17.0 MB in 351 requests on a phone: images 10.6 MB (29), media 2.8 MB (2) and scripts 2.4 MB (253). Under 2 MB keeps phones on slow connections fast.

4 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example agu_website_-_rebranding_-_productfoto_s_-_1200_x_1600_px_1_ at 1,200 px wide, shown at 170 px. Resized copies would save about 3.4 MB.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Some list items are not inside a list.

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

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

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

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 118 pages on agu.com and 6 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/ and /stores/store/redirect/___store/nl/___from_store/nl/uenc/aHR0cHM6Ly9hZ3UuY29tLz9fX19zdG9yZT1ubA~~ all use the title “agu | Fietskleding en regenkleding voor alle weersomstandigheden”. Search engines can't tell which page to show for a search, so each competes with the others.

/klantenservice has no meta description, so Google writes the search snippet from whatever text it finds.

/stores/store/redirect/___store/nl/___from_store/nl/uenc/aHR0cHM6Ly9hZ3UuY29tLz9fX19zdG9yZT1ubA~~, /stores/store/redirect/___store/eu/___from_store/nl/uenc/aHR0cHM6Ly9hZ3UuY29tL2V1Lw~~, /stores/store/redirect/___store/de/___from_store/nl/uenc/aHR0cHM6Ly9hZ3UuY29tL2RlLw~~, /stores/store/redirect/___store/fr/___from_store/nl/uenc/aHR0cHM6Ly9hZ3UuY29tL2ZyLw~~, /stores/store/redirect/___store/dk/___from_store/nl/uenc/aHR0cHM6Ly9hZ3UuY29tL2RrLw~~ and /stores/store/redirect/___store/es/___from_store/nl/uenc/aHR0cHM6Ly9hZ3UuY29tL2VzLw~~ and 1 other took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=56013569&tm=gtm002&Ver=2&mid=160a784c-be62-4775-9bce-b978cd04a531&bo=5&sid=02195010d30611f19fa8898b0061ef35&vid=021959b0d30611f19ccec584215c2a20&vids=1&msclkid=N&pi=91.

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

6 links go through two or more redirects, for example https://agu.com/stores/store/redirect/___store/nl/___from_store/nl/uenc/aHR0cHM6Ly9hZ3UuY29tLz9fX19zdG9yZT1ubA~~/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

agu.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

agu.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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 33 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.