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.

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
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
ssl.google-analytics.com/ga.js	7200.0 s	17.4 KiB

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:33.611 source:map[type:text value:[unattributed]]]]

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

nodeLabel: Trending: Background Wallpaper Business Purchase Music Celebration View Get 10 …

path: 1,HTML,1,BODY,3,DIV,3,DIV,2,DIV,2,DIV,0,DIV

selector: div._bIyG9 > div._dsXcE > div._peHAd > div._Tb2bY

snippet: <div class="_Tb2bY _Mr8rw" style="background-image: url("https://static.depositphotos.com/storage/image/d3d516…");" is-overlay-enabled="true" data-qa="LandingHeaderBox">

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
Macmillan Publishers `div._LGuFb > div._EBdTx > picture._jBH4f > img`	/storage/image/b60df6ecbe33a6ccf5b28fdb0206e426fa9a2a33.jpg	14.4 KiB	11.7 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: 750 ms 437.0 KiB

URL	Transfer Size	Est Savings
accounts.google.com/gsi/client	95.5 KiB	72.5 KiB
www.googletagmanager.com/gtag/js?id=G-ZJX50C9LQD&cx=c&gtm=4e64h1h1	163.5 KiB	67.8 KiB
/gtm.js?id=GTM-W6LTGTD&gtm_auth=lldYB05Mw8y1z7dEPqGC7w&gt...	184.0 KiB	62.4 KiB
webst.depositphotos.com/_js/vue/chunk.entry-client-wmf.js?6559b92ff6a2d95b1cf5	98.4 KiB	53.5 KiB
webst.depositphotos.com/_js/vue/chunk.vendors.js?6559b92ff6a2d95b1cf5	93.7 KiB	51.4 KiB
webst.depositphotos.com/_js/vue/chunk.ioc.js?6559b92ff6a2d95b1cf5	77.5 KiB	37.9 KiB
webst.depositphotos.com/_js/vue/chunk.swiper.js?6559b92ff6a2d95b1cf5	39.2 KiB	28.2 KiB
webst.depositphotos.com/_js/vue/0c8e34b7746e6668632e.js?6559b92ff6a2d95b1cf5	34.9 KiB	22.3 KiB
webst.depositphotos.com/_js/vue/chunk.sentry.js?6559b92ff6a2d95b1cf5	39.9 KiB	20.6 KiB
webst.depositphotos.com/_js/vue/chunk.moment.js?6559b92ff6a2d95b1cf5	24.8 KiB	20.5 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
webst.depositphotos.com/_js/vue/chunk.sentry.js?6559b92ff6a2d95b1cf5	780 ms	716 ms	32 ms
depositphotos.com/	584 ms	36 ms	89 ms
/gtm.js?id=GTM-W6LTGTD&gtm_auth=lldYB05Mw8y1z7dEPqGC7w&gt...	564 ms	483 ms	64 ms
Unattributable	559 ms	8.7 ms	0.0 ms
depositphotos.com/_js/legacy.js?c66c68dc74b7574bf9b8ae868e2a32ff	365 ms	360 ms	3.1 ms
www.googletagmanager.com/gtag/js?id=G-ZJX50C9LQD&cx=c&gtm=4e64h1h1	321 ms	256 ms	62 ms
webst.depositphotos.com/_js/vue/chunk.route.Index.js?6559b92ff6a2d95b1cf5	230 ms	223 ms	7.2 ms
webst.depositphotos.com/_js/vue/chunk.ioc.js?6559b92ff6a2d95b1cf5	228 ms	186 ms	40 ms
webst.depositphotos.com/_js/vue/chunk.Banner.js?6559b92ff6a2d95b1cf5	221 ms	202 ms	9.5 ms
webst.depositphotos.com/_js/vue/chunk.app.js?6559b92ff6a2d95b1cf5	187 ms	158 ms	23 ms
www.google-analytics.com/analytics.js	156 ms	131 ms	5.3 ms
webst.depositphotos.com/_js/vue/54bcbdb18716924f47cd.js?6559b92ff6a2d95b1cf5	154 ms	153 ms	0.6 ms
accounts.google.com/gsi/client	104 ms	68 ms	35 ms
webst.depositphotos.com/_js/vue/chunk.router.js?6559b92ff6a2d95b1cf5	70 ms	67 ms	2.0 ms
webst.depositphotos.com/_js/vue/chunk.entry-client-wmf.js?6559b92ff6a2d95b1cf5	70 ms	2.1 ms	67 ms
ssl.google-analytics.com/ga.js	57 ms	50 ms	5.1 ms
webst.depositphotos.com/_js/vue/444ad7ca60f7c7f11f19.js?6559b92ff6a2d95b1cf5	54 ms	30 ms	11 ms
webst.depositphotos.com/_js/vue/main.js?6559b92ff6a2d95b1cf5	51 ms	43 ms	7.8 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
Script Evaluation	3.3 s
Script Parsing & Compilation	710 ms
Other	603 ms
Style & Layout	281 ms
Parse HTML & CSS	168 ms
Garbage Collection	124 ms
Rendering	38 ms

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

Estimated savings: 0.0 ms 31.5 KiB

URL	Transfer Size	Est Savings
:root, [data-theme='day']{--background:#ffffff;--background-hover:#f0f1f3;--surface-0:#ffffff;--sur…	22.6 KiB	18.4 KiB
/_css/vue/src_core_application_repositories_RecentSearche...	14.0 KiB	13.1 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.

	URL
Xerox `div._LGuFb > div._EBdTx > picture._jBH4f > img`	/storage/image/9040073fdd09f4f4cdd6b1c2b3a3a603f2e1dbd4.jpg
Simon & Schuster `div._LGuFb > div._EBdTx > picture._jBH4f > img`	/storage/image/74affcb89ef5fe4c97e67ab76c691bbebc7767cf.jpg
Hachette Book Group `div._LGuFb > div._EBdTx > picture._jBH4f > img`	/storage/image/ac05c1c3561130979dc4a8ea2e816239b0c9a053.jpg
Cleveland Research Company `div._LGuFb > div._EBdTx > picture._jBH4f > img`	/storage/image/52f6fb55f66ecaf0a307746639f6182713dae06c.jpg
Macmillan Publishers `div._LGuFb > div._EBdTx > picture._jBH4f > img`	/storage/image/b60df6ecbe33a6ccf5b28fdb0206e426fa9a2a33.jpg
Norton `div._LGuFb > div._EBdTx > picture._jBH4f > img`	/storage/image/cff333e6db743e47cddab0a07470c40209473377.jpg
Wiley `div._LGuFb > div._EBdTx > picture._jBH4f > img`	/storage/image/91df17c4adae3388dd9ff5611c4710321b245b05.jpg

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

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 26 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 140 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 410 ms

○INP breakdown

○Avoid non-composited animations

○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

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search for Images `div._yAlDx > div._WpAT4 > div._RRkQ9 > input._kIybM`

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search for Images `div._yAlDx > div._WpAT4 > div._RRkQ9 > input._kIybM`

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
Yes, Get It Now! `div.x997 > div.text-button-1 > div.button-old-1 > div.text-1`
Accept All `div#app > div._npz_F > button.__eNkG > span._HbaYd`

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

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
View `div._Tb2bY > div._cxzXG > div._sGzeT > a._EDY2A`

○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]` values are valid

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●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

●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

○`[accesskey]` values are unique

○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

○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

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

○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

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
depositphotos.com/	`Not signed in with the identity provider.`

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
webst.depositphotos.com/_js/vue/chunk.entry-client-wmf.js?6559b92ff6a2d95b1cf5

●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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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`