intis.eu website review

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

Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.

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

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

2 third-party services load with your homepage (Cookiebot and Google Fonts), adding 43 KiB and 133 ms of main-thread time.

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

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

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

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.

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

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

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Intelligent, Connected Technology”. Most of its time is element render delay (2.3 s).

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

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.

1 image (30 KiB) is 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.

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 26 characters: “Intis - Global IoT Company”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“IntelligentConnected Technology”, “” and “Intelligent, Connected Technology”). 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.

The homepage links to 27 pages on intis.eu and 31 external pages.

There is no https://intis.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://intis.eu/en and / all use the title “Intis - Global IoT Company”, 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://intis.eu/en/about-us and https://intis.eu/about-us use the same meta description. A description written for each page earns more clicks.

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

https://intis.eu/en/about-us, https://intis.eu/en/careers, https://intis.eu/en/contact, https://intis.eu/building-automation, https://intis.eu/about-us and https://intis.eu/contact and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://intis.eu/hr, https://intis.eu/building-automation, https://intis.eu/about-us and https://intis.eu/contact took over 3 s to send their HTML from our server.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://fonts.googleapis.com/css?family=Open+Sans:400,700' violates the following Content Security Polic…”.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Opening the homepage sets 2 cookies (measured from a US location before any click).

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