Skip to content
Audit Complete

Results for https://metal-archives.com

Visit site
United Stated United Stated · New York Completed: Apr 22, 2026 22:33 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
B80

Site Health

Score: 80 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Good foundation, but a few gaps could be exploited.

Major barriers for users with disabilities — up to 15% of your audience.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Cloudflare Rocket Loader · 58 peers
You 80
·
Avg 74
+6 above average
0 50 100
Better than 91% of Cloudflare Rocket Loader sites See full Cloudflare Rocket Loader benchmark →
Google Search Console · 3591 peers
You 80
·
Avg 73
+7 above average
0 50 100
Better than 95% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

1 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
5

4 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fmetal-archives.com)](https://beavercheck.com/results/d1894ae7-66c1-4776-bb3a-548c71434590)
<a href="https://beavercheck.com/results/d1894ae7-66c1-4776-bb3a-548c71434590"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmetal-archives.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmetal-archives.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

2 critical 8 warning

10 barrier(s) likely increasing bounce by ~28%.

Speed (1)

High main-thread blocking time

+2% bounce

Page is non-interactive for 204ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

4 form field(s) without a label

+6% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (3)

18 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

3 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$450 investment → $0.15/month returns + USD 157,500 risk avoided

Payback period: > 2 years First-year ROI: -100%

Investment

$450

4h · 5 findings

Monthly returns

$0.15 /mo

~$1.79 / year

  • Bandwidth savings $0.15

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$450

4.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,125 / month at risk

~$157,502 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+6 more

Bandwidth Waste

$0.15 /mo

1864.2 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~186 KB per page load
    Saves $0.15/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

85
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
73
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
75
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

933 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.20 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

204 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.218

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.39 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

3.45 s

Detailed Report

Audit breakdown by category with detailed findings.

85

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.218138] map[node:map[boundingRect:map[bottom:834 height:318 left:573 right:935 top:516 width:362] lhId:page-6-DIV nodeLabel:Latest updates: Bands Labels Artists Incandesca April 22, 18:32 Last Days of … path:1,HTML,1,BODY,0,DIV,2,DIV,2,DIV,1,DIV selector:div#wrapper > div#content_wrapper > div#latest > div#lastUpdated snippet:<div id="lastUpdated" class="block"> type:node] score:0.218138 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1934 height:193 left:195 right:485 top:1741 width:290] lhId:page-0-IMG nodeLabel:div#news > div.motd > p.body > img path:1,HTML,1,BODY,0,DIV,2,DIV,3,DIV,5,DIV,1,P,9,IMG selector:div#news > div.motd > p.body > img snippet:<img src="/images/ozzy.webp" style="width: calc(100% - 450px)"> type:node]]] type:subitems]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div#news > div.motd > p.body > img div#news > div.motd > p.body > img
metal-archives.com/images/ozzy.webp345.0 KiB317.1 KiB
Username Password Login Register Forgot login? body > div#wrapper > div#left_col > div#member_box
metal-archives.com/css/default/images/ui-bg_grain.png22.6 KiB16.0 KiB
Metal Archives body > div#wrapper > div#header > a#MA_logo
metal-archives.com/css/default/images/smallerlogo.jpg21.4 KiB13.6 KiB
Inhale Blue Moment April 22nd Concerto Moon Between Live and... April 22nd … div#content_wrapper > div#latest > div#upcomingAlbums > div.tabs
metal-archives.com/css/default/images/ui-bg_waves.png19.7 KiB13.2 KiB
Bands alphabetical country genre Labels alphabetical country Reviews R.I.P. Ran… body > div#wrapper > div#left_col > div#left_menu_box
metal-archives.com/css/default/images/ui-bg_webs.png7.1 KiB4.5 KiB

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
metal-archives.com/min/index.php?g=css&v=12511.9 KiB160 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Latest updates: Bands Labels Artists Incandesca April 22, 18:32 Last Days of … div#wrapper > div#content_wrapper > div#latest > div#lastUpdated
0.218

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 75.0 KiB
URLTransfer SizeEst Savings
metal-archives.com/min/index.php?g=js&v=127106.0 KiB75.0 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div#news > div.motd > p.body > img div#news > div.motd > p.body > img
metal-archives.com/images/ozzy.webp

More information about the performance of your application. These numbers don't directly affect the Performance score.

Time to Interactive 3.5 s
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoids enormous network payloads Total size was 607 KiB
JavaScript execution time 0.9 s
Minimizes main-thread work 1.4 s
Avoid long main-thread tasks 5 long tasks found
Network Requests
Network Round Trip Times 10 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 140 ms
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid non-composited animations
73

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest additions: div#content_wrapper > div#latest > div#lastAdded > span.header
Latest updates: div#content_wrapper > div#latest > div#lastUpdated > span.header
Latest reviews: div#content_wrapper > div#latest > div#lastReviews > span.header
Upcoming albums div#content_wrapper > div#latest > div#upcomingAlbums > span.header

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#news > div.motd > p.body > img div#news > div.motd > p.body > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#search_box > form#search_form > div > input#searchQueryBox div#search_box > form#search_form > div > input#searchQueryBox
div#member_box > form#login_form > div > input div#member_box > form#login_form > div > input
div#member_box > form#login_form > div > input div#member_box > form#login_form > div > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Band name Music genre Themes Album title Song title Label Artist User profile G… div#search_box > form#search_form > div > select

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#search_box > form#search_form > div > input#searchQueryBox div#search_box > form#search_form > div > input#searchQueryBox
Band name Music genre Themes Album title Song title Label Artist User profile G… div#search_box > form#search_form > div > select
Advanced search div#search_box > form#search_form > div > a.float_left
Submit div#search_box > form#search_form > div > button.btn_submit

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
alphabetical li > ul > li > a
country li > ul > li > a
genre li > ul > li > a
alphabetical li > ul > li > a
country li > ul > li > a
R.I.P. div#left_menu_box > ul.menu_style_3 > li > a
Random Band div#left_menu_box > ul.menu_style_3 > li > a
User rankings div#left_menu_box > ul.menu_style_3 > li > a
News archive div#left_menu_box > ul.menu_style_3 > li > a
Reports div#left_menu_box > ul.menu_style_3 > li > a
Wotans Macht tr > td > span.forceBreak > a
Ⱂⱆⱍⰵ Ⰿⱁⰼ tr > td > span.forceBreak > a
Profanomancer tr > td > span.forceBreak > a
Hurmos tr > td > span.forceBreak > a
H. Mortiz tr > td > span.forceBreak > a
Irrational Exuberants tr > td > span.forceBreak > a
Dragged into Obliteration tr > td > span.forceBreak > a
Doomantra tr > td > span.forceBreak > a
Cornucopia tr > td > span.forceBreak > a
Fuck White God tr > td > span.forceBreak > a
Vasodilator tr > td > span.forceBreak > a
Ganid tr > td > span.forceBreak > a
Indignance tr > td > span.forceBreak > a
Contaminate tr > td > span.forceBreak > a
Ghost Bath tbody > tr > td > a
Shot to Hell tbody > tr > td > a
Ghost Bath tr > td > span.forceBreak > a
Moonlover tbody > tr > td > a
At the Gates tr > td > span.forceBreak > a
With Fear I Kiss... tbody > tr > td > a
Warside tr > td > span.forceBreak > a
Cognitive Extinction tbody > tr > td > a
Oromet tr > td > span.forceBreak > a
The Sinking Isle tbody > tr > td > a
Necrony tr > td > span.forceBreak > a
Promo Tape '93-'94 tbody > tr > td > a
Коммунизм 2077 tr > td > span.forceBreak > a
Дестрой tbody > tr > td > a
Hail the Void tr > td > span.forceBreak > a
Memento Mori tbody > tr > td > a
Immortal tr > td > span.forceBreak > a
Battles in the North tbody > tr > td > a
Dead Again tbody > tr > td > a
Immortal tr > td > span.forceBreak > a
Diabolical... tbody > tr > td > a
Sawed Apart tr > td > span.forceBreak > a
Bone Harvester tbody > tr > td > a
Συντριμμια tr > td > span.forceBreak > a
Repulsive... tbody > tr > td > a
Doedsvangr tr > td > span.forceBreak > a
Within the Flesh tbody > tr > td > a
Black Abyss tr > td > span.forceBreak > a
The Overflowing... tbody > tr > td > a
Survive/Yourself tbody > tr > td > a
Dead Void tr > td > span.forceBreak > a
Volatile Forms tbody > tr > td > a
Hellripper tr > td > span.forceBreak > a
Coronach tbody > tr > td > a
Between Live and... tbody > tr > td > a
A Grotesque... tbody > tr > td > a
I Don't Care tbody > tr > td > a
Cardiomyotomy tr > td > span.forceBreak > a
Beautifying... tbody > tr > td > a
Deadzone tr > td > span.forceBreak > a
Deliberate tbody > tr > td > a
Extinction A.D. tr > td > span.forceBreak > a
Truth or... tbody > tr > td > a
Hans & Valter tr > td > span.forceBreak > a
The Prophecy tbody > tr > td > a
Without Dreams tr > td > span.forceBreak > a
Mana Diagram tr > td > span.forceBreak > a
Where Victims Lie tr > td > span.forceBreak > a
Coven of the Swamp tr > td > span.forceBreak > a
The Veil tbody > tr > td > a
A Figment of... tbody > tr > td > a
Falling Leaves tbody > tr > td > a
Ural tr > td > span.forceBreak > a
Anthropic Genetic... tbody > tr > td > a
Rahvira tr > td > span.forceBreak > a
In the Darkness... tbody > tr > td > a
Seum tr > td > span.forceBreak > a
Parking Life tbody > tr > td > a
Hagane tr > td > span.forceBreak > a
We Are the Knight tbody > tr > td > a
Bloody Falls tr > td > span.forceBreak > a
Mother, Your Son... tbody > tr > td > a
Vomit Forth tr > td > span.forceBreak > a
In the Name of... tbody > tr > td > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ghost Bath Ghost Bath Apr 22nd Black Label Society Shot to Hell Apr 22nd Gh… div.tabs > div.block > div.ui-tabs-panel-content > table
Inhale Blue Moment April 22nd Concerto Moon Between Live and... April 22nd … div.tabs > div.block > div.ui-tabs-panel-content > table
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Access to XMLHttpRequest at 'https://www.metal-archives.com/index/ajax-stats' from origin 'https://metal-archives.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to XMLHttpRequest at 'https://www.metal-archives.com/user/session' from origin 'https://metal-archives.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
75

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#news > div.motd > p.body > img div#news > div.motd > p.body > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
70
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
75
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

277 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

634 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.043

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

465 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

638 ms

Detailed Report

Audit breakdown by category with detailed findings.

100

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div#news > div.motd > p.body > img div#news > div.motd > p.body > img
metal-archives.com/images/ozzy.webp345.0 KiB302.8 KiB
Username Password Login Register Forgot login? body > div#wrapper > div#left_col > div#member_box
metal-archives.com/css/default/images/ui-bg_grain.png22.6 KiB16.0 KiB
Metal Archives body > div#wrapper > div#header > a#MA_logo
metal-archives.com/css/default/images/smallerlogo.jpg21.4 KiB13.6 KiB
Inhale Blue Moment April 22nd Concerto Moon Between Live and... April 22nd … div#content_wrapper > div#latest > div#upcomingAlbums > div.tabs
metal-archives.com/css/default/images/ui-bg_waves.png19.7 KiB13.2 KiB
Bands alphabetical country genre Labels alphabetical country Reviews R.I.P. Ran… body > div#wrapper > div#left_col > div#left_menu_box
metal-archives.com/css/default/images/ui-bg_webs.png7.1 KiB4.5 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
metal-archives.com/min/index.php?g=css&v=12511.9 KiB50 ms

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 75.1 KiB
URLTransfer SizeEst Savings
metal-archives.com/min/index.php?g=js&v=127106.0 KiB75.1 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div#news > div.motd > p.body > img div#news > div.motd > p.body > img
metal-archives.com/images/ozzy.webp

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 0.6 s
Max Potential First Input Delay 40 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoids enormous network payloads Total size was 608 KiB
JavaScript execution time 0.1 s
Minimizes main-thread work 0.4 s
Network Requests
Network Round Trip Times 10 ms
Server Backend Latencies 10 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 130 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
70

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest additions: div#content_wrapper > div#latest > div#lastAdded > span.header
Latest updates: div#content_wrapper > div#latest > div#lastUpdated > span.header
Latest reviews: div#content_wrapper > div#latest > div#lastReviews > span.header
Upcoming albums div#content_wrapper > div#latest > div#upcomingAlbums > span.header

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
oneyoudontknow div#news > div.motd > p.body > a
Metal Graphs div#news > div.motd > p.body > a
here div#news > div.motd > p.body > a
here div#news > div.motd > p.body > a
Voidsel div#news > div.motd > p.body > a
here div#news > div.motd > p.body > a
this thread div#news > div.motd > p.body > a
Diamhea div#news > div.motd > p.body > a
BastardHead div#news > div.motd > p.body > a
here div#news > div.motd > p.body > a
here div#news > div.motd > p.body > a
here div#news > div.motd > p.body > a
BastardHead div#news > div.motd > p.body > a
here div#news > div.motd > p.body > a
here div#news > div.motd > p.body > a
news item from over 7 years ago div#news > div.motd > p.body > a
a neat and shiny list in HTML table form div#news > div.motd > p.body > a
the thread's opening post div#news > div.motd > p.body > a
email me div#news > div.motd > p.body > a

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#news > div.motd > p.body > img div#news > div.motd > p.body > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#search_box > form#search_form > div > input#searchQueryBox div#search_box > form#search_form > div > input#searchQueryBox
div#member_box > form#login_form > div > input div#member_box > form#login_form > div > input
div#member_box > form#login_form > div > input div#member_box > form#login_form > div > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Band name Music genre Themes Album title Song title Label Artist User profile G… div#search_box > form#search_form > div > select

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#search_box > form#search_form > div > input#searchQueryBox div#search_box > form#search_form > div > input#searchQueryBox
Band name Music genre Themes Album title Song title Label Artist User profile G… div#search_box > form#search_form > div > select
Advanced search div#search_box > form#search_form > div > a.float_left
Submit div#search_box > form#search_form > div > button.btn_submit

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
alphabetical li > ul > li > a
country li > ul > li > a
genre li > ul > li > a
alphabetical li > ul > li > a
country li > ul > li > a
R.I.P. div#left_menu_box > ul.menu_style_3 > li > a
Random Band div#left_menu_box > ul.menu_style_3 > li > a
User rankings div#left_menu_box > ul.menu_style_3 > li > a
News archive div#left_menu_box > ul.menu_style_3 > li > a
Reports div#left_menu_box > ul.menu_style_3 > li > a
Wotans Macht tr > td > span.forceBreak > a
Ⱂⱆⱍⰵ Ⰿⱁⰼ tr > td > span.forceBreak > a
Profanomancer tr > td > span.forceBreak > a
Hurmos tr > td > span.forceBreak > a
H. Mortiz tr > td > span.forceBreak > a
Irrational Exuberants tr > td > span.forceBreak > a
Dragged into Obliteration tr > td > span.forceBreak > a
Doomantra tr > td > span.forceBreak > a
Cornucopia tr > td > span.forceBreak > a
Fuck White God tr > td > span.forceBreak > a
Vasodilator tr > td > span.forceBreak > a
Ganid tr > td > span.forceBreak > a
Indignance tr > td > span.forceBreak > a
Contaminate tr > td > span.forceBreak > a
Ghost Bath tbody > tr > td > a
Shot to Hell tbody > tr > td > a
Ghost Bath tr > td > span.forceBreak > a
Moonlover tbody > tr > td > a
At the Gates tr > td > span.forceBreak > a
With Fear I Kiss... tbody > tr > td > a
Warside tr > td > span.forceBreak > a
Cognitive Extinction tbody > tr > td > a
Oromet tr > td > span.forceBreak > a
The Sinking Isle tbody > tr > td > a
Necrony tr > td > span.forceBreak > a
Promo Tape '93-'94 tbody > tr > td > a
Коммунизм 2077 tr > td > span.forceBreak > a
Дестрой tbody > tr > td > a
Hail the Void tr > td > span.forceBreak > a
Memento Mori tbody > tr > td > a
Immortal tr > td > span.forceBreak > a
Battles in the North tbody > tr > td > a
Dead Again tbody > tr > td > a
Immortal tr > td > span.forceBreak > a
Diabolical... tbody > tr > td > a
Sawed Apart tr > td > span.forceBreak > a
Bone Harvester tbody > tr > td > a
Συντριμμια tr > td > span.forceBreak > a
Repulsive... tbody > tr > td > a
Doedsvangr tr > td > span.forceBreak > a
Within the Flesh tbody > tr > td > a
Black Abyss tr > td > span.forceBreak > a
The Overflowing... tbody > tr > td > a
Survive/Yourself tbody > tr > td > a
Dead Void tr > td > span.forceBreak > a
Volatile Forms tbody > tr > td > a
Hellripper tr > td > span.forceBreak > a
Coronach tbody > tr > td > a
Between Live and... tbody > tr > td > a
A Grotesque... tbody > tr > td > a
I Don't Care tbody > tr > td > a
Cardiomyotomy tr > td > span.forceBreak > a
Beautifying... tbody > tr > td > a
Deadzone tr > td > span.forceBreak > a
Deliberate tbody > tr > td > a
Extinction A.D. tr > td > span.forceBreak > a
Truth or... tbody > tr > td > a
Hans & Valter tr > td > span.forceBreak > a
The Prophecy tbody > tr > td > a
Without Dreams tr > td > span.forceBreak > a
Mana Diagram tr > td > span.forceBreak > a
Where Victims Lie tr > td > span.forceBreak > a
Coven of the Swamp tr > td > span.forceBreak > a
The Veil tbody > tr > td > a
A Figment of... tbody > tr > td > a
Falling Leaves tbody > tr > td > a
Ural tr > td > span.forceBreak > a
Anthropic Genetic... tbody > tr > td > a
Rahvira tr > td > span.forceBreak > a
In the Darkness... tbody > tr > td > a
Seum tr > td > span.forceBreak > a
Parking Life tbody > tr > td > a
Hagane tr > td > span.forceBreak > a
We Are the Knight tbody > tr > td > a
Bloody Falls tr > td > span.forceBreak > a
Mother, Your Son... tbody > tr > td > a
Vomit Forth tr > td > span.forceBreak > a
In the Name of... tbody > tr > td > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ghost Bath Ghost Bath Apr 22nd Black Label Society Shot to Hell Apr 22nd Gh… div.tabs > div.block > div.ui-tabs-panel-content > table
Inhale Blue Moment April 22nd Concerto Moon Between Live and... April 22nd … div.tabs > div.block > div.ui-tabs-panel-content > table
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<html>` element has a valid value for its `[lang]` attribute
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Access to XMLHttpRequest at 'https://www.metal-archives.com/index/ajax-stats' from origin 'https://metal-archives.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to XMLHttpRequest at 'https://www.metal-archives.com/user/session' from origin 'https://metal-archives.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
75

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#news > div.motd > p.body > img div#news > div.motd > p.body > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback