Lighthouse Mobile

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

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.flex > div.group > a.w-10 > img.w-full `div.flex > div.group > a.w-10 > img.w-full`	/storage/v1/object/public/advertiser-ads/ads/179136505207...	461.5 KiB	461.0 KiB
Instant cutout export demonstration showing isolated subject with transparent P… `div.bg-white > div.w-full > picture.w-full > img.w-full`	www.pixir.in/ISc.webp	275.2 KiB	241.1 KiB
Before background removal: original portrait photograph with studio background … `div.relative > div.absolute > picture.w-full > img.w-full`	www.pixir.in/Model1.webp	219.0 KiB	124.1 KiB
Pixir `div.w-full > div.relative > div.relative > img.w-12`	www.pixir.in/logo_pixir.png	98.0 KiB	96.9 KiB
After background removal: professional portrait with transparent background sho… `div.relative > div.absolute > picture.w-full > img.w-full`	www.pixir.in/rv_Model1.webp	180.4 KiB	85.4 KiB
Seamless integration example showing transparent cutout subject placed into new… `div.group > div.w-full > picture.w-full > img.w-full`	www.pixir.in/Seamless.webp	114.5 KiB	82.3 KiB
div.flex > div.group > a.w-10 > img.w-full `div.flex > div.group > a.w-10 > img.w-full`	/storage/v1/object/public/advertiser-ads/ads/179024588195...	20.3 KiB	19.9 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

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
/storage/v1/object/public/advertiser-ads/ads/179136505207...	3600.0 s	462.2 KiB
/storage/v1/object/public/advertiser-ads/ads/179024588195...	3600.0 s	20.9 KiB
www.pixir.in/cdn-cgi/challenge-platform/h/g/scripts/jsd/4df4a60fa397/main.js?	14400.0 s	11.9 KiB
/beacon.min.js/v4bc70e2c01a94c73b74392e423484066179121581...	86400.0 s	10.2 KiB
www.pixir.in/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	172746.0 s	927 B

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
www.pixir.in/assets/index-DbQA1zqJ.css	18.4 KiB

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

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

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.

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: 1.1 s 196.3 KiB

URL	Transfer Size	Est Savings
www.pixir.in/assets/ort.bundle.min-B5M2MB43.js	106.2 KiB	104.0 KiB
www.pixir.in/assets/index-x-ziy8RP.js	163.6 KiB	67.3 KiB
www.pixir.in/assets/OnlineStudio-fTOAmZiD.js	32.6 KiB	24.9 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.pixir.in/	4.7 s	30 ms	1.5 ms
www.pixir.in/assets/index-x-ziy8RP.js	1.8 s	909 ms	1.8 ms
Unattributable	785 ms	119 ms	0.0 ms
www.pixir.in/cdn-cgi/challenge-platform/scripts/jsd/main.js	305 ms	253 ms	2.1 ms

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
Other	2.8 s
Style & Layout	2.0 s
Script Evaluation	1.3 s
Rendering	1.2 s
Garbage Collection	87 ms
Parse HTML & CSS	59 ms
Script Parsing & Compilation	7.6 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
/storage/v1/object/public/advertiser-ads/ads/179136505207...	462.2 KiB
www.pixir.in/Model5.jpg	306.5 KiB
www.pixir.in/Model1.jpg	290.4 KiB
www.pixir.in/Model3.jpg	284.1 KiB
www.pixir.in/ISc.webp	276.8 KiB
www.pixir.in/Model4.jpg	267.7 KiB
www.pixir.in/Model2.jpg	257.5 KiB
www.pixir.in/Model1.webp	219.7 KiB
www.pixir.in/rv_Model1.webp	181.1 KiB
www.pixir.in/assets/index-x-ziy8RP.js	165.1 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

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoid long main-thread tasks 9 long tasks found

●Avoid non-composited animations 3 animated elements found

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

●Page didn't prevent back/forward cache restoration

●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

○INP breakdown

○User Timing marks and measures

○Avoid large layout shifts

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
Pixir.in Free Background Removal Sponsored No SignUp \| No Quality Loss \| No Li… `section.w-full > div.relative > div.animate-pixir-marquee > div.flex`

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
FREE AI BACKGROUND REMOVER `div > div.flex > span.inline-flex > span`
Remove Background Free `div.lg:col-span-6 > div.flex > button.btn-primary > span`
Select Image `div.w-full > div.text-center > button.btn-primary > span`
PIXIR STUDIO `div.flex > div.w-full > div > p.text-[10px]`
OR TRY A SAMPLE `div.px-4 > div.flex > span.text-[10px] > span`
Advertise with us `div.container-custom > div.flex > a.text-[10px] > span`
CUTOUT RESULT `div.container-custom > div.relative > div.absolute > span.absolute`
CREATIVE CANVAS VARIATIONS `section.py-16 > div.container-custom > div.max-w-3xl > span.text-xs`
Start Removing Backgrounds `div.container-custom > div#pricing-banner > button.btn-primary > span`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Unique Visitors `div.grid > div.bg-[#F8FAF8] > div > h4.text-[11px]`

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jump to editorial spread slide 1 `div.group > div.relative > div.absolute > button.transition-all`
Jump to editorial spread slide 2 `div.group > div.relative > div.absolute > button.transition-all`
Jump to editorial spread slide 3 `div.group > div.relative > div.absolute > button.transition-all`
Jump to editorial spread slide 4 `div.group > div.relative > div.absolute > button.transition-all`
Jump to editorial spread slide 5 `div.group > div.relative > div.absolute > button.transition-all`

These items highlight common accessibility best practices.

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
Remove Background Free `div.grid > div.lg:col-span-6 > div.flex > button.btn-primary`
See how it works `div.grid > div.lg:col-span-6 > div.flex > button.btn-secondary`

○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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

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

○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
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.pixir.in/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.pixir.in/cdn-cgi/challenge-platform/scripts/jsd/main.js

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
www.pixir.in/assets/index-x-ziy8RP.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

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

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