ao.dk website review

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

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

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

3 images could be 256 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

About 62 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.

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

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

5 third-party services load with your homepage (cookieinformation.com, azurefd.net and New Relic and others), adding 2.3 MB and 46 ms of main-thread time.

azurefd.net costs a phone 13 ms of main-thread work and 1.9 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.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “På vores hjemmeside sættes nødvendige cookies, som får side…”.

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

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

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

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

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

The layout shifts by 0.141 while loading, so content jumps under the reader's thumb. Good is under 0.1.

2 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' largest content (lcp) went from 2.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 69 requests on a phone: scripts 1.9 MB (18), images 1.1 MB (9) and other files 68 KiB (37). Under 2 MB keeps phones on slow connections fast.

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

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your page has no <title>, so Google has to invent the blue link in search results.

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

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

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.

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.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

1 image is served at too low a resolution for sharp phone screens.

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

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

Your security.txt expired on 2025-01-01, so researchers may not trust its contact details.

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

ao.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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage has only about 59 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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.

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