wizardsofthegrimoire.com website review

About 4.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 36.3 s faster on a phone.

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

YouTube costs a phone 2.1 s of main-thread work and 7.5 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.

5 images could be 94 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

8 third-party services load with your homepage (YouTube, amaicdn.com and preordernowapp.com and others), adding 8.8 MB and 2.6 s of main-thread time.

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

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

21 KiB could be saved by minifying JavaScript.

amaicdn.com costs a phone 174 ms of main-thread work and 404 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

Your largest element takes 57.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “"ONE HECK OF A SELF-CONTAINED DUELING GAME" - SPACEBIFF”.

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

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

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

The layout shifts by 0.103 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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 11.1 MB in 352 requests on a phone: scripts 7.9 MB (87), other files 974 KiB (192) and images 664 KiB (24). Under 2 MB keeps phones on slow connections fast.

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

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

4 frames have no title, so screen-reader users cannot tell what they contain.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is only 23 characters: “Wizards of the Grimoire”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 62 characters: “Wizards of the Grimoire is a strategy card game for 2 players.”. 70 to 160 characters is enough to sell the click.

There are 4 <h1> headlines (“”, “Kickstarter VIP Reservation” and “Wizards of the Grimoire”). One clear main headline is easier for people and search engines.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 20 pages on wizardsofthegrimoire.com and 11 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 https://wizardsofthegrimoire.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.

/ and https://wizardsofthegrimoire.com/products/wizards-of-the-grimoire-base-game all use the title “Wizards of the Grimoire”. Search engines can't tell which page to show for a search, so each competes with the others.

https://wizardsofthegrimoire.com/pages/gallery and https://wizardsofthegrimoire.com/pages/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

https://wizardsofthegrimoire.com/pages/gallery, https://wizardsofthegrimoire.com/pages/contact-us and https://wizardsofthegrimoire.com/products/1-kickstarter-vip-reservation have 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.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'defaultSetting')”.

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

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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