dieharddice.com website review

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

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

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

17 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

8 third-party services load with your homepage (dfktv2.com, Clarity and rebuyengine.com and others), adding 1.4 MB and 821 ms of main-thread time.

About 532 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 420 ms faster on a phone.

11 images could be 447 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

dfktv2.com costs a phone 320 ms of main-thread work and 432 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.

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

rebuyengine.com costs a phone 167 ms of main-thread work and 720 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 58 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.

7 KiB could be saved by minifying CSS.

Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need.

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

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

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

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

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

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

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

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

Your homepage downloads 36.8 MB in 281 requests on a phone: images 34.3 MB (74), scripts 1.2 MB (63) and other files 808 KiB (111). Under 2 MB keeps phones on slow connections fast.

5 images weigh 31.3 MB together. On a phone connection a single image that size takes seconds.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

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

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

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

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 281 pages on dieharddice.com and 21 external pages.

https://www.dieharddice.com/pages/spring-loot, https://www.dieharddice.com/collections/all, https://www.dieharddice.com/collections/gift-cards, https://www.dieharddice.com/collections/mystery-products and https://www.dieharddice.com/collections/portable-dice-trays have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.dieharddice.com/pages/spring-loot and https://www.dieharddice.com/pages/shipping have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 images are served at too low a resolution for sharp phone screens.

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

The homepage carries about 1,269 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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 19 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.