phimport.dk website review

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

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

8 third-party services load with your homepage (Klaviyo, Google CDN and Shopify and others), adding 1.0 MB and 339 ms of main-thread time.

Klaviyo costs a phone 267 ms of main-thread work and 460 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.7 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Shopify costs a phone 23 ms of main-thread work and 442 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.

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

About 86 KiB of JavaScript is downloaded but never used on this page.

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

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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying JavaScript.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 128 ms to 154 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.

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

7 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 3.9 MB in 272 requests on a phone: images 1.8 MB (88), scripts 1.0 MB (92) and other files 640 KiB (59). Under 2 MB keeps phones on slow connections fast.

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

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

2 elements hidden from screen readers can still receive keyboard focus.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 73 characters, so Google will cut it off around 60: “PH IMPORT - Rengøringsprodukter til både private og erhverv. – phimportdk”.

The homepage links to 129 pages on phimport.dk and 6 external pages.

/pages/for-og-efter has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/kontakt, /pages/for-og-efter and /pages/datablad have no <h1> headline, so visitors and search engines get no clear main topic.

/products/ph-grill-og-ovnrens, /products/bestsellerpakken and /collections/mest-populaere took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Invalid regular expression: /(?:youtube\.com\/(?:[^\/]+\/.+\/|(?:v|e(?:mbed)?)\/|youtu\.be\/)([^"&?\/\s]{11})/i: Unterm…”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://phimport.dk/customer_authentication/redirect?locale=da&region_country=DK.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

phimport.dk has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

DMARC is set to p=none, so mail pretending to be phimport.dk is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 4 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.