scandinavianbiolabs.com website review

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

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

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

27 images could be 1.4 MB 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.

8 third-party services load with your homepage (Facebook, TikTok and Klaviyo and others), adding 1.1 MB and 1.4 s of main-thread time.

26 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

About 756 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

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

Facebook costs a phone 271 ms of main-thread work and 217 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.

TikTok costs a phone 268 ms of main-thread work and 158 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 97 KiB JavaScript that modern phones do not need.

17 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

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.175 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 4.9 MB in 302 requests on a phone: scripts 2.2 MB (115), images 1.6 MB (67) and other files 698 KiB (105). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 165.1 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”.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 90 characters, so Google will cut it off around 60: “Natural Hair With Bio-Pilixin® Formula | Scandinavian Biolabs – Scandinavian Biolabs | COM”.

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

The homepage links to 83 pages on scandinavianbiolabs.com and 9 external pages.

https://scandinavianbiolabs.com/collections/hair-growth-products-for-men has no meta description, so Google writes the search snippet from whatever text it finds.

https://scandinavianbiolabs.com/pages/blogs, https://scandinavianbiolabs.com/pages/help-center, https://scandinavianbiolabs.com/pages/money-back-guarantee, https://scandinavianbiolabs.com/pages/hair-advisors, https://scandinavianbiolabs.com/pages/hair-quiz and https://scandinavianbiolabs.com/products/bio-pilixin-serum-for-men and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Unable to process event: init,[object Object]”.

Large scripts ship without source maps.

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

The page uses urgency cues (a countdown or limited-time wording).

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