Skip to content
https://magiceraser.live

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

99

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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
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
Before-and-after photo enhancement preview with improved sharpness and lighting div.mx-auto > div.relative > div.relative > img.h-full
magiceraser.live/_next/image?url=%2Fhome_enhance_before.webp&w=640&q=75179.6 KiB142.4 KiB
Edited product photo with a clean replacement background section.px-6 > div.mx-auto > div.relative > img.h-full
magiceraser.live/_next/image?url=%2Fhome_edit_background.webp&w=640&q=75120.5 KiB91.4 KiB
Before-and-after workspace photo showing a distraction removed from the scene div.mx-auto > div.relative > div.relative > img.h-full
magiceraser.live/_next/image?url=%2Fhome_remove_before.webp&w=640&q=7599.9 KiB75.9 KiB
Before-and-after workspace photo showing a distraction removed from the scene -… div.relative > div.relative > div.absolute > img.h-full
magiceraser.live/_next/image?url=%2Fhome_remove_after.webp&w=640&q=7568.4 KiB52.0 KiB
Before-and-after portrait preview with sharper detail and improved lighting div.grid > a.flex > div.relative > img.h-full
magiceraser.live/_next/image?url=%2Fhome_enhance_after.webp&w=384&q=7549.0 KiB44.1 KiB
Before-and-after photo enhancement preview with improved sharpness and lighting… div.relative > div.relative > div.absolute > img.h-full
magiceraser.live/_next/image?url=%2Fhome_enhance_after.webp&w=640&q=7549.0 KiB27.2 KiB
Perfume bottle on luxury studio background — AI Create example div.mx-auto > div.grid > div.relative > img.h-full
/_next/image?url=%2Fhome-ai-tools%2Fperfume-center.webp&w...24.6 KiB22.3 KiB
Product photo preview with the background removed for a clean cutout div.grid > a.flex > div.relative > img.h-full
magiceraser.live/_next/image?url=%2Ftools_background.webp&w=384&q=7524.0 KiB17.3 KiB
Perfume product styled with AI-generated background div.mx-auto > div.grid > div.relative > img.h-full
/_next/image?url=%2Fhome-ai-tools%2Fperfume-right.webp&w=...13.7 KiB12.7 KiB
Magic Eraser Logo div.max-w-6xl > div.flex > a.flex > img.rounded-lg
magiceraser.live/_next/image?url=%2Fapp_logo.png&w=48&q=7512.1 KiB11.1 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 Size
magiceraser.live/_next/static/css/a9cfd3d814f9482c.css13.5 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 256 ms
URLTime Spent
magiceraser.live/256 ms
magiceraser.live/en0.0 ms

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: 0.0 ms 300.2 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?l=dataLayer&id=G-JS4LWJQ80F176.9 KiB117.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-PJKTTN5C147.0 KiB65.2 KiB
www.googletagmanager.com/gtag/js?id=G-JS4LWJQ80F&cx=c&gtm=4e67d0176.9 KiB64.4 KiB
www.googletagmanager.com/gtag/js?id=AW-17733122693&cx=c&gtm=4e67d0148.4 KiB53.4 KiB

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

●Max Potential First Input Delay 130 ms
●Use efficient cache lifetimes
●Layout shift culprits
●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 1,670 KiB
●JavaScript execution time 0.5 s
●Minimizes main-thread work 1.5 s
●Avoid long main-thread tasks 3 long tasks found
●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 130 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 90 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
96

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
REMOVE div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
REMOVE div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
BLOG div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
BLOG div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
TEMPLATES div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
TEMPLATES div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
ACADEMY div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
INDUSTRIES div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
HOW-TO GUIDES div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]
GLOSSARY div.mx-auto > div.mt-10 > a.text-[14px] > span.text-[11px]

These are opportunities to improve the legibility of your content.

○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
●`[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
●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
●Identical links have the same purpose.
○`[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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
○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.
○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.
81

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
AttributionReporting
www.googletagmanager.com/gtag/js?id=AW-17733122693&cx=c&gtm=4e67d0 line 537, col 191
●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
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
92

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.

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

Send Feedback