jorgsholm.dk website review

11 images could be 501 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, tailwindcss.com and Klaviyo and others), adding 1.0 MB and 929 ms of main-thread time.

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

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

417 KiB could be saved by minifying JavaScript.

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

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

32 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Alle vores knive er tilbage på lager”.

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

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

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

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

Your homepage downloads 3.9 MB in 210 requests on a phone: scripts 1.8 MB (72), images 900 KiB (12) and other files 850 KiB (109). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example DSC2026.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 15 KiB.

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

23 tap targets are too small or too close together to hit reliably with a finger.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner 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.

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

Your title is only 9 characters: “Jørgsholm”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 212 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 122 pages on jorgsholm.dk and 4 external pages.

There is no https://jorgsholm.dk/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://jorgsholm.dk/collections/udstyr, https://jorgsholm.dk/collections/borddaekning and https://jorgsholm.dk/collections/shop-alt-til-bordet took over 3 s to send their HTML from our server.

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

30 of 108 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 “Error: <svg> attribute height: Expected length, "auto".”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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