dc.com website review

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

cloudfront.net costs a phone 1.9 s of main-thread work and 2.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (cloudfront.net, awswaf.com and Optanon and others), adding 3.8 MB and 2.3 s of main-thread time.

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

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

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

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

awswaf.com costs a phone 241 ms of main-thread work and 304 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.

Optanon costs a phone 183 ms of main-thread work and 322 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.

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

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

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

Polyfills for old browsers add 49 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.

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.

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

Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Connecting with "Clayface"”.

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

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

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

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

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

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

Your homepage downloads 13.9 MB in 269 requests on a phone: images 8.3 MB (57), scripts 3.1 MB (106) and other files 2.1 MB (78). Under 2 MB keeps phones on slow connections fast.

dc-logo-313x313.svg weighs 6.3 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example dc-logo-313x313.svg at 150 px wide, shown at 40 px. Resized copies would save about 2.3 MB.

2026_10_30_ClayfaceReaction_BlogRoll_Mobile_4x3.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).

1 image (112 KiB) is 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 3.95 g of CO₂e: 473.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.

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

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

There are 6 <h1> headlines (“CLAYFACE – FINAL TRAILER”, “WONDER WOMAN” and “CLAYFACE”). One clear main headline is easier for people and search engines.

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

The homepage links to 44 pages on dc.com and 64 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.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

robots.txt blocks GPTBot, 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.

/news and /videos use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /ComicShopLocator, whose canonical is /blog/2021/10/14/dc-comic-shop-locator. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/comics, /ComicShopLocator, /blog/2026-10-30/connecting-with-clayface, /blog/2026-10-30/bleeding-hearts-what-happens-when-a-zombie-feels-alive and /blog/2026-10-29/classic-creepouts-five-truly-terrifying-dc-animated-episodes have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) PlayerError: Error loading content "mec5155a7ec3d90517611b0f513729184be602714e"”.

Chrome logged issues while loading the page (“Cookie”).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

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