seitron.com website review

About 428 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

6 third-party services load with your homepage (Google Tag Manager, cookiepro.com and Optanon and others), adding 823 KiB and 700 ms of main-thread time.

Google Tag Manager costs a phone 622 ms of main-thread work and 657 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.

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

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

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

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

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

About 37 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 17 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.

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 “Seitron Banner 45 Sito 1”.

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

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

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

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.7 s (Speed Index). Good is under 3.4 s.

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

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

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

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

2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

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

Your title is 93 characters, so Google will cut it off around 60: “Seitron: analysis of combustion and emissions, refrigeration, gas safety and thermoregula…”.

There are 2 <h1> headlines (“Heritage and Innovation” and “Refrigeration”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 51 pages on seitron.com and 9 external pages.

There is no https://www.seitron.com/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.

https://www.seitron.com/en/private/assistance, https://www.seitron.com/en/downloads/apps-software, https://www.seitron.com/en/downloads/firmware, https://www.seitron.com/en/downloads/catalogues, https://www.seitron.com/en/contacts and https://www.seitron.com/en/products/professional-refrigeration/ac-refrigeration-tools and 1 other all use the title “Seitron: thermoregulation, safety and gas systems”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.seitron.com/en/industry/assistance, https://www.seitron.com/en/professionals/assistance, https://www.seitron.com/en/private/assistance, https://www.seitron.com/en/private/practical-guide, https://www.seitron.com/en/company/who-we-are-and-our-values and https://www.seitron.com/en/company/certifications and 8 others use the same meta description. A description written for each page earns more clicks.

https://www.seitron.com/en/company/sales-network has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 561 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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 8 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.