gameness.com website review

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

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

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

8 third-party services load with your homepage (Osano CMP, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.2 MB and 1.1 s of main-thread time.

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

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

Google Tag Manager costs a phone 341 ms of main-thread work and 481 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.

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

Osano CMP costs a phone 351 ms of main-thread work and 67 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.

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

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

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

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

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

10 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “black belt friday animated gif featuring martial artists wi…”.

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

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

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

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

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

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

Your homepage downloads 3.6 MB in 259 requests on a phone: scripts 1.3 MB (78), images 1.2 MB (69) and other files 724 KiB (83). Under 2 MB keeps phones on slow connections fast.

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

44 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

Your title is 70 characters, so Google will cut it off around 60: “Gameness | BJJ Gis and Belts | Jiu Jitsu Rashguards | Wholesale Option”.

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

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

Your <h1> is empty.

The homepage links to 370 pages on gameness.com and 6 external pages.

/collections/mens-collection, /collections/mens-gis, /collections/mens-rashguards and /collections/mens-grappling-shorts-spats use the same meta description. A description written for each page earns more clicks.

/collections/belts, /collections/nogi, /collections/mens-rashguards, /collections/mens-grappling-shorts-spats, /collections/gloves-gear and /collections/gloves and 1 other took over 3 s to send their HTML from our server.

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

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

3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://gtm.gameness.com/g/collect?v=2&tid=G-1HDV80JXMT&gtm=45je6b41v883985019za20ozb830233527zd830…”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

gameness.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

gameness.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 14 cookies (measured from a US location before any click).

Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.