intelligrated.com website review

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

About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.8 s faster on a phone.

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

About 407 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.

382 KiB could be saved by minifying JavaScript.

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

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

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

8 third-party services load with your homepage (Adobe Tag Manager, signalfx.com and intelligrated.com and others), adding 1.3 MB and 796 ms of main-thread time.

Polyfills for old browsers add 75 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

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

Adobe Tag Manager costs a phone 257 ms of main-thread work and 138 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.

Adobe Scene7 costs a phone 90 ms of main-thread work and 307 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.

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

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

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

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.

3 KiB JavaScript is shipped twice across bundles.

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 first text or image appears after 10.5 s on a phone. Good is under 1.8 s.

Your largest element takes 23.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “INTELLIGRATED TREW TRANSNORM Three trusted brands unite to …”.

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

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

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

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

Real visitors wait 253 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

6 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-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.0 MB in 168 requests on a phone: scripts 3.3 MB (67), images 614 KiB (33) and stylesheets 421 KiB (13). Under 2 MB keeps phones on slow connections fast.

1 image (244 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 1.41 g of CO₂e: 169.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

4 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: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

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

There are 3 <h1> headlines (“Intelligrated Trew Transnorm”, “Smarter Warehouses Start Here” and “Get what you need for your operations”). One clear main headline is easier for people and search engines.

Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 192 pages on intelligrated.com and 22 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://automation.honeywell.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://automation.honeywell.com/us/en/home, https://automation.honeywell.com/au/en/home, https://automation.honeywell.com/cn/zh/home, https://automation.honeywell.com/de/de/home, https://automation.honeywell.com/fr/fr/home and https://automation.honeywell.com/it/it/home and 5 others all use the title “Industrial Automation | Honeywell”. Search engines can't tell which page to show for a search, so each competes with the others.

https://automation.honeywell.com/us/en/home, https://automation.honeywell.com/it/it/home, https://automation.honeywell.com/mx/es/home and https://automation.honeywell.com/ca/fr/home use the same meta description. A description written for each page earns more clicks.

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

https://automation.honeywell.com/us/en/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

5 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://explore.honeywell.com/rs/510-REI-219/images/HoneywellSansWeb-Bold.svg' from origin 'https://…”.

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.

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 1,093 words of visible text.

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

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