Skip to content
https://abc.xyz

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.

45

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.

RequestCache TTLTransfer Size
widgets.q4app.com/widgets/dependencies/q4.core.1.1.9.min.js0.0 ms761.3 KiB
s206.q4cdn.com/479360582/files/design/blocks.png3600.0 s501.3 KiB
abc.xyz/js/module/widgets/dist/dependencies/evergreen.core.1.0.0.min.js10.0 s202.2 KiB
abc.xyz/css/evergreen/dist/default/evergreen.1.0.0.min.css10.0 s58.8 KiB
s206.q4cdn.com/479360582/files/css/global.css?v=433043600.0 s62.5 KiB
s206.q4cdn.com/479360582/files/design/alphabet_logo.png3600.0 s57.2 KiB
/479360582/files/fonts/Google_Sans_Display_Medium/google-...3600.0 s56.0 KiB
/479360582/files/fonts/Google_Sans_Display_Regular/google...3600.0 s55.4 KiB
widgets.q4app.com/widgets/dependencies/q4.app.1.1.9.min.js0.0 ms41.1 KiB
abc.xyz/GlobalBranding.ashx10.0 s35.3 KiB
widgets.q4app.com/widgets/q4.nav.1.0.0.min.js0.0 ms30.5 KiB
abc.xyz/js/typescript/dist/index.js10.0 s30.4 KiB
s206.q4cdn.com/479360582/files/design/alphabet_footer_logo.png3600.0 s28.4 KiB
s206.q4cdn.com/479360582/files/design/gblock-1.png3600.0 s25.9 KiB
widgets.q4app.com/widgets/q4.api.1.13.5.min.js0.0 ms19.7 KiB
s206.q4cdn.com/479360582/files/css/client.css?v=396563600.0 s20.5 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
widgets.q4app.com/widgets/q4.datepicker.1.0.0.min.js0.0 ms13.6 KiB
s206.q4cdn.com/479360582/files/design/signature-larry-page-n-w600-h208.png3600.0 s16.2 KiB
abc.xyz/js/module/widgets/dist/dependencies/evergreen.app.1.0.0.min.js10.0 s12.5 KiB
abc.xyz/js/module/widgets/dist/latest/evergreen.q4Api.min.js10.0 s6.1 KiB
sidebar.bugherd.com/embed.js?apikey=0v7un9kwhfa25yamhh0hjw14400.0 s7.7 KiB
sidebar.bugherd.com/embed.js?apikey=0v7un9kwhfa25yamhh0hjw14400.0 s7.1 KiB
abc.xyz/js/typescript/dist/q4CookieConsent/index.js10.0 s2.7 KiB
abc.xyz/js/module/widgets/dist/latest/evergreen.q4Pager.min.js10.0 s2.3 KiB
s206.q4cdn.com/479360582/files/fonts/style-cf.css3600.0 s2.1 KiB
abc.xyz/js/module/widgets/dist/latest/evergreen.q4MultiSecFilings.min.js10.0 s1.5 KiB
abc.xyz/js/module/widgets/dist/latest/evergreen.q4Slideshow.min.js10.0 s1.2 KiB
abc.xyz/js/anti-csrf.js10.0 s1.0 KiB
s206.q4cdn.com/479360582/files/css/print.css3600.0 s1.2 KiB
s206.q4cdn.com/479360582/files/js/polyfills/findIndex_polyfill.js3600.0 s1.0 KiB

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
Alphabet investor relations div.module_container > div.module_container > a > img
s206.q4cdn.com/479360582/files/design/alphabet_logo.png56.8 KiB54.2 KiB
Alphabet investor relations div.module_container > div.module_container > a > img
s206.q4cdn.com/479360582/files/design/alphabet_footer_logo.png28.0 KiB25.6 KiB
div.HomepageHeading-content-wrapper > div.HomepageHeading-content > div.google-block > img div.HomepageHeading-content-wrapper > div.HomepageHeading-content > div.google-block > img
s206.q4cdn.com/479360582/files/design/gblock-1.png25.5 KiB19.8 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:40.735 label:Time to first byte subpart:timeToFirstByte] map[duration:2755.23 label:Resource load delay subpart:resourceLoadDelay] map[duration:263.096 label:Resource load duration subpart:resourceLoadDuration] map[duration:269.81 label:Element render delay subpart:elementRenderDelay]]
lhId: page-3-IMG
nodeLabel: Larry Page Signature
path: 1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,0,FORM,3,DIV,1,DIV,2,MAIN,2,DIV,0,DIV,0,SPAN,0,SPAN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,PICTURE,2,IMG
selector: div.Enhancement-item > figure.Figure > picture > img.Image
snippet: <img class="Image" alt="Larry Page Signature" srcset=" /files/design/signature-larry…" width="300" height="104" data-src="//s206.q4cdn.com/479360582/files/design/signature-larry-page-n-w300-h104.p…" data-lazy-load="true" src="https://abc.xyz/files/design/signature-larry-page-n-w600-h208.png">

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-3-IMG
nodeLabel: Larry Page Signature
path: 1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,0,FORM,3,DIV,1,DIV,2,MAIN,2,DIV,0,DIV,0,SPAN,0,SPAN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,PICTURE,2,IMG
selector: div.Enhancement-item > figure.Figure > picture > img.Image
snippet: <img class="Image" alt="Larry Page Signature" srcset=" /files/design/signature-larry…" width="300" height="104" data-src="//s206.q4cdn.com/479360582/files/design/signature-larry-page-n-w300-h104.p…" data-lazy-load="true" src="https://abc.xyz/files/design/signature-larry-page-n-w600-h208.png">

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.

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.

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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 33.0 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.

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 Evaluation1.1 s
Other417 ms
Script Parsing & Compilation406 ms
Parse HTML & CSS202 ms
Style & Layout181 ms
Rendering7.0 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 2.3 KiB
URLTransfer SizeEst Savings
inline: $('.nav-data').nav({ styleMobile: …2.9 KiB2.3 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
Alphabet investor relations div.module_container > div.module_container > a > img
s206.q4cdn.com/479360582/files/design/alphabet_footer_logo.png
Alphabet investor relations div.module_container > div.module_container > a > img
s206.q4cdn.com/479360582/files/design/alphabet_logo.png
div.HomepageHeading-content-wrapper > div.HomepageHeading-content > div.google-block > img div.HomepageHeading-content-wrapper > div.HomepageHeading-content > div.google-block > img
s206.q4cdn.com/479360582/files/design/gblock-1.png

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
●Forced reflow
●Modern HTTP
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 2,399 KiB
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 8 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 0 ms
●Server Backend Latencies 360 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 20 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
100

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.

○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
●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 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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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
○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.
○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.
○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.
92

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.

SourceDescription
abc.xyz/ line 1024, col 28
TypeError: ".HeaderPaneDiv4".insertBefore is not a function at https://abc.xyz/:1025:29

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

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.

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