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
js.stripe.com/v3/	120.0 s	225.5 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.4 KiB
www.scribd.com/_fs-ch-1T1wmsGaOgGaSxcX/assets/script.js	86400.0 s	204.7 KiB
/signals/config/287045611447707?v=2.9.298&r=stable&domain...	1200.0 s	46.2 KiB
utt.impactcdn.com/A3071581-5350-42cd-80be-79cdd173e0991.js	900.0 s	20.0 KiB
m.stripe.network/out-4.5.45.js	300.0 s	16.5 KiB
d2hrivdxn8ekm8.cloudfront.net/tracker-latest.min.js	0.0 ms	15.0 KiB
/tag-manager/d89a8e6a-7818-406f-8239-63104b420785-additio...	0.0 ms	9.7 KiB
/tag-manager/d89a8e6a-7818-406f-8239-63104b420785-latest.js	0.0 ms	7.2 KiB
survey.survicate.com/workspaces/7de87bc73aff1974945059e230fb953d/web_surveys.js	10.0 s	5.9 KiB
acdn.adnxs.com/dmp/up/pixie.js	86402.0 s	9.2 KiB
/npm/statsig-sidecar/dist/index.min.js?apikey=client-Qp5s...	604800.0 s	33.0 KiB
/tr/?id=287045611447707&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	19 B

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 > main._1BBjPx > div.GridContainer-module_wrapper_7Rx6L- > img._1E2frY `div > main._1BBjPx > div.GridContainer-module_wrapper_7Rx6L- > img._1E2frY`	/webpack/assets/images/landing_pages/logged_out_homepage/...	169.7 KiB	132.5 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

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.

URL	Transfer Size	Duration
s-f.scribdassets.com/webpack/monolith/8260.2faccba10c75077cfa0b.css	4.8 KiB	752 ms
www.scribd.com/_fs-ch-1T1wmsGaOgGaSxcX/assets/script.js	204.7 KiB	2.9 s

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.

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.

URL	Est Savings
/webpack/assets/fonts/scribd_sans/medium/Scribd-JaSN-Medi...	5.0 ms
/webpack/assets/fonts/source_sans_pro/regular/source_sans...	5.0 ms
/webpack/assets/fonts/scribd_sans/bold/Scribd-JaSN-Bold.c...	5.0 ms

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

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: 752 ms

URL	Time Spent
scribd.com/	752 ms
www.scribd.com/	0.0 ms

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: 5.8 s 1.1 MiB

URL	Transfer Size	Est Savings
s-f.scribdassets.com/webpack/landing-pages/297.4a05c6.js	765.4 KiB	422.4 KiB
js.stripe.com/v3/	225.2 KiB	164.2 KiB
surveys-static-prd.survicate-cdn.com/widget_core-28.23.8.js	160.1 KiB	77.1 KiB
www.googletagmanager.com/gtag/js?id=G-Z4ZC50DED6&cx=c&gtm=4e64f0	177.4 KiB	69.5 KiB
www.googletagmanager.com/gtag/js?id=G-8KZ8BV0P5W&cx=c&gtm=4e64f0	176.9 KiB	66.7 KiB
www.googletagmanager.com/gtag/js?id=AW-991817613&cx=c&gtm=4e64f0	144.4 KiB	64.2 KiB
www.googletagmanager.com/gtag/js?id=AW-11301899641&cx=c&gtm=4e64f0	144.4 KiB	63.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-KXQQWDG	164.5 KiB	61.9 KiB
browser.sentry-cdn.com/10.25.0/bundle.min.js	77.6 KiB	34.7 KiB
connect.facebook.net/en_US/fbevents.js	96.3 KiB	31.9 KiB
www.scribd.com/_fs-ch-1T1wmsGaOgGaSxcX/assets/script.js	204.4 KiB	24.6 KiB
/AzZdHGSGtpxCq1Cpt/4e10b135-d113-4574-a477-270ace40bba7/o...	89.8 KiB	20.1 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
/AzZdHGSGtpxCq1Cpt/4e10b135-d113-4574-a477-270ace40bba7/o...	913 ms	735 ms	31 ms
Unattributable	839 ms	65 ms	0.0 ms
s-f.scribdassets.com/webpack/landing-pages/297.4a05c6.js	679 ms	648 ms	6.3 ms
www.scribd.com/	604 ms	37 ms	14 ms
www.googletagmanager.com/gtm.js?id=GTM-KXQQWDG	537 ms	484 ms	45 ms
surveys-static-prd.survicate-cdn.com/widget_core-28.23.8.js	385 ms	315 ms	60 ms
www.googletagmanager.com/gtag/js?id=G-Z4ZC50DED6&cx=c&gtm=4e64f0	384 ms	339 ms	42 ms
/npm/statsig-sidecar/dist/index.min.js?apikey=client-Qp5s...	364 ms	342 ms	8.2 ms
www.scribd.com/_fs-ch-1T1wmsGaOgGaSxcX/assets/script.js	238 ms	188 ms	15 ms
js.stripe.com/v3/	232 ms	141 ms	91 ms
www.googletagmanager.com/gtag/js?id=G-8KZ8BV0P5W&cx=c&gtm=4e64f0	217 ms	171 ms	44 ms
www.googletagmanager.com/gtag/js?id=AW-11301899641&cx=c&gtm=4e64f0	208 ms	175 ms	32 ms
connect.facebook.net/en_US/fbevents.js	200 ms	132 ms	26 ms
www.googletagmanager.com/gtag/js?id=AW-991817613&cx=c&gtm=4e64f0	180 ms	147 ms	31 ms
d2hrivdxn8ekm8.cloudfront.net/tracker-latest.min.js	175 ms	172 ms	1.2 ms
/signals/config/287045611447707?v=2.9.298&r=stable&domain...	162 ms	145 ms	16 ms
browser.sentry-cdn.com/10.25.0/bundle.min.js	105 ms	70 ms	12 ms
utt.impactcdn.com/A3071581-5350-42cd-80be-79cdd173e0991.js	78 ms	73 ms	4.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
Script Evaluation	4.4 s
Other	933 ms
Script Parsing & Compilation	484 ms
Style & Layout	380 ms
Parse HTML & CSS	163 ms
Garbage Collection	108 ms
Rendering	83 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 8.3 KiB

