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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:114.269 source:map[type:text value:[unattributed]]] map[reflowTime:10.027 source:map[column:630506 line:1 type:source-location url:https://pixlr.com/dist/web.d72bd5e51ddc8cb5d9a4.js 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

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
/css2?family=Reddit+Sans:ital,wght@0,200..900;1,200..900&...	995 B	277 ms
pixlr.com/dist/webstyle.16d097b8c671f06f8726.css	13.2 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
AI Image Generator Example One `div.right > div.box-out > div#ai-image-generator > img`	pixlr.com/images/index/ai-image-generator-one.webp	50.0 KiB	29.8 KiB
AI Image Generator Example Three `div.right > div.box-out > div#ai-image-generator > img`	pixlr.com/images/index/ai-image-generator-three.webp	45.2 KiB	25.8 KiB
AI Generative Expand Example After `div.right > div.box-out > div#ai-generative-expand > img`	pixlr.com/images/index/generative-expand-back.webp	42.6 KiB	19.6 KiB
AI Noise reducation `div.wrap > div.reels > a.box-shine > img.hero`	pixlr.com/img/tool/remove-noise-info.webp	26.0 KiB	18.7 KiB
AI Generative Transform `div.wrap > div.reels > a.box-shine > img.hero`	pixlr.com/img/tool/generative-transform-info.webp	25.0 KiB	17.7 KiB
AI super scale `div.wrap > div.reels > a.box-shine > img.hero`	pixlr.com/img/tool/super-scale-info.webp	24.5 KiB	17.2 KiB
AI Generative Expand Example Before `div.right > div.box-out > div#ai-generative-expand > img`	pixlr.com/images/index/generative-expand-front.webp	35.7 KiB	16.5 KiB
AI Face Swapper `div.wrap > div.reels > a.box-shine > img.hero`	pixlr.com/img/tool/face-swap-info.webp	23.3 KiB	16.0 KiB
AI Image Sharper `div.wrap > div.reels > a.box-shine > img.hero`	pixlr.com/img/tool/super-sharp-info.webp	22.1 KiB	14.8 KiB
AI Generative Fill Before `div.right > div.box-out > div#ai-generative-fill > img`	pixlr.com/images/index/ai-generative-fill-before.webp	35.8 KiB	11.4 KiB
AI Generative Fill After `div.right > div.box-out > div#ai-generative-fill > img`	pixlr.com/images/index/ai-generative-fill-after.webp	32.2 KiB	10.3 KiB
AI Image Generator Example Two `div.right > div.box-out > div#ai-image-generator > img`	pixlr.com/images/index/ai-image-generator-two.webp	26.3 KiB	9.3 KiB
AI Remove Background `div.wrap > div.reels > a.box-shine > img.hero`	pixlr.com/img/tool/remove-background-info.webp	12.9 KiB	7.9 KiB

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 reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not 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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 340.1 KiB

URL	Transfer Size	Est Savings
pixlr.com/dist/web.d72bd5e51ddc8cb5d9a4.js	258.9 KiB	203.1 KiB
accounts.google.com/gsi/client	95.5 KiB	70.4 KiB
www.googletagmanager.com/gtag/js?id=G-ZTY6N776WH	165.0 KiB	66.6 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.


HDR Photo filter `div.wrap > div.reels > a.box-shine > img.hero`
Bokeh Photo filter `div.wrap > div.reels > a.box-shine > img.hero`
Reflect Mirror Photo filter `div.wrap > div.reels > a.box-shine > img.hero`
Reflect Mirror Photo filter `div.wrap > div.reels > a.box-shine > img.hero`
Glitch Photo filter `div.wrap > div.reels > a.box-shine > img.hero`
Glitch Photo filter `div.wrap > div.reels > a.box-shine > img.hero`

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 40 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,332 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.7 s

●Avoid long main-thread tasks 1 long task found

●Network Requests

●Network Round Trip Times 20 ms

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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
BEST IN CLASS `body > section.design > div.wrap > span.row-label`
Open Photo Grid Maker `section.design > div.wrap > div.left > a.button`
Open Product Shot Creator `section.design > div.wrap > div.left > a.button`
Test Photo Filters `section.design > div.wrap > div.left > a.button`

These are opportunities to improve the legibility of your content.

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

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

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

●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

●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

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

○Buttons have an accessible name

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○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

○Elements with visible text labels have matching accessible names.

○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

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.

Source	Description
accounts.google.com/gsi/client line 85, col 88	`[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.`
pixlr.com/img/general/photo-collage.svg	`Failed to load resource: the server responded with a status of 502 ()`
pixlr.com/img/tool/remove-object-info.webp	`Failed to load resource: the server responded with a status of 502 ()`
pixlr.com/img/general/e-icon.svg	`Failed to load resource: the server responded with a status of 502 ()`
pixlr.com/img/general/nano-banana.svg	`Failed to load resource: the server responded with a status of 502 ()`
pixlr.com/	`Not signed in with the identity provider.`
pixlr.com/	`The Content-Security-Policy directive name 'Strict-Transport-Security:' contains one or more invalid characters. Only ASCII alphanumeric characters or dashes '-' are allowed in directive names.`
pixlr.com/	`Unrecognized Content-Security-Policy directive 'includeSubDomains'.`
pixlr.com/	`Unrecognized Content-Security-Policy directive 'preload'.`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
pixlr.com/dist/web.d72bd5e51ddc8cb5d9a4.js

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

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