krakendice.com website review

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

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

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

8 third-party services load with your homepage (Shopify, bogos.io and Google CDN and others), adding 5.6 MB and 574 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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

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

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

The first text or image appears after 2.3 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 96 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.4 MB in 327 requests on a phone: images 6.2 MB (36), other files 1.3 MB (140) and scripts 645 KiB (106). Under 2 MB keeps phones on slow connections fast.

13 images are downloaded at several times the size a phone draws them, for example BLACK-Friday-2026-free-playmat.jpg at 2,000 px wide, shown at 50 px. Resized copies would save about 4.8 MB.

black-Friday-2026-new.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

4 images further down the page (199 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

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

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

The homepage links to 286 pages on krakendice.com and 25 external pages.

/collections/back-in-stock, /collections/14pc-resin-dice-sets and /collections/limited-edition-collector-sets have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

2 links go through two or more redirects, for example https://facebook.com/krakendice.

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.

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

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

DMARC is set to p=none, so mail pretending to be krakendice.com is still delivered. Add a report address, check the reports, then move to quarantine.

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