sepiia.com website review

24 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

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

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

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

61 images could be 7.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 2.4 MB and 1.6 s of main-thread time.

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

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

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

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

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

Klaviyo costs a phone 298 ms of main-thread work and 628 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

9 KiB could be saved by minifying JavaScript.

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.

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 30.5 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 55.6 s. Good is under 3.8 s.

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

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

Real visitors wait 260 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-31, real Chrome visitors' tap response (inp) went from 214 ms to 293 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 1.7 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 19.7 MB in 509 requests on a phone: images 9.7 MB (100), media 5.6 MB (15) and scripts 2.7 MB (170). Under 2 MB keeps phones on slow connections fast.

37 images are downloaded at several times the size a phone draws them, for example sepiia-polo-manga-larga-hombre-gris-oscuro-warm-plus-4_3e236 at 1,200 px wide, shown at 180 px. Resized copies would save about 6.0 MB.

3 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

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

6 images (2.7 MB) 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 5.59 g of CO₂e: 671.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 dropdowns have no label.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

Your <h1> is empty.

The homepage links to 177 pages on sepiia.com and 4 external pages.

https://sepiia.com/en/pages/sepiia-club is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://sepiia.com/en/pages/sepiia-club and https://sepiia.com/en/collections/warm-technology have no meta description, so Google writes the search snippet from whatever text it finds.

https://sepiia.com/en/collections/best-sellers-for-men took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=52015159&Ver=2&mid=d4344ca9-8b86-46cc-ba0e-abb1a5ad0f16&bo=1&sid=4cd21900d98c11f18fdfb1d4e7967253&vid=4cd257c0d98c11f193e0f9b18e8e8746&vids=1&msclkid=N&pi=918639831&lg.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Unexpected end of input”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,054 words of visible text.

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