trepol.dk website review

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

8 third-party services load with your homepage (Shopify, pop-convert.com and Cookiebot and others), adding 10.2 MB and 568 ms of main-thread time.

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

Shopify costs a phone 307 ms of main-thread work and 9.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 66. Pages that score under 90 lose visitors before the first paint.

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

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

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

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

Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need.

About 28 KiB of CSS is downloaded but never applied on this page.

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

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.

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

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

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “trepol® udvikler og designer eksklusive emhætter og bordpla…”. Most of its time is element render delay (2.5 s).

Your homepage downloads 14.0 MB in 392 requests on a phone: media 8.6 MB (1), images 2.1 MB (18) and scripts 1.8 MB (106). Under 2 MB keeps phones on slow connections fast.

Kopi_af_Design_uden_navn_10.svg weighs 1.6 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example Kopi_af_Design_uden_navn_10.svg at 947 px wide, shown at 161 px. Resized copies would save about 1.2 MB.

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

Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Your title is 74 characters, so Google will cut it off around 60: “trepol - emhætter og emfang designet til det eksklusive køkken – Trepol.dk”.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 115 pages on trepol.dk and 7 external pages.

https://trepol.dk/pages/new-yorker and https://trepol.dk/pages/unika-emhaetter have no <h1> headline, so visitors and search engines get no clear main topic.

https://trepol.dk/products/model-94-vaeghaengt, https://trepol.dk/pages/unika-emhaetter, https://trepol.dk/collections/vaeghaengte-emhaetter and https://trepol.dk/products/model-961-indbygget took over 3 s to send their HTML from our server.

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

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

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 6 cookies (measured from a US location before any click).

Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.