sames.com website review

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

8 third-party services load with your homepage (YouTube, Facebook and Other Google APIs/SDKs and others), adding 2.2 MB and 954 ms of main-thread time.

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

YouTube costs a phone 696 ms of main-thread work and 973 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 655 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

DatoCMS costs a phone 0 ms of main-thread work and 1.0 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.

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

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

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sames, your partner in industrial spraying. LET'S TALK ABOU…”.

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

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

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

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

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

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

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

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

Your homepage downloads 4.5 MB in 107 requests on a phone: fonts 2.0 MB (2), scripts 1.2 MB (14) and images 1.1 MB (62). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (372 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 1.27 g of CO₂e: 151.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

8 buttons have no accessible name, so screen readers announce just “button”.

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

Links must have discernible text: 6 elements on the page fail this check, rated serious by axe-core.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The homepage links to 142 pages on sames.com and 5 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.sames.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.sames.com/usa/en/category/liquid/application, https://www.sames.com/usa/en/category/liquid/controlling-movement, https://www.sames.com/usa/en/category/liquid/feeding, https://www.sames.com/usa/en/category/liquid/mixing-dosing and https://www.sames.com/usa/en/category/liquid/accessories have no meta description, so Google writes the search snippet from whatever text it finds.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 23 testimonial or review blocks. 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.

The homepage carries about 1,253 words of visible text.

Before a visitor clicks anything, the page loads Google Ads and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 12 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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