Website review, no card needed
gamenerdz.com website review
Visit site (opens in a new tab)Reviewed 11 October 202646 issues · 90 checks
This review found 46 issues worth fixing on gamenerdz.com, 21 of them high impact, across 90 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
72C- #94,946 of 122,520 reviewed websitesbeats 19%
- #58,755 of 69,186 online storesbeats 12%
- #633 of 891 BigCommerce storesbeats 24%
Closest competitors among BigCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 2.0 s |
| Apr 25, 2026 | 2.0 s |
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 89 ms |
| Apr 25, 2026 | 90 ms |
| May 2, 2026 | 90 ms |
| May 9, 2026 | 89 ms |
| May 16, 2026 | 91 ms |
| May 23, 2026 | 94 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 96 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 97 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 97 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
29.6 s · 5.1 MB8 images could be 5.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 29.6 s faster on a phone.
Use efficient cache lifetimes
25.8 s · 4.6 MB28 files are served with short cache lifetimes, so returning visitors download them again (4.6 MB).
Reduce unused JavaScript
4.7 s · 948 KiBAbout 948 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.
Render-blocking requests
1.2 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 30). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, 99minds.io and Bigcommerce and others), adding 7.8 MB and 1.4 s of main-thread time.
Amazon Web Services adds 50 ms
50 msAmazon Web Services costs a phone 50 ms of main-thread work and 4.1 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.
Bigcommerce adds 275 ms
275 msBigcommerce costs a phone 275 ms of main-thread work and 1.7 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.
Google Tag Manager adds 362 ms
362 msGoogle Tag Manager costs a phone 362 ms of main-thread work and 701 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.
Legacy JavaScript
350 ms · 52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
99minds.io adds 288 ms
288 ms99minds.io costs a phone 288 ms of main-thread work and 744 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.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 218 ms. During a long task the page ignores taps.
Reduce unused CSS
29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user CLS: 0.78
0.78For real visitors the layout shifts by 0.78 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 48.9 s
48.9 sYour largest element takes 48.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dungeon Crawler Carl”.
Time to Interactive: 48.9 s
48.9 sThe page becomes fully interactive after 48.9 s. Good is under 3.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 604 ms
604 msScripts block taps and scrolling for 604 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.16
0.16The layout shifts by 0.16 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 89 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 97 ms
97 msReal visitors wait 97 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 295 ms
295 msReal visitors wait 295 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 8.5 MB in 123 requests
8.5 MBYour homepage downloads 8.5 MB in 123 requests on a phone: images 5.3 MB (11), scripts 2.6 MB (62) and other files 511 KiB (33). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
3.5 MB5 images are downloaded at several times the size a phone draws them, for example 1791651135196-dungeoncarl.png at 1,920 px wide, shown at 220 px. Resized copies would save about 3.5 MB.
1 image below the first screen load straight away
1 image further down the page (278 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.41 g of CO₂e: 288.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
52 text elements with low contrast
52 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (114 characters)
Your title is 114 characters, so Google will cut it off around 60: “Gamenerdz.com - Board Games, Magic The Gathering, Pokemon, Table Top Games, Dungeons & Dr…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.gamenerdz.com/sitemap.xml, so Google discovers your pages only by following links.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
21 internal links, 5 external
The homepage links to 21 pages on gamenerdz.com and 5 external pages.
3 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Board Games, MTG, Magic: the Gathering, Yu-Gi-Oh, Pokemon, Role Playing Games, Dungeons & Dragons, Warhammer Miniatures…”.
Canonical URL set
The canonical URL is https://www.gamenerdz.com/.
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
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.
Some text only appears after JavaScript runs
31%The HTML your server sends has 96 of the 306 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.gamenerdz.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.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
1 page points its canonical at the homepage
https://www.gamenerdz.com/compare 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.
2 pages share a title
/ and https://www.gamenerdz.com/compare all use the title “Gamenerdz.com - Board Games, Magic The Gathering, Pokemon, Table Top …”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages without a meta description
https://www.gamenerdz.com/gift-card, https://www.gamenerdz.com/sitemap.php, https://www.gamenerdz.com/preorders, https://www.gamenerdz.com/deals, https://www.gamenerdz.com/board-games and https://www.gamenerdz.com/card-games and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages with very little text
https://www.gamenerdz.com/compare, https://www.gamenerdz.com/gift-card, https://www.gamenerdz.com/preorders, https://www.gamenerdz.com/deals, https://www.gamenerdz.com/board-games and https://www.gamenerdz.com/card-games and 6 others 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.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.
2 checks passed
Tap targets are thumb-sized
43 of 51 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 306 words of copy
The homepage carries about 306 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CALL US AT 1-888-75-NERDZ” and “REGISTER”.
4 calls to action
The homepage has 4 calls to action, for example “Register”, “Call us at 1-888-75-NERDZ” and “Subscribe”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 3 mores (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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies (measured from a US location before any click).
No consent tool detected
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.
40 other companies contacted
Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at gamenerdz.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on gamenerdz.com, including 21 speed issues, 6 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.