simes.com website review

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

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

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

13 images could be 848 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 700 ms).

About 36 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.

Usercentrics CMP costs a phone 167 ms of main-thread work and 301 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.

6 third-party services load with your homepage (Usercentrics CMP, Google CDN and LinkedIn Ads and others), adding 631 KiB and 280 ms of main-thread time.

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

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

Desktop scores 90 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

2 KiB could be saved by minifying CSS.

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Simes, Architectural lighting”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.1 MB in 54 requests on a phone: images 1.5 MB (24), scripts 386 KiB (10) and fonts 189 KiB (4). Under 2 MB keeps phones on slow connections fast.

16 images (1.5 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 (641 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

6 images are downloaded at several times the size a phone draws them, for example evidenza2_anyway.jpg at 1,245 px wide, shown at 390 px. Resized copies would save about 184 KiB.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (10 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Your meta description is only 22 characters: “Simes S.p.A. Home page”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://simes.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at simes.com/robots.txt, the first file search crawlers ask for.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 39 pages on simes.com and 17 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.

https://simes.com/en/inspiration and https://simes.com/en/ispirazione all use the title “Simes S.p.A. - Inspiration and Application reference Referenze Applic…”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://simes.com/en/inspiration and https://simes.com/en/ispirazione use the same meta description. A description written for each page earns more clicks.

https://simes.com/en/overview/221/shift-pro-rotosymmetric, https://simes.com/en/overview/231/any-way-bollard, https://simes.com/en/overview/219/shift-pro and https://simes.com/en/overview/220/field have no <h1> headline, so visitors and search engines get no clear main topic.

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

7 of 19 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 “Usercentrics [WebSdk - initBySetting]: The domain "simes.com" has not been added to the allow list for this Usercentric…”.

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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