netrunnercards.net website review

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

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

15 images could be 498 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

6 third-party services load with your homepage (Shopify, Mailchimp and Cloudflare CDN and others), adding 802 KiB and 315 ms of main-thread time.

About 220 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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 2.1 MB in 162 requests on a phone: images 928 KiB (16), scripts 769 KiB (98) and other files 176 KiB (18). Under 2 MB keeps phones on slow connections fast.

1 image (58 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 0.60 g of CO₂e: 71.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Your title is only 20 characters: “Netrunner Cards Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 44 pages on netrunnercards.net and 1 external page.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://netrunnercards.net/collections/showdown, https://netrunnercards.net/pages/contact and https://netrunnercards.net/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

https://netrunnercards.net/products/stained-glass-bundle and https://netrunnercards.net/products/fine-art-playset-bundle use the same meta description. A description written for each page earns more clicks.

https://netrunnercards.net/collections/netrunner-cards, https://netrunnercards.net/collections/playmats, https://netrunnercards.net/collections/accessories, https://netrunnercards.net/collections/showdown, https://netrunnercards.net/collections/cards-for-organizers and https://netrunnercards.net/pages/contact and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

9 of 23 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 ()”.

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

The homepage has only about 97 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 6 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.