stateofwow.com website review

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

4 images could be 277 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

6 third-party services load with your homepage (Google Tag Manager, Klaviyo and Cookie-Script.com and others), adding 361 KiB and 226 ms of main-thread time.

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

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

1 long task block the main thread while loading, the longest for 102 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content, ads and to analyse o…”. Most of its time is element render delay (2.8 s).

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

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

The first text or image appears after 1.9 s on a phone. Good is under 1.8 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 12.3 MB in 43 requests on a phone: media 11.3 MB (2), images 568 KiB (10) and scripts 352 KiB (18). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example state-of-wow-frontpage-header_2-1600x1067.jpg at 1,600 px wide, shown at 328 px. Resized copies would save about 108 KiB.

1 image (174 KiB) is 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.

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.stateofwow.com/app/uploads/2022/02/stateofwow-black.svg")”.

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

The homepage links to 18 pages on stateofwow.com and 17 external pages.

There is no https://www.stateofwow.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://www.stateofwow.com/esg-at-state-of-wow and https://www.stateofwow.com/cookie-privacy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.stateofwow.com/cookie-privacy has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.stateofwow.com/esg-at-state-of-wow took over 3 s to send its HTML from our server.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 519 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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 1 cookie (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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.