multicare.dk website review

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

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

4 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and Google Analytics and others), adding 354 KiB and 272 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

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

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

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

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.

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

Real visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.

Real visitors wait 4.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.0 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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.

2 visible links have no text or label, so screen readers cannot say where they go.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 167 pages on multicare.dk and 0 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.

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.

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

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

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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