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.

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:60.99 source:map[column:17883 line:2 type:source-location url:https://charliekirkface.net/_next/static/chunks/786-84eda7cb3ba2929c.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:169.244 source:map[type:text value:[unattributed]]] map[reflowTime:0.438 source:map[column:11536 line:0 type:source-location url:https://charliekirkface.net/cdn-cgi/challenge-platform/scripts/jsd/main.js urlProvider:network]] map[reflowTime:5.325 source:map[column:27732 line:0 type:source-location url:https://charliekirkface.net/_next/static/chunks/83723-12052d4327ec9afa.js urlProvider:network]] map[reflowTime:1.665 source:map[column:20771 line:0 type:source-location url:https://charliekirkface.net/_next/static/chunks/42506-30c48f33587f0e80.js urlProvider:network]] map[reflowTime:46.68 source:map[column:29144 line:0 type:source-location url:https://charliekirkface.net/_next/static/chunks/90926-d6503bb56250797b.js urlProvider:network]] map[reflowTime:7.32 source:map[column:18848 line:0 type:source-location url:https://charliekirkface.net/_next/static/chunks/48103-e8ad57a4d6ecd71d.js urlProvider:network]] map[reflowTime:1.439 source:map[column:69434 line:0 type:source-location url:https://charliekirkface.net/_next/static/chunks/7311-08bfbef532b0cd28.js urlProvider:network]] map[reflowTime:37.527 source:map[column:96 line:130 type:source-location url:https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202610140101/show_ads_impl_fy2021.js?bust=122881636 urlProvider:network]]]

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

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
charliekirkface.net/_next/image?url=%2Flogo.png&w=128&q=75	0.0 ms	1.2 MiB
charliekirkface.net/_next/image?url=%2Fimgs%2Fkirkify%2Fdisplay-3.jpg&w=640&q=75	0.0 ms	502.3 KiB
charliekirkface.net/_next/image?url=%2Fimgs%2Fkirkify%2Fdisplay-1.jpg&w=640&q=75	0.0 ms	304.7 KiB
charliekirkface.net/_next/image?url=%2Fimgs%2Fkirkify%2Fdisplay-2.jpg&w=640&q=75	0.0 ms	36.1 KiB
pagead2.googlesyndication.com/pagead/js/rum.js?fcd=true	3600.0 s	29.3 KiB
/pagead/managed/js/adsense/m202610140101/show_ads_impl_fy...	1209600.0 s	165.1 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/d2d3316b729e/...	14400.0 s	11.5 KiB
pl.screwdom.org/js/pa-GuKjAdQQt6V1nMlTZyDOr.js	14400.0 s	6.6 KiB

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
div.relative > div.flex > a.group/brand > img.h-8 `div.relative > div.flex > a.group/brand > img.h-8`	charliekirkface.net/_next/image?url=%2Flogo.png&w=128&q=75	1.2 MiB	1.2 MiB
Tiny-face group-shot example `div.container > div.border-foreground/8 > div.relative > img.object-cover`	charliekirkface.net/_next/image?url=%2Fimgs%2Fkirkify%2Fdisplay-3.jpg&w=640&q=75	501.6 KiB	477.2 KiB
Tiny-face example with balanced lighting `div.container > div.border-foreground/8 > div.relative > img.object-cover`	charliekirkface.net/_next/image?url=%2Fimgs%2Fkirkify%2Fdisplay-1.jpg&w=640&q=75	304.3 KiB	265.2 KiB
Built-in Face Reference `div.border-foreground/8 > div.flex > div.border-foreground/10 > img.size-full`	charliekirkface.net/imgs/kirkify/face-reference.jpg	60.1 KiB	59.4 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.

URL	Transfer Size
charliekirkface.net/_next/static/css/23d139a9eaf3d2aa.css	27.3 KiB
charliekirkface.net/_next/static/css/f7188f1c2b323788.css	26.3 KiB
charliekirkface.net/_next/static/css/8d958d24824f9ea4.css	984 B
charliekirkface.net/_next/static/css/d8f3ac3fd0f18636.css	4.1 KiB

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

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.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 170 ms 436.8 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/adsense/m202610140101/show_ads_impl_fy...	165.1 KiB	114.1 KiB
www.googletagmanager.com/gtag/js?id=G-P71HVSMXRG	175.3 KiB	71.9 KiB
charliekirkface.net/_next/static/chunks/1197b774-dfa4b028af886f83.js	98.2 KiB	69.4 KiB
charliekirkface.net/_next/static/chunks/48103-e8ad57a4d6ecd71d.js	78.7 KiB	49.4 KiB
/i/ca-pub-4168717719853776?href=https%3A%2F%2Fcharliekirk...	69.4 KiB	36.2 KiB
/pagead/js/adsbygoogle.js?client=ca-pub-4168717719853776	55.9 KiB	29.6 KiB
charliekirkface.net/_next/static/chunks/68249-8f1fc7a1c648d723.js	33.1 KiB	23.4 KiB
charliekirkface.net/_next/static/chunks/af7a3046-bb9957f3003d6372.js	61.1 KiB	21.8 KiB
charliekirkface.net/_next/static/chunks/16833-90f1c7d534263030.js	35.4 KiB	21.0 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.1 s
Style & Layout	409 ms
Other	310 ms
Script Parsing & Compilation	180 ms
Parse HTML & CSS	35 ms
Rendering	32 ms
Garbage Collection	30 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
charliekirkface.net/logo.png	1.2 MiB
charliekirkface.net/_next/image?url=%2Flogo.png&w=128&q=75	1.2 MiB
charliekirkface.net/_next/image?url=%2Fimgs%2Fkirkify%2Fdisplay-3.jpg&w=640&q=75	502.3 KiB
charliekirkface.net/_next/image?url=%2Fimgs%2Fkirkify%2Fdisplay-1.jpg&w=640&q=75	304.7 KiB
www.googletagmanager.com/gtag/js?id=G-P71HVSMXRG	175.6 KiB
/pagead/managed/js/adsense/m202610140101/show_ads_impl_fy...	165.1 KiB
charliekirkface.net/favicon.ico	129.8 KiB
charliekirkface.net/_next/static/chunks/1197b774-dfa4b028af886f83.js	98.2 KiB
charliekirkface.net/_next/static/chunks/48103-e8ad57a4d6ecd71d.js	82.2 KiB
/i/ca-pub-4168717719853776?href=https%3A%2F%2Fcharliekirk...	70.7 KiB

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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 9 long tasks found

●Avoid non-composited animations 14 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 100 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 230 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.relative > div.mb-6 > div.flex > button#radix-_r_2_ `div.relative > div.mb-6 > div.flex > button#radix-_r_2_`

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.

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
01 `div.border-foreground/8 > div.mb-4 > div.flex > span.bg-primary`
02 `div.space-y-4 > div.border-foreground/8 > div.flex > span.bg-primary`
03 `div.space-y-4 > div.border-foreground/8 > div.mb-4 > span.bg-primary`
Sign In to Swap Faces `div.grid > div.space-y-4 > div.border-foreground/8 > button.inline-flex`
English `footer#footer > div.container > div.flex > button#radix-_r_7_`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Photo Face Swap Video Face Swap How It Works Examples Guides FAQ Pricing `div.flex > nav.group/navigation-menu > div > ul.group`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

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.__variable_231f96 `html.__variable_231f96`

These items highlight common accessibility best practices.

○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

●Image elements have `[alt]` attributes

●`[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

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

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

●Links have a discernible name

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

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

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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 / Warning	Source
SharedStorage	charliekirkface.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	charliekirkface.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	charliekirkface.net/cdn-cgi/challenge-platform/scripts/jsd/main.js

●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 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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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