niku.no website review

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

14 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

4 third-party services load with your homepage (hcaptcha.com, dialogapi.no and JSDelivr CDN and others), adding 1.3 MB and 883 ms of main-thread time.

Your mobile performance score is 70 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

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

hcaptcha.com costs a phone 831 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 266 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Motorisert georadarsystem i Romsdalen.”.

Real visitors wait 833 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

6 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-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Boringer-i-gang.-Foto-Ambjorg-Reinsnos.jpg weighs 5.1 MB. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example Boringer-i-gang.-Foto-Ambjorg-Reinsnos.jpg at 14,646 px wide, shown at 358 px. Resized copies would save about 5.5 MB.

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

12 images further down the page (6.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

Your homepage downloads 3.7 MB in 70 requests on a phone: images 1.9 MB (28), scripts 947 KiB (19) and fonts 429 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

1 form field has 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.

Your title is only 9 characters: “Forside —”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“Vi er et uavhengig forsknings- og kompetansemiljø…”, “Nyhetssaker” and “Nyhetsbrev”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 99 pages on niku.no and 5 external pages.

https://www.niku.no/tjenester, https://www.niku.no/tjenester/forskning, https://www.niku.no/prosjekter, https://www.niku.no/ansatte, https://www.niku.no/tjenester/nordomrade and https://www.niku.no/tjenester/klima-og-kulturarv and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

36 of 57 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 (“The Protected Audience API is deprecated and will be removed in a future release.”).

1 error was logged to the browser console while the page loaded, for example “Framing 'https://newassets.hcaptcha.com/' violates the following report-only Content Security Policy directive: "defaul…”.

Chrome logged issues while loading the page (“Content security policy”).

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.

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

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 755 words of visible text.

Opening the homepage sets 1 cookie (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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.