integral.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Cookiebot and Adroll and others), adding 882 KiB and 972 ms of main-thread time.

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

Google Tag Manager costs a phone 486 ms of main-thread work and 560 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.

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

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

A phone's processor spends 3.7 s on main-thread work while loading, 1.4 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 304 ms. During a long task the page ignores taps.

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

Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need.

About 27 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 2.0 MB in 152 requests on a phone: scripts 1.2 MB (35), images 668 KiB (54) and other files 55 KiB (57). Under 2 MB keeps phones on slow connections fast.

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

4 images are downloaded at several times the size a phone draws them, for example Metals-Businesses.jpg at 1,360 px wide, shown at 340 px. Resized copies would save about 181 KiB.

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 136 pages on integral.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.integral.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.integral.com/future-of-fx-report, https://www.integral.com/demo, https://www.integral.com/products/fx, https://www.integral.com/products/digital, https://www.integral.com/products/fx/ems and https://www.integral.com/products/digital/connectivity and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

Opening the homepage sets 5 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.