waldon.eu website review

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

25 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

5 third-party services load with your homepage (Shopify, enhencer.com and Microsoft Hosted Libs and others), adding 114 KiB and 138 ms of main-thread time.

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

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.

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

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

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

Scripts block taps and scrolling for 294 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.

2 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.2 MB in 212 requests on a phone: images 4.0 MB (52), other files 778 KiB (97) and scripts 327 KiB (49). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (933 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example 12_insta.jpg at 1,280 px wide, shown at 390 px. Resized copies would save about 128 KiB.

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

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

10 images have no alt text, which hurts accessibility and image search.

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

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

54 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: 3 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 22 characters: “Waldon Baby Collection”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 2 problems, for example “Organization: sameAs is an empty list”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 150 pages on waldon.eu and 6 external pages.

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

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

/ and https://waldon.eu/pages/waldon-baby-collection all use the title “Waldon Baby Collection”. Search engines can't tell which page to show for a search, so each competes with the others.

https://waldon.eu/collections/all, https://waldon.eu/blogs/aktualnosci, https://waldon.eu/pages/contact and https://waldon.eu/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://waldon.eu/collections/all, https://waldon.eu/collections/kokony-niemowlece, https://waldon.eu/collections/warkocze, https://waldon.eu/collections/poduszki-ciaowe, https://waldon.eu/collections/poduszki-do-karmienia and https://waldon.eu/collections/rozki-niemowlece and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

10 images failed to load on a phone, for example https://waldon.eu/cdn/shop/files/pln.svg?v=1233.

16 of 50 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: the server responded with a status of 404 ()”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Meta Pixel (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 15 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.