biosakure.com website review

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

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

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

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

Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

Shopify costs a phone 519 ms of main-thread work and 1.1 MB 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 411 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.

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

shopapps.site costs a phone 165 ms of main-thread work and 303 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 29 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.

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

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

80 KiB could be saved by minifying JavaScript.

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

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

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.

3 KiB could be saved by minifying CSS.

2 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

Your homepage downloads 4.4 MB in 481 requests on a phone: scripts 1.8 MB (239), images 1.0 MB (31) and other files 994 KiB (154). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example logo_biosakure_premium_haircare_verde.svg at 747 px wide, shown at 140 px. Resized copies would save about 47 KiB.

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

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

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

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

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

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

There are 8 <h1> headlines (“Pedidos”, “Envío y Seguimiento” and “Pagos”). One clear main headline is easier for people and search engines.

Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 132 pages on biosakure.com and 14 external pages.

A phone browser shows 2,202 words, but the HTML your server sends has only 598. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

https://biosakure.com/pages/brujula-capilar has no meta description, so Google writes the search snippet from whatever text it finds.

https://biosakure.com/collections/tratamientos-capilares/prelavado, https://biosakure.com/collections/tratamientos-capilares/proteinas, https://biosakure.com/collections/tratamientos-capilares/protecci%C3%B3n and https://biosakure.com/collections/tratamientos-capilares 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://biosakure.com/collections/acondicionadores-y-mascarillas-capilares/hidrataci%C3%B3n, whose canonical is https://biosakure.com/collections/acondicionadores-y-mascarillas-capilares/hidrataci%c3%b3n. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'style')”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 2,202 words of visible text.

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