wanderlab.ro website review

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

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

8 third-party services load with your homepage (YouTube, Shopify and Klaviyo and others), adding 2.9 MB and 905 ms of main-thread time.

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

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

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

YouTube costs a phone 444 ms of main-thread work and 999 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.

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

Klaviyo costs a phone 181 ms of main-thread work and 505 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 files are served with short cache lifetimes, so returning visitors download them again (46 KiB).

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 438 requests on a phone: scripts 1.9 MB (163), other files 1.5 MB (209) and images 688 KiB (20). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 67 characters, so Google will cut it off around 60: “Jurnale foto de calatorie personalizate – WanderLab Creative Studio”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 89 pages on wanderlab.ro and 7 external pages.

Your Organization JSON-LD is missing logo, 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.

https://wanderlab.ro/collections/australia, https://wanderlab.ro/collections/mothers-day-copy, https://wanderlab.ro/collections/family-wedding, https://wanderlab.ro/collections/mothers-day, https://wanderlab.ro/collections/bday-memories and https://wanderlab.ro/collections/summer-2025 and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://wanderlab.ro/collections/europa, https://wanderlab.ro/collections/asia, https://wanderlab.ro/collections/africa, https://wanderlab.ro/collections/america-de-sud and https://wanderlab.ro/collections/america-de-nord use the same meta description. A description written for each page earns more clicks.

https://wanderlab.ro/collections/europa, https://wanderlab.ro/collections/asia, https://wanderlab.ro/collections/africa, https://wanderlab.ro/collections/america-de-sud, https://wanderlab.ro/collections/america-de-nord and https://wanderlab.ro/collections/australia and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://wanderlab.ro/collections/mothers-day-copy, https://wanderlab.ro/collections/pets and https://wanderlab.ro/collections/family-wedding took over 3 s to send their HTML from our server.

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

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

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

Chrome logged issues while loading the page (“Cookie”).

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 1,088 words of visible text.

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

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