hellhades.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user LCP: 3.1 s

  3.1 s

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

• Tap response (INP) got 24% slower for real visitors

  +24%

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

• Real-user FCP: 2.3 s

  2.3 s

  Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

• Largest content (LCP) held steady for real visitors

  -7%

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

• Page weight: 4.1 MB

  4.1 MB

  Your homepage downloads 4.1 MB on a phone, 1.1 MB of it images (27%). Under 2 MB keeps phones on slow connections fast.

• 4 images in older formats

  4 images (1.1 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.

  Elements (4)

• 1 image far larger than shown

  242 KiB

  1 image is downloaded at several times the size a phone draws it, for example join_EA_banner-scaled.png at 2,560 px wide, shown at 321 px. Resized copies would save about 242 KiB.

  Elements (1)

• 1 image below the first screen load straight away

  1 image further down the page (277 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  Elements (1)

• About 1.2 g of CO₂ per visit

  1.16 g

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

• 3 text elements with low contrast

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

  Elements (3)

• Links look like plain text

  3 links inside paragraphs rely on colour alone to stand out.

  Elements (3)

• All page content should be contained by landmarks (3 elements)

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

  Elements (3)

• Headings skip levels

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

  Elements (1)

• 2 H1 headlines

  There are 2 <h1> headlines (“The home of Raid: Shadow Legends guides, tools & …” and “Tools, Tier lists and guides for RPG hero collect…”). One clear main headline is easier for people and search engines.

• 526 internal links, 35 external

  The homepage links to 526 pages on hellhades.com and 35 external pages.

• No llms.txt

  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.

• 2 pages without a meta description

  /the-arbiter-missions-and-rewards and /raid/faction-wars-tier-list have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (2)

• 15 pages without an H1

  /blog, /raid/new-player-promo-link-generator, /raid/new-player-guide, /guide-to-affinity-raid-shadow-legends, /raid/guide-to-champion-ascension and /raid-shadow-legends-debuffs-buffs and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 4 broken images

  4 images failed to load on a phone, for example https://token.rubiconproject.com/token?pid=50242&puid=AU1D-0100-001791768203-Q5B2DJ2A-52YI&gdpr=0.

• 7 small tap targets

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

• 4 JavaScript errors while loading

  4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) NotSupportedError: Failed to execute 'browsingTopics' on 'Document': document.browsingTopics() is…”.

• No HSTS header

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

• No Content-Security-Policy

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

• No clickjacking protection

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

• No X-Content-Type-Options

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

• 2 links through redirect chains

  2 links go through two or more redirects, for example https://pl.go-ga.me/pmc5ikqv.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• No security.txt

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

• No CAA record

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

• DNSSEC is off

  hellhades.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 social proof

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

• No direct contact details

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

• About 671 words of copy

  The homepage carries about 671 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be hellhades.com is still delivered. Reports are on, so moving to quarantine is the next step.

• Email authentication score: 75/100

  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.

• 8 trackers load before any consent

  8

  Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 3 mores (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.

• 20 cookies set on arrival

  20

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

• No consent tool detected

  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.

• 60 other companies contacted

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