gwi.com website review

About 331 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and Cloudflare CDN and others), adding 913 KiB and 743 ms of main-thread time.

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

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

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

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

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.

1 image could be 39 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.

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 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “video-player”.

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

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

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

For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.

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

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

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

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

1 image 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' largest content (lcp) went from 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

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

The homepage links to 68 pages on gwi.com and 12 external pages.

Your Organization JSON-LD is missing name, logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 56 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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

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.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and HubSpot (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 4 cookies (measured from a US location before any click).

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