Skip to content
https://remove.bg

Lighthouse Mobile

· 0 checks — Mobile 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.

31

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.

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:72.655 source:map[type:text value:[unattributed]]] map[reflowTime:0.908 source:map[column:13963 line:59 type:source-location url:https://static.remove.bg/remove-bg-web/77139bce0dcc0828bdade2e4110046e30e2c7d2b/vite/assets/application-a075360d.js urlProvider:network]] map[reflowTime:0.85 source:map[column:11044 line:263 type:source-location url:https://static.remove.bg/remove-bg-web/77139bce0dcc0828bdade2e4110046e30e2c7d2b/vite/assets/application-a075360d.js urlProvider:network]] map[reflowTime:22.496 source:map[column:55348 line:16 type:source-location url:https://static.remove.bg/remove-bg-web/77139bce0dcc0828bdade2e4110046e30e2c7d2b/vite/assets/index-a57bbcdb.js urlProvider:network]] map[reflowTime:26.232 source:map[column:54077 line:16 type:source-location url:https://static.remove.bg/remove-bg-web/77139bce0dcc0828bdade2e4110046e30e2c7d2b/vite/assets/index-a57bbcdb.js urlProvider:network]] map[reflowTime:0.444 source:map[column:54141 line:16 type:source-location url:https://static.remove.bg/remove-bg-web/77139bce0dcc0828bdade2e4110046e30e2c7d2b/vite/assets/index-a57bbcdb.js urlProvider:network]] map[reflowTime:0.341 source:map[column:54208 line:16 type:source-location url:https://static.remove.bg/remove-bg-web/77139bce0dcc0828bdade2e4110046e30e2c7d2b/vite/assets/index-a57bbcdb.js urlProvider:network]]]

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.mx-auto > div.flex > div.flex > video.w-full div.mx-auto > div.flex > div.flex > video.w-full
sb.kaleidousercontent.com/67418/2592x1728/c755e5d9d3/emilia-thumbnail.png1.9 MiB1.9 MiB
div.flex > figure.!m-0 > picture > img.w-full div.flex > figure.!m-0 > picture > img.w-full
/67418/2000x2000/0a17f63fa5/rbg-feature-pages-batch-1-min...1.4 MiB1.4 MiB
Example image div > figure.!m-0 > picture > img.w-full
sb.kaleidousercontent.com/67418/992x558/b024f7a4e1/stunning-quality-product.png210.1 KiB199.4 KiB
Original div.mx-auto > figure.!m-0 > picture > img.rounded-2xl
sb.kaleidousercontent.com/67418/604x802/9455f54d5d/person-1.png173.2 KiB158.5 KiB
New background div.mx-auto > figure.!m-0 > picture > img.rounded-2xl
sb.kaleidousercontent.com/67418/604x802/f047041244/person-3.png153.3 KiB138.6 KiB
Endless possibilities div.mx-auto > figure.!m-0 > picture > img.rounded-2xl
sb.kaleidousercontent.com/67418/604x802/9007e9962c/person-4.png148.9 KiB134.2 KiB
Example image div.absolute > figure.!m-0 > picture > img.w-full
/67418/992x558/235d7eafc9/stunning-quality-prodcut-transp...128.2 KiB117.5 KiB
Transparent background div.mx-auto > figure.!m-0 > picture > img.rounded-2xl
sb.kaleidousercontent.com/67418/604x802/cb1c7782ea/person-2.png122.4 KiB107.7 KiB
Example foreground image div.w-full > figure.!m-0 > picture > img.w-full
static.remove.bg/uploader-examples/person/3_thumbnail.jpg16.3 KiB15.9 KiB
Example image div.w-full > figure.!m-0 > picture > img.w-full
static.remove.bg/uploader-examples/car/2_thumbnail.jpg12.0 KiB9.8 KiB
Example image div.w-full > figure.!m-0 > picture > img.w-full
static.remove.bg/uploader-examples/animal/7_thumbnail.jpg12.0 KiB9.8 KiB
Example image div.w-full > figure.!m-0 > picture > img.w-full
static.remove.bg/uploader-examples/product/9_thumbnail.jpg9.6 KiB7.4 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-VIDEO
nodeLabel: div.mx-auto > div.flex > div.flex > video.w-full
path: 1,HTML,1,BODY,2,DIV,2,MAIN,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,VIDEO
selector: div.mx-auto > div.flex > div.flex > video.w-full
snippet: <video preload="auto" class="w-full h-auto rounded-4xl max-w-[320px] lg:max-w-[420px]" poster="https://sb.kaleidousercontent.com/67418/2592x1728/c755e5d9d3/emilia-thumbn…" autoplay="" playsinline="true" src="https://sb.kaleidousercontent.com/67418/x/3a4152a758/emilia-main-c.mp4">

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

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
fonts.googleapis.com/css?family=Poppins:700917 B836 ms

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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: 925 ms
URLTime Spent
remove.bg/925 ms
www.remove.bg/0.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 rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

CategoryTime Spent
Script Evaluation2.8 s
Other1.1 s
Style & Layout647 ms
Parse HTML & CSS165 ms
Rendering113 ms
Script Parsing & Compilation112 ms
Garbage Collection102 ms

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.flex > figure.!m-0 > picture > img.w-full div.flex > figure.!m-0 > picture > img.w-full
sb.kaleidousercontent.com/67418/2000x2000/41c2135a20/bulk-still.png
Original div.mx-auto > figure.!m-0 > picture > img.rounded-2xl
sb.kaleidousercontent.com/67418/604x802/9455f54d5d/person-1.png
Transparent background div.mx-auto > figure.!m-0 > picture > img.rounded-2xl
sb.kaleidousercontent.com/67418/604x802/cb1c7782ea/person-2.png
New background div.mx-auto > figure.!m-0 > picture > img.rounded-2xl
sb.kaleidousercontent.com/67418/604x802/f047041244/person-3.png
Endless possibilities div.mx-auto > figure.!m-0 > picture > img.rounded-2xl
sb.kaleidousercontent.com/67418/604x802/9007e9962c/person-4.png
Example image div > figure.!m-0 > picture > img.w-full
sb.kaleidousercontent.com/67418/992x558/b024f7a4e1/stunning-quality-product.png
Example image div.absolute > figure.!m-0 > picture > img.w-full
/67418/992x558/235d7eafc9/stunning-quality-prodcut-transp...
div.flex > figure.!m-0 > picture > img.w-full div.flex > figure.!m-0 > picture > img.w-full
/67418/2000x2000/0a17f63fa5/rbg-feature-pages-batch-1-min...
Emil Barsø Rheinlænder div > figure.!m-0 > picture > img.w-full
Marc Cohen div > figure.!m-0 > picture > img.w-full
Taylor Hatmaker div > figure.!m-0 > picture > img.w-full

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

●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 10 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 20 ms
●Server Backend Latencies 190 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 250 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
85

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
English div.flex > div.flex > div.!mr-6 > div.focus:outline-none

These are opportunities to improve the usage of ARIA in your application which 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
Cookie Policy div.banner > div.container > p.policy > a
Close div.banner > div.container > div.buttons > button.btn

These are opportunities to improve the legibility of your content.

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.flex > figure.!m-0 > picture > img.w-full div.flex > figure.!m-0 > picture > img.w-full
div.flex > figure.!m-0 > picture > img.w-full div.flex > figure.!m-0 > picture > img.w-full

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.relative > div.absolute > label.block > input.bg-transparent div.relative > div.absolute > label.block > input.bg-transparent

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.

○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
●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 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
●No element has a `[tabindex]` value greater than 0
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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
○`<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
○Select elements have associated label elements.
○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
○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.
○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
The disableRemotePlayback attribute should be used in order to disable the default Cast integration instead of using -internal-media-controls-overlay-cast-button selector.
www.remove.bg/ line 67, col -1
●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 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
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

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.flex > figure.!m-0 > picture > img.w-full div.flex > figure.!m-0 > picture > img.w-full
div.flex > figure.!m-0 > picture > img.w-full div.flex > figure.!m-0 > picture > img.w-full

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
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback