wndrr.com website review

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

35 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, shgcdn3.com and myshopify.com and others), adding 271 KiB and 463 ms of main-thread time.

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

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

About 22 KiB of CSS is downloaded but never applied 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.

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.

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

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

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

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

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

GIF-_SML-FILE.gif weighs 1.0 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.1 MB in 119 requests on a phone: images 2.6 MB (76), scripts 413 KiB (31) and HTML 115 KiB (1). Under 2 MB keeps phones on slow connections fast.

PHONE_BANNER_a1707a02-d591-496f-a546-ca757efde861.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 (1.0 MB) 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.

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

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 28 characters: “WNDRR | Melbourne streetwear”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 177 pages on wndrr.com and 3 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to /collections/bundle-tees-muscles, which answers with an error. Visitors hit a dead end and search engines drop it.

/pages/bundles-deals, /collections/bundle-soho-club-tees, /collections/regular-fit-tees-bundle-3-for-120, /collections/bundle-shorts-buy-3-save-20, /collections/bundle-sweats-2-for-180 and /collections/bundle-trackpants-2-for-160 and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/bundles-deals, /collections/bundle-soho-club-tees, /collections/regular-fit-tees-bundle-3-for-120, /collections/bundle-shorts-buy-3-save-20, /collections/bundle-sweats-2-for-180 and /collections/bundle-trackpants-2-for-160 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcs…”).

6 links from your homepage to your own site are broken, for example https://www.wndrr.com/ (network).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

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.

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

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

DMARC is set to p=none, so mail pretending to be wndrr.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 Tag Manager and Klaviyo (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 10 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.