graymattergaming.org website review

hcaptcha.com costs a phone 1.3 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Shopify and others), adding 3.3 MB and 3.1 s of main-thread time.

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

11 images could be 854 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.

Shopify costs a phone 485 ms of main-thread work and 737 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.

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

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

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

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

17 KiB could be saved by minifying JavaScript.

About 10 KiB of CSS is downloaded but never applied on this page.

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Now with 4' x 4' Sizes!”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 87 ms to 92 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.0 MB in 306 requests on a phone: scripts 2.9 MB (83), images 1.6 MB (32) and other files 940 KiB (152). Under 2 MB keeps phones on slow connections fast.

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

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

7 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is 69 characters, so Google will cut it off around 60: “Wargaming Battle Mats, Objective Markers & Trays | Gray Matter Gaming”.

There are 2 <h1> headlines (“” and “Also new Double Sided Bloody Fantasy Football Mat…”). One clear main headline is easier for people and search engines.

Your meta description is 307 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 67 pages on graymattergaming.org and 10 external pages.

https://graymattergaming.org/products/warhammer-40k-acrylic-terrain-markers-10th-edition-tournament-2023 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://graymattergaming.org/products/warhammer-40k-acrylic-terrain-markers-10th-edition-tournament-2023 all use the title “Wargaming Battle Mats, Objective Markers & Trays | Gray Matter Gaming”. Search engines can't tell which page to show for a search, so each competes with the others.

https://graymattergaming.org/collections/objective-markers, https://graymattergaming.org/collections/terrain-markers, https://graymattergaming.org/collections/movement-trays, https://graymattergaming.org/collections/tabletop-terrain, https://graymattergaming.org/collections/baron-of-dice and https://graymattergaming.org/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://graymattergaming.org/collections/tabletop-terrain, https://graymattergaming.org/collections/baron-of-dice, https://graymattergaming.org/pages/reviews-and-videos and https://graymattergaming.org/pages/gaming-groups-stores-and-events have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

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

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 1,328 words of visible text.

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