rexel.se website review

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

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

About 372 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

About 3.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

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

7 third-party services load with your homepage (Google Tag Manager, Optanon and Unpkg and others), adding 2.6 MB and 135 ms of main-thread time.

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

rexel.com costs a phone 0 ms of main-thread work and 1.4 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.

Google Fonts costs a phone 0 ms of main-thread work and 701 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.

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

118 KiB could be saved by minifying JavaScript.

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

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.

3 KiB could be saved by minifying CSS.

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 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Rexel Sverige och våra digitala partners använder cookies o…”.

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

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

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

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

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

Real visitors see the first content after 2.1 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.

12 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-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.5 MB in 284 requests on a phone: other files 1.8 MB (202), images 1.4 MB (47) and fonts 972 KiB (13). Under 2 MB keeps phones on slow connections fast.

11 images further down the page (989 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example critizr-logo-sm_1763387383007 at 8,000 px wide, shown at 70 px. Resized copies would save about 165 KiB.

2 images (169 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

10 links inside paragraphs rely on colour alone to stand out.

1 tap target is too small or too close together to hit reliably with a finger.

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

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.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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.

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

4 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 set, so this is minor.

The homepage links to 200 pages on rexel.se and 11 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 https://www.rexel.se/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.

Your homepage links to https://www.rexel.se/swe/Produktkatalog/Kabel-%2800-05%2C-48-49%29/02---Styr--och-maskinkabel/c/00060179, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.rexel.se/swe/store-finder, https://www.rexel.se/swe/Produktkatalog/Kabel-%2800-05%2C-48-49%29/c/0006, https://www.rexel.se/swe/Produktkatalog/Kabel-%2800-05%2C-48-49%29/00---Kraftkabel/c/00060092, https://www.rexel.se/swe/Produktkatalog/Kabel-%2800-05%2C-48-49%29/01---Styr--och-elektronikkabel/c/00060178, https://www.rexel.se/swe/Produktkatalog/Kabel-%2800-05%2C-48-49%29/03---Kopplingskabel/c/00060086 and https://www.rexel.se/swe/Produktkatalog/Kabel-%2800-05%2C-48-49%29/04---Installationskabel/c/00060064 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 145 found) and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Large scripts ship without source maps.

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

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

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

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