fixwellhockey.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Google CDN and Klaviyo and others), adding 1.8 MB and 612 ms of main-thread time.

Shopify costs a phone 417 ms of main-thread work and 1.2 MB 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,603 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google CDN costs a phone 100 ms of main-thread work and 352 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.

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

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

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

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

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

5 KiB could be saved by minifying CSS.

4 KiB could be saved by minifying JavaScript.

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

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

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

The first text or image appears after 2.0 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 4.4 MB in 491 requests on a phone: scripts 1.6 MB (120), other files 1.5 MB (271) and images 704 KiB (56). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example LOGO_NEW_ORANGE_noBG.png at 7,087 px wide, shown at 104 px. Resized copies would save about 101 KiB.

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

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

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

The homepage links to 141 pages on fixwellhockey.com and 21 external pages.

https://fixwellhockey.com/collections/goalie-sticks and https://fixwellhockey.com/collections/rea have no meta description, so Google writes the search snippet from whatever text it finds.

https://fixwellhockey.com/pages/new-subscriber, https://fixwellhockey.com/collections/refurbished-hockey-sticks and https://fixwellhockey.com/collections/all-refurbished-hockey-sticks have no <h1> headline, so visitors and search engines get no clear main topic.

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

31 of 82 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: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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.

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

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