jottnar.com website review

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

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

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

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

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

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

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

cloudfront.net costs a phone 119 ms of main-thread work and 299 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 (cloudfront.net, Facebook and Klarna and others), adding 995 KiB and 378 ms of main-thread time.

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

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

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

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

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.

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

Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video Cover”.

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

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

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

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

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

Your homepage downloads 22.9 MB in 215 requests on a phone: media 19.0 MB (3), scripts 1.4 MB (69) and images 1.4 MB (40). Under 2 MB keeps phones on slow connections fast.

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

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

7 images have 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.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 101 pages on jottnar.com and 10 external pages.

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

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

Large scripts ship without source maps.

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

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