statist.no website review

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

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

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

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

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

27 images could be 686 KiB 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.

The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

The page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.

6 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Google Fonts and others), adding 2.1 MB and 509 ms of main-thread time.

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

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

23 KiB could be saved by minifying JavaScript.

statist.se costs a phone 0 ms of main-thread work and 1.5 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 12 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.

9 KiB could be saved by minifying CSS.

5 long tasks block the main thread while loading, the longest for 128 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.

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.

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

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

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

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

The layout shifts by 0.269 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' largest content (lcp) went from 0.7 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 2.4 MB in 85 requests on a phone: images 1.5 MB (50), scripts 723 KiB (16) and fonts 140 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

2 buttons have no accessible name, so screen readers announce just “button”.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is 68 characters, so Google will cut it off around 60: “TV- & Film- Statister, Castings, Auditions, Skuespiller | Statist.no”.

21 links have no real href, so search engines can't follow them.

Structured data found (Organization) but with 2 problems, for example “Organization: missing name”.

No XML sitemap at https://www.statist.no/sitemap.xml, so Google discovers your pages only by following links.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 662 pages on statist.no and 3 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.statist.no/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.

https://www.statist.no/galleri, https://www.statist.no/fordon-rekvisita, https://www.statist.no/djur, https://www.statist.no/kontakta-oss, https://www.statist.no/jobb/statisterskuespillere-tv-serien-gronne-fingre-soker-roller-fremtredende-statister-samt-statister and https://www.statist.no/jobb/reklamefilm-oslo-mann-40-60-ar-karakter and 4 others have no <title>, so Google invents the link text in results.

https://www.statist.no/galleri, https://www.statist.no/fordon-rekvisita, https://www.statist.no/djur, https://www.statist.no/kontakta-oss, https://www.statist.no/jobb/statisterskuespillere-tv-serien-gronne-fingre-soker-roller-fremtredende-statister-samt-statister and https://www.statist.no/jobb/reklamefilm-oslo-mann-40-60-ar-karakter and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.statist.no/jobb, https://www.statist.no/medlemmar, https://www.statist.no/galleri, https://www.statist.no/hus-lagenhet, https://www.statist.no/fordon-rekvisita and https://www.statist.no/djur and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (404)”.

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.

Your longest form asks for 29 fields (0 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 12,844 words of visible text.

Opening the homepage sets 6 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.