shopthewalkingdead.com website review

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

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

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

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

8 third-party services load with your homepage (jQuery CDN, Facebook and Azure Web Services and others), adding 1.9 MB and 966 ms of main-thread time.

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

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

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

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

jQuery CDN costs a phone 303 ms of main-thread work and 127 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.

Azure Web Services costs a phone 123 ms of main-thread work and 354 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.

Klaviyo costs a phone 123 ms of main-thread work and 345 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.

Ada costs a phone 82 ms of main-thread work and 516 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.

107 KiB could be saved by minifying JavaScript.

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

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

About 42 KiB of CSS is downloaded but never applied on this page.

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.

2 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 28.5 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 29.2 s. Good is under 3.8 s.

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.

7 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 128 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.6 MB in 413 requests on a phone: images 2.8 MB (97), scripts 1.9 MB (104) and other files 1.2 MB (143). Under 2 MB keeps phones on slow connections fast.

3037956126761588078_2048.jpg weighs 537 KiB. On a phone connection a single image that size takes seconds.

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

3 images are downloaded at several times the size a phone draws them, for example 7548352101837433687_2048.jpg at 2,048 px wide, shown at 350 px. Resized copies would save about 284 KiB.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

68 links have no real href, so search engines can't follow them.

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

The homepage links to 187 pages on shopthewalkingdead.com and 17 external pages.

robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://thewalkingdeadshop.amc.com/collections/the-walking-dead-daryl-dixon, https://thewalkingdeadshop.amc.com/collections/dead-city, https://thewalkingdeadshop.amc.com/collections/the-walking-dead-the-ones-who-live and https://thewalkingdeadshop.amc.com/collections/little-ass-kickers-collection have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://thewalkingdeadshop.amc.com/cdn/shop/t/74/assets/x' because its MIME type ('text/ht…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

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

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