uop.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Optanon and others), adding 2.7 MB and 1.7 s of main-thread time.

About 1.4 MB of JavaScript is downloaded but never used on this page.

Google CDN costs a phone 601 ms of main-thread work and 1.1 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.

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

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

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

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

gbqofs.com costs a phone 63 ms of main-thread work and 302 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 131 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 250 ms faster on a phone.

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

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

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

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

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

Scripts block taps and scrolling for 1.8 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.

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

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

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

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

15 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-31, real Chrome visitors' tap response (inp) went from 268 ms to 301 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 8.2 MB in 195 requests on a phone: media 3.1 MB (1), scripts 2.9 MB (57) and images 998 KiB (57). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example 06-HydrogenEconomy.jpg at 2,048 px wide, shown at 360 px. Resized copies would save about 1.0 MB.

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

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 8 characters: “UOP Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“POWERING CUSTOMER EVOLUTION.”, “” and “Deep Dive”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 72 pages on uop.com and 38 external pages.

There is no https://uop.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.

/ and https://uop.honeywell.com/en all use the title “UOP Home”. Search engines can't tell which page to show for a search, so each competes with the others.

https://uop.honeywell.com/en/about-uop, https://uop.honeywell.com/en/contact-us, https://uop.honeywell.com/en/portal-support, https://uop.honeywell.com/en/energy-transition, https://uop.honeywell.com/en/products-and-services/all-product-and-services and https://uop.honeywell.com/en/products-and-services/catalysts and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://uop.honeywell.com/en/redirects/news-and-events, whose canonical is https://uop.honeywell.com/en/news-events. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://uop.honeywell.com/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 29 found) and read each the way a search engine does.

No viewport meta tag, so phones render the desktop layout zoomed out.

1 image failed to load on a phone, for example https://id.rlcdn.com/464526.gif.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Unexpected token '.'”.

Large scripts ship without source maps.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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