Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

Performance issues directly impact user engagement and conversion rates.

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.

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.

	URL	Resource Size	Est Savings
Minecraft game board from qnoss’s BALATRO data-pack gallery `article.card > a.card-image > div.media > img`	/data/2werGvOk/images/f054b4cc15a4f4a7a50aea20e10fec96f91...	96.6 KiB	85.9 KiB
Publisher screenshot of Super Mario Ring on Melty `article.card > a.card-image > div.media > img`	melty.gg/design/melty-landing/mashup-frames/mario-elden-ring.webp	85.2 KiB	77.3 KiB
Melty’s publisher screenshot for Skate Warfare `article.card > a.card-image > div.media > img`	melty.gg/design/melty-landing/mashup-frames/skate-warfare.webp	78.3 KiB	71.1 KiB
DOOM shareware screenshot from the NucleDoom creator gallery `article.card > a.card-image > div.media > img`	/data/GpxZbmCB/images/f0936a6d96da1e99766994657d91ffbbac4...	69.8 KiB	59.5 KiB
2010 Rust Rewrite Mashup creator project screenshot `article.card > a.card-image > div.media > img`	merging.games/covers/mw2-skate-minecraft-reviewed-600.webp	47.8 KiB	33.9 KiB
Cover pairing: Half-Life on the left; Minecraft on the right. Original games, n… `article.card > a.card-image > div.media > img`	merging.games/covers/minecraft-x-halflife-reviewed-600.webp	46.4 KiB	32.5 KiB
Cover pairing: ULTRAKILL on the left; Minecraft on the right. Original games, n… `article.card > a.card-image > div.media > img`	merging.games/covers/ultracraft-reviewed-600.webp	44.3 KiB	30.4 KiB
SkyCraft creator project screenshot `a.feature > div > div.media > img`	merging.games/covers/skycraft-reviewed-600.webp	62.8 KiB	30.0 KiB
Cover pairing: Minecraft on the left; Elden Ring / Monster Hunter: World on the… `article.card > a.card-image > div.media > img`	merging.games/covers/minecraft-crossover-bridge-reviewed-600.webp	42.7 KiB	28.8 KiB
Cover pairing: Sekiro on the left; Minecraft on the right. Original games, not … `article.card > a.card-image > div.media > img`	merging.games/covers/sekirocraft-reviewed-600.webp	37.3 KiB	23.4 KiB
Cover pairing: Valheim on the left; Minecraft on the right. Original games, not… `article.card > a.card-image > div.media > img`	merging.games/covers/valcraft-reviewed-600.webp	36.8 KiB	22.9 KiB
Cover pairing: Outer Wilds on the left; Minecraft on the right. Original games,… `article.card > a.card-image > div.media > img`	merging.games/covers/owcraft-reviewed-600.webp	36.7 KiB	22.8 KiB
Cover pairing: DOOM on the left; Skyrim on the right. Original games, not mashu… `article.card > a.card-image > div.media > img`	merging.games/covers/skydoom-reviewed-600.webp	32.2 KiB	18.7 KiB
FalloutCraft creator project screenshot `article.card > a.card-image > div.media > img`	merging.games/covers/falloutcraft-reviewed-600.webp	28.5 KiB	16.5 KiB
Cover pairing: Skyrim on the left; Elden Ring on the right. Original games, not… `article.card > a.card-image > div.media > img`	merging.games/covers/skyring-reviewed-600.webp	27.8 KiB	16.1 KiB
HalfCraft creator project screenshot `article.card > a.card-image > div.media > img`	merging.games/covers/halfcraft-reviewed-600.webp	21.8 KiB	12.6 KiB
Mari0 gameplay screenshot published by Stabyourself.net `article.card > a.card-image > div.media > img`	stabyourself.net/images/screenshots/mari0-1.png	11.6 KiB	8.8 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.

URL	Transfer Size	Duration
merging.games/styles.css	5.3 KiB	93 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
stabyourself.net/images/screenshots/mari0-1.png	0.0 ms	11.8 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.7 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 899 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.2 s

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 30 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 60 ms

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
merging.games `body > header > div.wrap > a.brand`

○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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

●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

●Background and foreground colors have a sufficient contrast ratio

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○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

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<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

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<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.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●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 browser errors logged to the console

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`