dekom.com website review

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

Your mobile performance score is 85 (desktop: 75). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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

1 third-party service load with your homepage (YouTube), adding 21 KiB and 15 ms of main-thread time.

15 KiB could be saved by minifying JavaScript.

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

6 KiB could be saved by minifying CSS.

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.

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

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

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

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

Visually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 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-17, real Chrome visitors' tap response (inp) went from 93 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.1 MB in 118 requests on a phone: images 1.6 MB (86), fonts 223 KiB (6) and scripts 174 KiB (14). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

There are 4 <h1> headlines (“Platforms”, “Manufacturer” and “DEKOM Professionals”). One clear main headline is easier for people and search engines.

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.

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

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

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

The homepage links to 207 pages on dekom.com and 9 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.

/en/video-conferencing/google-meet, /en/video-conferencing/ringcentral-rooms and /en/media-technology/room-design have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'name') qt (https://www.dekom.com/cache-buster-1718886307/static/golden-mini/ma…”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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.

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

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