wendre.ee website review

The page goes through 1 redirect before it starts loading, costing about 2.4 s. Link and advertise the final URL directly.

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

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

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

8 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Shopify and others), adding 3.2 MB and 2.0 s of main-thread time.

hcaptcha.com costs a phone 933 ms of main-thread work and 1.2 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.

Google Tag Manager costs a phone 437 ms of main-thread work and 437 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

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

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

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

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

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

Your homepage downloads 5.6 MB in 501 requests on a phone: scripts 2.9 MB (281), images 1,007 KiB (37) and other files 802 KiB (117). Under 2 MB keeps phones on slow connections fast.

EST-wendre-e-smaspaev-mobile.png 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).

2 images are downloaded at several times the size a phone draws them, for example wendre-limited-edition-90-years-jubilee-continental_bed_2160 at 900 px wide, shown at 171 px. Resized copies would save about 123 KiB.

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

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

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

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

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: 19 elements on the page fail 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.

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is only 14 characters: “Wendre Bedding”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 9 <h1> headlines (“Beds”, “Mattresses” and “Duvets”). One clear main headline is easier for people and search engines.

The homepage links to 211 pages on wendre.ee and 7 external pages.

https://wendrebedding.com/collections/spring-mattress and https://wendrebedding.com/collections/warm-duvets have no meta description, so Google writes the search snippet from whatever text it finds.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The page uses urgency cues (a countdown or limited-time wording).

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