kijimea.se website review

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

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

20 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

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

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

75 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.

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

Klaviyo costs a phone 102 ms of main-thread work and 352 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.

8 third-party services load with your homepage (Reviews.io, Klaviyo and Kameleoon and others), adding 905 KiB and 407 ms of main-thread time.

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

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

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

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

2 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “År 2001 skapade professor J. Lederberg, som nästan 50 år ti…”.

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

The layout shifts by 0.129 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

3 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' 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).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.4 MB in 280 requests on a phone: other files 882 KiB (123), scripts 823 KiB (80) and images 390 KiB (21). Under 2 MB keeps phones on slow connections fast.

Kijimea-K53A_Topshot-Kapseln-Online-Shop_1000x1000px.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 image has no alt text, which hurts accessibility and image search.

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.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 45 pages on kijimea.se and 4 external pages.

Your homepage links to https://kijimea.se/pages/personliche-beratung-4, which answers with an error. Visitors hit a dead end and search engines drop it.

https://kijimea.se/policies/privacy-policy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://kijimea.se/collections/alla-produkter, https://kijimea.se/pages/intervju-med-experten, https://kijimea.se/policies/terms-of-service, https://kijimea.se/policies/refund-policy, https://kijimea.se/policies/privacy-policy and https://kijimea.se/pages/recensioner and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://kijimea.se/pages/recensioner, https://kijimea.se/apps/sparning-av-foersaendelser and https://kijimea.se/pages/dagars-aterbetalningsgaranti have no <h1> headline, so visitors and search engines get no clear main topic.

https://kijimea.se/policies/shipping-policy took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'length')”.

5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 380 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 8 fields (6 required). Every extra field lowers completion.

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

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

Before a visitor clicks anything, the page loads Klaviyo (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 8 cookies, 2 of them by other companies (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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.