kongeparken.no website review

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

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

8 third-party services load with your homepage (Google Tag Manager, voiceflow.com and Facebook and others), adding 10.3 MB and 1.2 s of main-thread time.

cdn-website.com costs a phone 162 ms of main-thread work and 8.7 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.

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

About 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 470 ms faster on a phone.

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

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

voiceflow.com costs a phone 249 ms of main-thread work and 629 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.

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

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

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

15 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB could be saved by minifying CSS.

Your largest element takes 18.2 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 21.9 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 12.2 MB in 158 requests on a phone: media 8.0 MB (1), scripts 2.2 MB (48) and images 1.5 MB (32). Under 2 MB keeps phones on slow connections fast.

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

Some list items are not inside a list.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

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

Your title is only 17 characters: “Der helter skapes”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 60 pages on kongeparken.no and 8 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.

https://www.kongeparken.no/parkering is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.kongeparken.no/planlegg, https://www.kongeparken.no/apningstider and https://www.kongeparken.no/oftestiltesporsmal all use the title “Planlegg opplevelsene!”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kongeparken.no/planlegg, https://www.kongeparken.no/apningstider and https://www.kongeparken.no/oftestiltesporsmal use the same meta description. A description written for each page earns more clicks.

https://www.kongeparken.no/apningstider, https://www.kongeparken.no/parkering, https://www.kongeparken.no/lost---found and https://www.kongeparken.no/billetter-priser have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kongeparken.no/apningstider, https://www.kongeparken.no/lost---found, https://www.kongeparken.no/attraksjoner, https://www.kongeparken.no/bedriftoggrupper and https://www.kongeparken.no/billetter-priser have 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 21 found) and read each the way a search engine does.

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap Pixel and 1 more (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 19 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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.