solutran.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (gbqofs.com, datadoghq-browser-agent.com and Adobe Tag Manager and others), adding 882 KiB and 1.2 s of main-thread time.

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

gbqofs.com costs a phone 371 ms of main-thread work and 208 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.

datadoghq-browser-agent.com costs a phone 328 ms of main-thread work and 59 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 Tag Manager costs a phone 263 ms of main-thread work and 223 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.

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

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

2 images could be 40 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.

2 KiB could be saved by minifying CSS.

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.

Your largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Data use: We use cookies and similar tools to make your use…”.

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

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

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

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

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

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

5 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' tap response (inp) went from 241 ms to 220 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.7 MB in 153 requests on a phone: scripts 2.6 MB (73), other files 1.4 MB (55) and stylesheets 380 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://business.optum.com/content/dam/optum/dmp/logo.png")”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 23 pages on solutran.com and 26 external pages.

https://business.optum.com/en, https://business.optum.com/en.html and / all use the title “Optum Business - Helping to Create Better Healthcare Solutions”. Search engines can't tell which page to show for a search, so each competes with the others.

https://business.optum.com/en/insights/ai-brings-scale-precision-directed-spend-benefits.html has no meta description, so Google writes the search snippet from whatever text it finds.

https://business.optum.com/en, https://business.optum.com/en.html and / use the same meta description. A description written for each page earns more clicks.

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

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

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://prod.ui.search.optum.com/widget/v2.2.0/static/css/async/554.9c888462.css' from ori…”.

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

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

Opening the homepage sets 18 cookies (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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.