3.dk website review

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

About 970 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

6 third-party services load with your homepage (Google Tag Manager, Optimizely and cookieinformation.com and others), adding 19.8 MB and 1.4 s of main-thread time.

ctfassets.net costs a phone 0 ms of main-thread work and 17.8 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.

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

94 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

imgix costs a phone 0 ms of main-thread work and 598 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.

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

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

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.

3 KiB could be saved by minifying CSS.

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.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ved dit besøg på 3.dk anvender 3 egne cookies og cookies fr…”.

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

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

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

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

Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

9 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' tap response (inp) went from 242 ms to 218 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 20.9 MB in 57 requests on a phone: media 17.8 MB (2), scripts 2.1 MB (21) and images 611 KiB (17). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (60 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Elements use prohibited ARIA attributes (4 elements).

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

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

Your title is 71 characters, so Google will cut it off around 60: “3 | Mobil, abonnementer med 3LikeHome, 5G-internet og meget mere | 3.dk”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

The homepage links to 292 pages on 3.dk and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

The HTML your server sends has 1,162 of the 3,194 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no /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.

/selvbetjening/oversigt, /selvbetjening/abonnementer, /selvbetjening/forbrug, /selvbetjening/regning, /selvbetjening/tilvalg and /selvbetjening/udstyrogtilbehoer and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/selvbetjening/oversigt, /selvbetjening/abonnementer, /selvbetjening/forbrug, /selvbetjening/regning, /selvbetjening/tilvalg and /selvbetjening/udstyrogtilbehoer all use the title “Mit 3 Selvbetjening”. Search engines can't tell which page to show for a search, so each competes with the others.

/soeg has no meta description, so Google writes the search snippet from whatever text it finds.

/selvbetjening/oversigt, /selvbetjening/abonnementer, /selvbetjening/forbrug, /selvbetjening/regning, /selvbetjening/tilvalg and /selvbetjening/udstyrogtilbehoer use the same meta description. A description written for each page earns more clicks.

/business, /soeg, /shop/mobilabonnementer, /abonnementer/fordele/3family, /abonnementer/fordele/3likehome and /abonnementer/fordele/dakning-i-luften and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/abonnementer/fordele/dakning-i-luften and /abonnementer/fordele/3likehome/roaming have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/selvbetjening/oversigt, /selvbetjening/abonnementer, /selvbetjening/forbrug, /selvbetjening/regning, /selvbetjening/tilvalg and /selvbetjening/udstyrogtilbehoer took over 3 s to send their HTML from our server.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

6 links go through two or more redirects, for example https://www.3.dk/selvbetjening/oversigt/.

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.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

DMARC is set to p=none, so mail pretending to be 3.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 Google Ads and Google Tag Manager (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 5 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.