imagecomics.com website review

181 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 2.5 s.

Your mobile performance score is 57 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

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

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

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

3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Cloudflare), adding 321 KiB and 157 ms of main-thread time.

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

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

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

Desktop scores 86 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Discover new comics hitting shelves this week for #NewComic…”.

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

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

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

Your homepage downloads 5.7 MB in 200 requests on a phone: images 4.9 MB (184), scripts 399 KiB (5) and fonts 311 KiB (6). Under 2 MB keeps phones on slow connections fast.

10 images (1.0 MB) 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.

5 images are downloaded at several times the size a phone draws them, for example _3b6a306af1.jpg at 1,200 px wide, shown at 370 px. Resized copies would save about 129 KiB.

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

11 elements hidden from screen readers can still receive keyboard focus.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Structured data found (BreadcrumbList and Organization) but with 1 problem, for example “Organization: missing name”.

1 link has no real href, so search engines can't follow it.

The homepage links to 238 pages on imagecomics.com and 20 external pages.

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, ClaudeBot, Google-Extended, Applebot-Extended 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.

/comics/read-first-issues, /press-releases/tony-fleecs-tim-seeley-have-each-sold-millions-of-copies-across-respective-bestsellers-stray-dogs-revival-more-now-theyre-teaming-up-to-launch-the-princess-murders-this-december, /press-releases/from-hell-meets-fatale-in-mirka-andolfos-long-awaited-follow-up-to-mercy-the-upcoming-merciless-launching-this-december and /press-releases/upcoming-creature-corps-series-launch-promises-ultra-violent-battle-packed-showdown-this-december use the same meta description. A description written for each page earns more clicks.

/comics/new-releases and /comics/read-first-issues have no <h1> headline, so visitors and search engines get no clear main topic.

/comics/coming-soon has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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

3 links go through two or more redirects, for example https://www.facebook.com/pages/Image-Comics-Inc/178643148813259.

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.

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

imagecomics.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 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 758 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 Analytics and Google Tag Manager (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 4 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.