norwegianbiolabs.com website review

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

About 414 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Snapchat and Pinterest and others), adding 1.3 MB and 875 ms of main-thread time.

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

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

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

78 KiB could be saved by minifying JavaScript.

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

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

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

JSDelivr CDN costs a phone 26 ms of main-thread work and 495 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.

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

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

Polyfills for old browsers add 10 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.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 6.9 MB in 158 requests on a phone: images 2.9 MB (25), media 2.3 MB (1) and scripts 1.3 MB (66). Under 2 MB keeps phones on slow connections fast.

Ashwagandha_Bottle_Mockup_White_5.png weighs 709 KiB. On a phone connection a single image that size takes seconds.

7 images (1.1 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.

2 images are downloaded at several times the size a phone draws them, for example 6_15.png at 390 px wide, shown at 85 px. Resized copies would save about 92 KiB.

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No XML sitemap at https://norwegianbiolabs.com/sitemap.xml, so Google discovers your pages only by following links.

Your <h1> is empty.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 54 pages on norwegianbiolabs.com and 3 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.

There is no https://norwegianbiolabs.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://norwegianbiolabs.com/collections/athletic-performance, https://norwegianbiolabs.com/collections/sleep, https://norwegianbiolabs.com/collections/cognitive-function, https://norwegianbiolabs.com/collections/foundational-health, https://norwegianbiolabs.com/collections/hormone-support and https://norwegianbiolabs.com/customer_authentication/redirect and 6 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/, https://norwegianbiolabs.com/collections/athletic-performance, https://norwegianbiolabs.com/collections/sleep, https://norwegianbiolabs.com/collections/cognitive-function, https://norwegianbiolabs.com/collections/foundational-health and https://norwegianbiolabs.com/collections/hormone-support and 7 others all use the title “Norwegian Bio Labs – Premium Supplements”. Search engines can't tell which page to show for a search, so each competes with the others.

https://norwegianbiolabs.com/collections/shop-all, https://norwegianbiolabs.com/collections/athletic-performance, https://norwegianbiolabs.com/collections/sleep, https://norwegianbiolabs.com/collections/cognitive-function, https://norwegianbiolabs.com/collections/foundational-health and https://norwegianbiolabs.com/collections/hormone-support and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://norwegianbiolabs.com/products/lions-mane-extract has no <h1> headline, so visitors and search engines get no clear main topic.

https://norwegianbiolabs.com/contact.html has 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.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 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 (Forbidden)”.

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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