kolmarden.com website review

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

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

7 third-party services load with your homepage (Google Tag Manager, Cookie-Script.com and ctfassets.net and others), adding 9.2 MB and 282 ms of main-thread time.

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

ctfassets.net costs a phone 0 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.

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

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

11 images could be 338 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google Tag Manager costs a phone 255 ms of main-thread work and 348 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 2.2 s on main-thread work while loading, 858 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

15 KiB JavaScript is shipped twice across bundles.

Desktop scores 91 but mobile only 53. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Välkommen till Halloween på Kolmården 🎃”.

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

Visually, the page fills in at 7.0 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.

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

5 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-24, real Chrome visitors' tap response (inp) went from 167 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 10.6 MB in 84 requests on a phone: media 7.4 MB (1), scripts 1.4 MB (20) and images 1.3 MB (46). Under 2 MB keeps phones on slow connections fast.

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

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 19 characters: “Kolmårdens djurpark”. Between 30 and 65 characters leaves room to say what you do and for whom.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//images.ctfassets.net/vyz35actmxi5/3lC1BSVW63SMfdMgvMG…”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 52 pages on kolmarden.com and 12 external pages.

The HTML your server sends has 462 of the 1,108 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

https://www.kolmarden.com/mina-sidor, https://www.kolmarden.com/halloween/guldfeber and https://www.kolmarden.com/sagojul are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.kolmarden.com/halloween, https://www.kolmarden.com/mat-online, https://www.kolmarden.com/mina-sidor, https://www.kolmarden.com/halloween/guldfeber, https://www.kolmarden.com/sagojul and https://www.kolmarden.com/bamses-varld/trollskogen and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kolmarden.com/halloween, https://www.kolmarden.com/planera/oppettider-program, https://www.kolmarden.com/mat-online, https://www.kolmarden.com/sagojul, https://www.kolmarden.com/halloween/halloxmas and https://www.kolmarden.com/djurpark/djur and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kolmarden.com/planera/oppettider-program and https://www.kolmarden.com/mat-online 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 40 found) and read each the way a search engine does.

32 of 74 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,108 words of visible text.

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