wunderundies.com website review

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

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

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

8 third-party services load with your homepage (Hotjar, omnisnippet1.com and Shopify and others), adding 1.9 MB and 1.3 s of main-thread time.

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

Hotjar costs a phone 561 ms of main-thread work and 67 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.

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

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

Shopify costs a phone 217 ms of main-thread work and 1.0 MB 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.

OptiMonk costs a phone 166 ms of main-thread work and 420 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.

6 images could be 164 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 KiB could be saved by minifying JavaScript.

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

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

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.

2 KiB could be saved by minifying CSS.

Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Advertisement for WunderUndies with a child in a pink shirt…”.

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

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

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

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

Your homepage downloads 3.7 MB in 309 requests on a phone: scripts 1.3 MB (125), images 1.1 MB (19) and other files 1.1 MB (126). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Your meta description is 314 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.

Your <h1> is empty.

The homepage links to 72 pages on wunderundies.com and 1 external page.

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

https://wunderundies.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://wunderundies.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://wunderundies.com/products/flat-seam-briefs-for-adults, https://wunderundies.com/products/flat-seam-boxers-for-adults and https://wunderundies.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

https://wunderundies.com/products/flat-seam-boxers-for-adults 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.

https://wunderundies.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) ReferenceError: item is not defined”.

Requests the notification permission on page load.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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.

The homepage carries about 6,812 words of visible text.

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