g5e.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Optimizely and others), adding 838 KiB and 765 ms of main-thread time.

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

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

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

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

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

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

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 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 238 ms to 251 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 3.5 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.3 MB in 131 requests on a phone: media 10.2 MB (2), scripts 901 KiB (34) and images 897 KiB (41). Under 2 MB keeps phones on slow connections fast.

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

2 buttons have no accessible name, so screen readers announce just “button”.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

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

4 tap targets are too small or too close together to hit reliably with a finger.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

The homepage links to 284 pages on g5e.com and 54 external pages.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 7 days; one year is the recommended minimum.

10 links go through two or more redirects, for example https://app.adjust.com/zcdnnn8?campaign=g5e.com&adgroup=mainpage.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

g5.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

g5.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage carries about 1,088 words of visible text.

DMARC is set to p=none, so mail pretending to be g5e.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.