kanzengames.com website review

About 899 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (uploadly-cdn.com, Shopify and rebuyengine.com and others), adding 1.4 MB and 839 ms of main-thread time.

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

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

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

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

uploadly-cdn.com costs a phone 290 ms of main-thread work and 112 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.

rebuyengine.com costs a phone 173 ms of main-thread work and 332 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.

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

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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ready to Sell Your Cards? Trade-in your cards into store cr…”.

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

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

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

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

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

Your homepage downloads 5.9 MB in 275 requests on a phone: images 3.1 MB (41), scripts 1.6 MB (115) and other files 703 KiB (98). Under 2 MB keeps phones on slow connections fast.

984142-984180_DLC_S6_EN_MediaAlerts_Starters_All_1-1024x1024 weighs 551 KiB. On a phone connection a single image that size takes seconds.

3 images (688 KiB) are 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 1.68 g of CO₂e: 201.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

11 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

9 elements hidden from screen readers can still receive keyboard focus.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

12 visible links have no text or label, so screen readers cannot say where they go.

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 11 characters: “KanZenGames”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 606 pages on kanzengames.com and 9 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.

https://kanzengames.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://kanzengames.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://kanzengames.com/customer_authentication/redirect, https://kanzengames.com/collections/lego, https://kanzengames.com/collections/pokemon-sealed-in-stock, https://kanzengames.com/collections/pokemon-booster-box-1, https://kanzengames.com/collections/pokemon-elite-trainer-box and https://kanzengames.com/collections/pokemon-tcg-booster-bundle and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://kanzengames.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

The page uses urgency cues (a countdown or limited-time wording).

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