URL	Transfer Size	Est Savings
/tag-manager/d89a8e6a-7818-406f-8239-63104b420785-additio...	9.3 KiB	5.3 KiB
/tag-manager/d89a8e6a-7818-406f-8239-63104b420785-latest.js	6.8 KiB	3.1 KiB

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 215.6 KiB

URL	Transfer Size	Est Savings
@charset "UTF-8";.StatusBadge-module_wrapper_YSlO4S{align-items:center; … } …	197.5 KiB	187.6 KiB
.sr-only{border:0;clip:rect(0,0,0,0);height:1px;margin:-1px;overflow:hidden;padding:0; … } …	28.1 KiB	28.0 KiB

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
s-f.scribdassets.com/webpack/landing-pages/297.4a05c6.js	765.8 KiB
www.scribd.com/	391.8 KiB
js.stripe.com/v3/	225.5 KiB
www.scribd.com/_fs-ch-1T1wmsGaOgGaSxcX/assets/script.js	204.7 KiB
s-f.scribdassets.com/webpack/landing-pages/367.f2d7d5.js	192.7 KiB
www.googletagmanager.com/gtag/js?id=G-Z4ZC50DED6&cx=c&gtm=4e64f0	177.5 KiB
www.googletagmanager.com/gtag/js?id=G-8KZ8BV0P5W&cx=c&gtm=4e64f0	176.9 KiB
/webpack/assets/images/landing_pages/logged_out_homepage/...	169.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-KXQQWDG	164.9 KiB
surveys-static-prd.survicate-cdn.com/widget_core-28.23.8.js	161.2 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
div > main._1BBjPx > div.GridContainer-module_wrapper_7Rx6L- > img._37pP5Y `div > main._1BBjPx > div.GridContainer-module_wrapper_7Rx6L- > img._37pP5Y`	/webpack/assets/images/landing_pages/logged_out_homepage/...
Slideshare `div.GridRow-module_wrapper__Uub42 > div.GridColumn-module_wrapper__soqyu > a._1Td2yl > img.GCaA8S`	/webpack/assets/images/shared/logos/slideshare/slideshare...

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 180 ms

●Server Backend Latencies 430 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 0 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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.

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
Scribd - Download on the App Store `div.GridColumn-module_wrapper__soqyu > ul.mobile_icons > li.wrapper__store_button > a.app_link`
Scribd - Get it on Google Play `div.GridColumn-module_wrapper__soqyu > ul.mobile_icons > li.wrapper__store_button > a.app_link`

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
Art 6 categories View all `div.Carousel-module_outerWrapper_7O67rx > ul.Carousel-module_scrollingWrapper_jUWcdf > li._1Lr0wE > a._3QNb9o`
Biography & Memoir 4 categories View all `div.Carousel-module_outerWrapper_7O67rx > ul.Carousel-module_scrollingWrapper_jUWcdf > li._1Lr0wE > a._3QNb9o`
Instagram Instagram `div > ul.Footer-module_columnList__fqabA > li > a.TextButton-module_wrapper__ZwW-w`
Facebook Facebook `div > ul.Footer-module_columnList__fqabA > li > a.TextButton-module_wrapper__ZwW-w`
Pinterest Pinterest `div > ul.Footer-module_columnList__fqabA > li > a.TextButton-module_wrapper__ZwW-w`

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

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

●ARIA attributes are used as specified for the element's role

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

●Heading elements appear in a sequentially-descending order

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

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

○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

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
AttributionReporting	/AzZdHGSGtpxCq1Cpt/4e10b135-d113-4574-a477-270ace40bba7/o... line 1, col 168456

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
www.scribd.com/csrf_token	`Failed to load resource: the server responded with a status of 406 ()`
www.scribd.com/personalization	`Failed to load resource: the server responded with a status of 406 ()`
/api/282187/envelope/?sentry_version=7&sentry_key=2158878...	`Failed to load resource: the server responded with a status of 429 ()`
www.scribd.com/	`SyntaxError: Failed to execute 'json' on 'Response': Unexpected end of JSON input at https://s-f.scribdassets.com/webpack/landing-pages/297.4a05c6.js:1:373635 at Generator.next (<anonymous>) at r (https://s-f.scribdassets.com/webpack/landing-pages/297.4a05c6.js:1:2375907) at s (https://s-f.scribdassets.com/webpack/landing-pages/297.4a05c6.js:1:2376109)`

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

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
/hc/en-us/articles/210129026-Frequently-Asked-Questions-a...	Learn more
/hc/en-us/articles/210129026-Frequently-Asked-Questions-a...	Learn more

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 are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid