schlesingergroup.com website review

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

About 237 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.

9 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Usercentrics CMP and Hubspot and others), adding 995 KiB and 944 ms of main-thread time.

Your mobile performance score is 52 (desktop: 38). Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 651 ms of main-thread work and 552 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 375 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

26 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 26 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.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Driven by curiosity. Built on listening. 60 years strong.”. Most of its time is element render delay (2.4 s).

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

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

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

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

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

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

Your homepage downloads 18.0 MB in 209 requests on a phone: images 16.1 MB (56), scripts 1.2 MB (57) and stylesheets 295 KiB (33). Under 2 MB keeps phones on slow connections fast.

9 images weigh 13.3 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example defaulttab.png at 1,495 px wide, shown at 311 px. Resized copies would save about 1.8 MB.

11 images (14.1 MB) are 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.

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

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

Some list items are not inside a list.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 186 pages on schlesingergroup.com and 21 external pages.

There is no https://sago.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://sago.com/en, https://sago.com/fr, https://sago.com/de and https://sago.com/es all use the title “Home | Sago”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sago.com/fr and https://sago.com/de have no meta description, so Google writes the search snippet from whatever text it finds.

https://sago.com/en/solutions/sagoverify and https://sago.com/en/solutions/platforms/methodify use the same meta description. A description written for each page earns more clicks.

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

https://sago.com/what-we-offer and https://sago.com/en/solutions/platforms/qualmeeting took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'jobs')”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

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