umage.dk website review

8 images could be 739 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

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

8 third-party services load with your homepage (JSDelivr CDN, Other Google APIs/SDKs and cdnfonts.com and others), adding 1.0 MB and 1 ms of main-thread time.

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

About 25 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

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.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

UMAGE_lifestyle_3DD_2026_Bloom_Objects_Showroom__6.jpg weighs 602 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example UMAGE_lifestyle_3DD_2026_Bloom_Objects_Showroom__6.jpg at 2,465 px wide, shown at 351 px. Resized copies would save about 539 KiB.

Your homepage downloads 3.1 MB in 104 requests on a phone: images 2.2 MB (57), scripts 436 KiB (28) and HTML 239 KiB (1). Under 2 MB keeps phones on slow connections fast.

UMAGE_lifestyle_3DD_2026_Bloom_Objects_Showroom__6.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

14 buttons have no accessible name, so screen readers announce just “button”.

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

2 images have no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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.

Elements with visible text labels do not have matching accessible names. (3 elements).

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

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

The homepage links to 266 pages on umage.dk and 16 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.

Your homepage links to https://umage.dk/products/umage-x-special-minds-asteria-floor-lamp, which answers with an error. Visitors hit a dead end and search engines drop it.

https://umage.dk/collections/bestsellers, https://umage.dk/collections/all-products, https://umage.dk/collections/coffee-side-tables, https://umage.dk/collections/desks-console-tables, https://umage.dk/collections/cabinets-shelving and https://umage.dk/collections/accessories-furniture have no meta description, so Google writes the search snippet from whatever text it finds.

https://umage.dk/collections/bestsellers, https://umage.dk/pages/blackweek, https://umage.dk/collections/all-products, https://umage.dk/collections/furniture, https://umage.dk/collections/dining-tables and https://umage.dk/collections/coffee-side-tables and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://umage.dk/collections/furniture, https://umage.dk/collections/dining-tables, https://umage.dk/collections/coffee-side-tables, https://umage.dk/collections/desks-console-tables, https://umage.dk/collections/lounge-chairs and https://umage.dk/collections/sofas-daybeds and 1 other took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://umage.dk/.

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

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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

The page uses urgency cues (a countdown or limited-time wording).

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