roxtec.com website review

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

About 879 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, omappapi.com and Facebook and others), adding 1.5 MB and 1.5 s of main-thread time.

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

Google Tag Manager costs a phone 676 ms of main-thread work and 646 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 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

Polyfills for old browsers add 48 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

4 images could be 51 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 50 ms).

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 21.9 s. Good is under 3.8 s.

Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By clicking “Accept All Cookies”, you agree to the storing …”.

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

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

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

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

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

Your homepage downloads 5.5 MB in 134 requests on a phone: media 2.4 MB (2), scripts 2.1 MB (54) and fonts 365 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

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

16 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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 favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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 142 pages on roxtec.com and 4 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.

/ and https://www.roxtec.com/en all use the title “Sealing solutions for cables and pipes | Roxtec Global”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.roxtec.com/en/products/solutions has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.roxtec.com/en/knowledge-library has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://www.roxtec.com/.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, Meta Pixel and Microsoft Ads and 2 mores (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 30 cookies (measured from a US location before any click).

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