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.

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.

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
Stubhub `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/stubhub.jpeg	26.3 KiB	25.4 KiB
BCBS `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/blue-cross.jpeg	16.0 KiB	15.1 KiB
State Farm `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/state-farm.jpeg	12.1 KiB	11.2 KiB
Quickbooks `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/quick-books.jpeg	12.1 KiB	11.1 KiB
Honey `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/honey.jpeg	12.0 KiB	11.0 KiB
Experian `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/experian.jpeg	11.2 KiB	10.2 KiB
Mercedes `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/mercedes.jpeg	11.1 KiB	10.1 KiB
Amazon `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/amazon.jpeg	9.5 KiB	8.5 KiB
eBay `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/ebay.jpeg	9.2 KiB	8.2 KiB
Ancestry `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/quicklinks/ancestry.jpeg	9.0 KiB	8.1 KiB
Geography `div.icons-list > a.meson-button > span.image-container > img.image`	www.excite.com/static/images/excite/moreresources/geography.png	6.0 KiB	5.0 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-11-IMG

nodeLabel: div.header-container-header > div.logo > a.meson-button > img

path: 1,HTML,1,BODY,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,A,0,IMG

selector: div.header-container-header > div.logo > a.meson-button > img

snippet: <img src="/static/logos/excite.com.svg">

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
cdn.cookielaw.org/scripttemplates/otSDKStub.js	0 B	780 ms
cdn.cookielaw.org/consent/5a9ae5d2-5914-4f6d-a884-1b4559709aac/OtAutoBlock.js	0 B	780 ms
www.excite.com/assets/451b8cb/pageview.js	27.9 KiB	600 ms

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.excite.com/static/logos/excite.com.svg	0.0 ms	4.4 KiB

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
www.excite.com/static/icomoon.ttf	5.0 ms

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

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

URL	Time Spent
excite.com/	842 ms
www.excite.com/	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

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: 900 ms 242.0 KiB

URL	Transfer Size	Est Savings
www.excite.com/assets/451b8cb/app.js	149.3 KiB	75.3 KiB
www.googletagmanager.com/gtag/js?id=G-JWGLYE8PG5&cx=c&gtm=4e64k0	143.5 KiB	63.3 KiB
/gtm.js?id=GTM-KMFC6W2&gtm_auth=&gtm_preview=&gtm_cookies...	159.0 KiB	52.8 KiB
www.excite.com/assets/451b8cb/4913.js	29.2 KiB	28.1 KiB
code.jquery.com/jquery-3.7.0.min.js	29.6 KiB	22.5 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.header-container-header > div.logo > a.meson-button > img `div.header-container-header > div.logo > a.meson-button > img`	www.excite.com/static/logos/excite.com.svg

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

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 781 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 1.0 s

●Minimizes main-thread work 1.7 s

●Avoid long main-thread tasks 11 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

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.

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
WEB `div.border-line > div.search > div.input-row > div.dropdown-btn`
Email `nav.side-menu > ul.menu-list > li.menu-button > a.meson-button`
News `nav.side-menu > ul.menu-list > li.menu-button > a.meson-button`
Weather `nav.side-menu > ul.menu-list > li.menu-button > a.meson-button`
Games `nav.side-menu > ul.menu-list > li.menu-button > a.meson-button`
Finance `nav.side-menu > ul.menu-list > li.menu-button > a.meson-button`
Sports `nav.side-menu > ul.menu-list > li.menu-button > a.meson-button`
Entertainment `nav.side-menu > ul.menu-list > li.menu-button > a.meson-button`
Horoscope `nav.side-menu > ul.menu-list > li.menu-button > a.meson-button`
Travel `nav.side-menu > ul.menu-list > li.menu-button > a.meson-button`
Sitemap `div.excite-footer > ul.footer-list > li.footer-item > a.meson-button`
Email `div.excite-footer > ul.footer-list > li.footer-item > a.meson-button`
Terms of Service `div.excite-footer > ul.footer-list > li.footer-item > a.meson-button`
Privacy Policy `div.excite-footer > ul.footer-list > li.footer-item > a.meson-button`

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.header-container-header > div.logo > a.meson-button > img `div.header-container-header > div.logo > a.meson-button > img`

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.border-line > div.search > div.input-row > input `div.border-line > div.search > div.input-row > input`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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.

○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

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

●Uses ARIA roles only on compatible elements

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

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

100

Best Practices

General

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.excite.com/assets/451b8cb/app.js

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

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

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

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`https://www.excite.com/robots.txt`

To appear in search results, crawlers need access to your app.

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.

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.header-container-header > div.logo > a.meson-button > img `div.header-container-header > div.logo > a.meson-button > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Document has a `<title>` element

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