sizebay.com website review

Your mobile performance score is 75 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

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

2 images could be 73 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

Real visitors wait 231 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

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

9 images are downloaded at several times the size a phone draws them, for example how-to-prepare-your-fashion-e-commerce-store-for-black-frida at 1,920 px wide, shown at 270 px. Resized copies would save about 919 KiB.

13 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

6 images (832 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

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

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

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

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

The homepage links to 56 pages on sizebay.com and 6 external pages.

There is no https://sizebay.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://sizebay.com/en/virtual-try-on and https://sizebay.com/en/virtual-fitting-room all use the title “Virtual try-on | The size recommendation tool for your e-commerce”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sizebay.com/en/fashion-hub and https://sizebay.com/en/about have no meta description, so Google writes the search snippet from whatever text it finds.

https://sizebay.com/en/virtual-try-on and https://sizebay.com/en/virtual-fitting-room use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://sizebay.com/en/blog, whose canonical is https://sizebay.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://sizebay.com/en/blog has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 137 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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.