smc.eu website review

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

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

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

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

12 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Optanon and Clarity and others), adding 645 KiB and 1.2 s of main-thread time.

Google Tag Manager costs a phone 559 ms of main-thread work and 211 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 401 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Optanon costs a phone 347 ms of main-thread work and 151 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.

57 KiB could be saved by minifying JavaScript.

17 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

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

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

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

5 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' tap response (inp) went from 169 ms to 175 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.1 MB in 314 requests on a phone: images 5.5 MB (167), scripts 1,022 KiB (92) and fonts 393 KiB (7). Under 2 MB keeps phones on slow connections fast.

ex600w-001.png weighs 539 KiB. On a phone connection a single image that size takes seconds.

40 images (3.7 MB) 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.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

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

Your title is only 23 characters: “SMC Europe | SMC Europe”. Between 30 and 65 characters leaves room to say what you do and for whom.

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 626 pages on smc.eu and 7 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.smc.eu/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.smc.eu/en-eu/products, https://www.smc.eu/en-eu/products/new/enhanced-products, https://www.smc.eu/en-eu/products/highlighted-products, https://www.smc.eu/en-eu/products/new-product-concepts and https://www.smc.eu/en-eu/products/clamp-cylinders~17572~nav have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://www.smc.eu/en-eu/products, whose canonical is https://www.smc.eu/en-gb/products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.smc.eu/en-eu/products/new-product-concepts, https://www.smc.eu/en-eu/products/featured-products/zgs, https://www.smc.eu/en-eu/products/actuators~16635~nav, https://www.smc.eu/en-eu/products/linear-actuators~16636~nav, https://www.smc.eu/en-eu/products/guided-actuators~17136~nav and https://www.smc.eu/en-eu/products/rotary-actuators~17282~nav and 3 others took over 3 s to send their HTML from our server.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

Social proof on the homepage: a star rating. 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.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Microsoft Clarity (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 11 cookies (measured from a US location before any click).

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