g1g.com website review

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

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

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

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

8 third-party services load with your homepage (ZenDesk, Google Tag Manager and Google Maps and others), adding 1.5 MB and 702 ms of main-thread time.

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

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

ZenDesk costs a phone 275 ms of main-thread work and 437 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 1,821 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google Maps costs a phone 99 ms of main-thread work and 394 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 long tasks block the main thread while loading, the longest for 210 ms. During a long task the page ignores taps.

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

34 KiB could be saved by minifying JavaScript.

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

6 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 29.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “#1 rated · 41 years of service Travel insurance you can tru…”.

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

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

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

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

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

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

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 22.6 MB in 154 requests on a phone: media 17.1 MB (3), scripts 2.1 MB (32) and fonts 2.1 MB (6). Under 2 MB keeps phones on slow connections fast.

8 images (685 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.

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

8 images are downloaded at several times the size a phone draws them, for example adventure.png at 610 px wide, shown at 167 px. Resized copies would save about 274 KiB.

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

Heading levels should only increase by one: 6 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

<td> elements in a large <table> do not have table headers. (1 element).

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No XML sitemap at https://g1g.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

A phone browser shows 6,888 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://g1g.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.

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

3 errors were logged to the browser console while the page loaded, for example “Manifest: Line: 1, column: 1, Syntax error.”.

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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