tess.no website review

5 images could be 562 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

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

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

About 243 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

Google Tag Manager costs a phone 295 ms of main-thread work and 354 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 third-party services load with your homepage (Google Tag Manager, Matomo and cookiebot.eu and others), adding 572 KiB and 407 ms of main-thread time.

93 KiB could be saved by minifying JavaScript.

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

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

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.

Real visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 5.5 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Din totalleverandør Spesialister på slanger og tilhørende t…”.

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

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

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

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

2 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 131 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 105 requests on a phone: images 1.5 MB (19), scripts 916 KiB (39) and fonts 591 KiB (4). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example United-Kingdom_ny.jpg at 276 px wide, shown at 25 px. Resized copies would save about 105 KiB.

3 images (146 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.

3 images further down the page (146 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 0.90 g of CO₂e: 107.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Your title is only 11 characters: “Hjem – TESS”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 4 problems, for example “WebPage: thumbnailUrl is not an absolute URL ("https://tess.no/wp-content/uploads/2025/12/Bunkringstrommel-Sirevag…”.

There is no robots.txt at tess.no/robots.txt, the first file search crawlers ask for.

The homepage links to 111 pages on tess.no and 21 external pages.

https://tess.no/tjenester/engineering, https://tess.no/tjenester/engineering/on-site-service, https://tess.no/tjenester/engineering/produkter-og-systemer, https://tess.no/tjenester/engineering/produkter-og-systemer/bunkringsstasjoner, https://tess.no/tjenester/engineering/produkter-og-systemer/hpu-og-flusheenheter and https://tess.no/tjenester/engineering/produkter-og-systemer/remote-loading and 4 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 91 found) and read each the way a search engine does.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.