serapian.com website review

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

Your mobile performance score is 40. 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.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

ZenDesk costs a phone 401 ms of main-thread work and 480 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 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Google CDN costs a phone 84 ms of main-thread work and 349 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.

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

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

32 KiB could be saved by minifying JavaScript.

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 13.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 26.1 s. Good is under 3.8 s.

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

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

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

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

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

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

Your homepage downloads 5.3 MB in 285 requests on a phone: scripts 2.1 MB (107), images 2.0 MB (46) and other files 789 KiB (112). Under 2 MB keeps phones on slow connections fast.

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

1 image (118 KiB) is 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 1.50 g of CO₂e: 179.4 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”.

ARIA dialog and alertdialog nodes should have an accessible name: 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.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

138 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 320 pages on serapian.com and 4 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.

https://www.serapian.com/pages/mosaico-chiaroscuro, https://www.serapian.com/pages/secret-bag and https://www.serapian.com/pages/maro-bag have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.serapian.com/collections/woman-new-arrivals took over 3 s to send its HTML from our server.

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

7 of 34 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.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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

Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 10 fields (5 required). Every extra field lowers completion.

The homepage carries about 508 words of visible text.

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