sansarushop.com website review

11 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.1 s faster on a phone.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and JSDelivr CDN and others), adding 2.2 MB and 2.9 s of main-thread time.

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

Google Tag Manager costs a phone 821 ms of main-thread work and 716 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 634 ms of main-thread work and 475 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.

JSDelivr CDN costs a phone 442 ms of main-thread work and 212 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 352 ms of main-thread work and 398 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.

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

reamaze.com costs a phone 262 ms of main-thread work and 216 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.

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

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

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 41.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We take care of your experience on our website using our ow…”.

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

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

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

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

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

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

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

Your homepage downloads 14.0 MB in 340 requests on a phone: media 5.6 MB (1), images 4.8 MB (66) and scripts 2.4 MB (123). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

2 images (80 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.

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

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

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

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

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.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

Headings skip levels (h1 → h3), 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 only 8 characters: “San Saru”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 220 pages on sansarushop.com and 11 external pages.

https://sansarushop.com/en/collections/pendientes-top-ventas-1 and https://sansarushop.com/en/collections/pulseras-top-ventas all use the title “Best-selling bracelets – San Saru”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sansarushop.com/en/pages/coleccion-huellas-con-piedras-de-nacimiento, https://sansarushop.com/en/collections/best-sellers, https://sansarushop.com/en/collections/collares-top-ventas, https://sansarushop.com/en/collections/anillos-top-ventas, https://sansarushop.com/en/collections/pendientes-top-ventas-1 and https://sansarushop.com/en/collections/pulseras-top-ventas and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://sansarushop.com/en/pages/coleccion-huellas-con-piedras-de-nacimiento, https://sansarushop.com/en/collections/nuevo, https://sansarushop.com/en/collections/outlet, https://sansarushop.com/en/collections/best-sellers, https://sansarushop.com/en/collections/collares-top-ventas and https://sansarushop.com/en/collections/anillos-top-ventas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sansarushop.com/en/collections/outlet, https://sansarushop.com/en/collections/collares-top-ventas and https://sansarushop.com/en/collections/pendientes-top-ventas-1 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://sansarushop.com/en/collections/regalos-para-mama took over 3 s to send its HTML from our server.

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

3 images failed to load on a phone, for example https://sansarushop.com/Liquid%20error%20(snippets/sidebar-menu%20line%20169):%20invalid%20url%20input.

2 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: 65 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 208 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.

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