umage.com website review

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

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

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

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

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.

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

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

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

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

Real visitors wait 261 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-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 262 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

The first text or image appears after 2.1 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-10-31, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.2 MB in 101 requests on a phone: images 1.4 MB (54), scripts 435 KiB (28) and HTML 231 KiB (1). Under 2 MB keeps phones on slow connections fast.

Lyst_skandinavisk_hjemmekontor_i_naturligt_lys.png 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.62 g of CO₂e: 74.6 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”.

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

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

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 269 pages on umage.com and 13 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.com/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.com/collections/bestsellers, https://umage.com/collections/all-products, https://umage.com/collections/coffee-side-tables, https://umage.com/collections/desks-console-tables, https://umage.com/collections/stools-benches and https://umage.com/collections/cabinets-shelving and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

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