g2o.com website review

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

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

About 306 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

About 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

49 KiB could be saved by minifying JavaScript.

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and LinkedIn Ads and others), adding 755 KiB and 350 ms of main-thread time.

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

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

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

13 KiB could be saved by minifying CSS.

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.

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

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

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “It goes beyond digital transformation. It reimagines custom…”. Most of its time is element render delay (4.4 s).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.2 MB in 55 requests on a phone: images 1.2 MB (13), scripts 832 KiB (15) and fonts 121 KiB (3). Under 2 MB keeps phones on slow connections fast.

5 images (511 KiB) 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.

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

1 image is downloaded at several times the size a phone draws it, for example CXTdefinition-900x600.jpg at 900 px wide, shown at 283 px. Resized copies would save about 8 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 75.2 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.

1 tap target is too small or too close together to hit reliably with a finger.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 68 pages on g2o.com and 3 external pages.

There is no https://g2o.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://g2o.com/industries-expertise/public-sector-consulting and https://g2o.com/contentful-migration-services have no meta description, so Google writes the search snippet from whatever text it finds.

https://g2o.com/ai-powered-legacy-software-modernization, https://g2o.com/innovation-alignment-sprint, https://g2o.com/performance-testing-services and https://g2o.com/strategy-to-impact-roadmapping use the same meta description. A description written for each page earns more clicks.

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

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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 596 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 (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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