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

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and TikTok and others), adding 1.0 MB and 1.4 s of main-thread time.

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

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

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

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

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

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

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

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

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

12 KiB could be saved by minifying JavaScript.

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

Your largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and other technologies to personalize your e…”.

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

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

The layout shifts by 0.227 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 175 ms to 187 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 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 17.8 MB in 326 requests on a phone: media 10.0 MB (4), images 5.4 MB (69) and scripts 1.4 MB (94). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

15 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Headings skip levels (h1 → h4 and h3 → h5), 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 meta description is 316 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found ((untyped)) but with 4 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 223 pages on youngdays.com and 8 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/collections/all-products-bundles-excluded is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/collections/all-products-bundles-excluded, /collections/all-products-bundles-and-outlet-excluded, /collections/new-arrivals-1, /collections/our-favorite-styles, /collections/baby-and-kids-bottoms and /collections/sets and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=9bdf6321-5c9f-44c8-9c0b-d165d0207c95&referrer=&landingpage=https%3A%2F%2Fyoungdays.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017_.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

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