Lighthouse Desktop

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

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: div#content-container > div#home > div.banner > div.clear-banner

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

selector: div#content-container > div#home > div.banner > div.clear-banner

snippet: <div class="clear-banner" style="background-image: url('/ypu/images/banners/default/dentist.jpg')">

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

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
i3.ypcdn.com/ypu/css/jquery-ui-1.10.3.custom.min.css?7e79470	5.7 KiB
i3.ypcdn.com/ypu/css/common.min.css?7e79470	10.1 KiB	226 ms
i1.ypcdn.com/ypu/vendor/VisitorAPI.js?7e79470	20.1 KiB
i1.ypcdn.com/ypu/css/home.min.css?7e79470	9.7 KiB	225 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
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	12.1 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 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.

	URL	Resource Size	Est Savings
Q&A Banner `div.qna-bg > div.container > header > img.qna-media`	i1.ypcdn.com/ypu/images/home/qna.png?7e79470	58.7 KiB	26.6 KiB
Take YP with you. It's free `div#section-apps > div.apps-bg > div.container > img.phones`	i2.ypcdn.com/ypu/images/home/app.png?7e79470	31.7 KiB	15.6 KiB
Claim your business! Many of the benefits of YP are free. `div#content-container > div#home > div#section-claim-business > img`	i4.ypcdn.com/ypu/images/home/claim.png?7e79470	38.6 KiB	8.1 KiB

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

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: 0.0 ms 157.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-0EQTJQH34W	176.7 KiB	69.9 KiB
i2.ypcdn.com/ypu/vendor/jquery-ui-1.10.3.custom.min.js?7e79470	60.4 KiB	54.2 KiB
i1.ypcdn.com/ypu/vendor/index.bundle.js?7e79470	66.6 KiB	33.0 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
Find People Icon `div.top-bar > nav > a.intelius-link_navbar > img`	i2.ypcdn.com/ypu/images/svgs/small_avatar.svg?7e79470

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

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

URL	Time Spent
yellowpages.com/	212 ms
www.yellowpages.com/	0.0 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.2 s

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 683 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.6 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid long main-thread tasks

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

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search by City `div#home > div.top-bar > nav > a#popular-cities`

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Open Side Menu `body > header#yp-header > div.container > div#burger-menu`

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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
The Real Yellow Pages logo `body > header#yp-header > div.container > a.site-logo`

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`

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
About Us `div.primary > section > div.expand-area > a`
Contact Us `div.primary > section > div.expand-area > a`
Advertise with Us `div.primary > section > div.expand-area > a`
Corporate Blog `div.primary > section > div.expand-area > a`
Advertising Choices `div.primary > section > div.expand-area > a`
Become a Network Partner `div.primary > section > div.expand-area > a`
Marketing Solutions `div.primary > section > div.expand-area > a`
Marketing & Sales Software `div.primary > section > div.expand-area > a`
Articles `div.primary > section.site-directory > div.expand-area > a`
Find a Business `div.primary > section.site-directory > div.expand-area > a`
YP Mobile App `div.primary > section.site-directory > div.expand-area > a`
Site Map `div.primary > section.site-directory > div.expand-area > a`
Categories `div.primary > section.site-directory > div.expand-area > a`
Browse Restaurants `div.primary > section.site-directory > div.expand-area > a`
Atlanta `section.city-guides > div.expand-area > div.col > a`
Austin `section.city-guides > div.expand-area > div.col > a`
Baltimore `section.city-guides > div.expand-area > div.col > a`
Boston `section.city-guides > div.expand-area > div.col > a`
Charlotte `section.city-guides > div.expand-area > div.col > a`
Chicago `section.city-guides > div.expand-area > div.col > a`
Dallas `section.city-guides > div.expand-area > div.col > a`
Denver `section.city-guides > div.expand-area > div.col > a`
Detroit `section.city-guides > div.expand-area > div.col > a`
Houston `section.city-guides > div.expand-area > div.col > a`
Indianapolis `section.city-guides > div.expand-area > div.col > a`
Kansas City `section.city-guides > div.expand-area > div.col > a`
Las Vegas `section.city-guides > div.expand-area > div.col > a`
Los Angeles `section.city-guides > div.expand-area > div.col > a`
Louisville `section.city-guides > div.expand-area > div.col > a`
Memphis `section.city-guides > div.expand-area > div.col > a`
Miami `section.city-guides > div.expand-area > div.col > a`
Milwaukee `section.city-guides > div.expand-area > div.col > a`
New York `section.city-guides > div.expand-area > div.col > a`
Oklahoma City `section.city-guides > div.expand-area > div.col > a`
Orlando `section.city-guides > div.expand-area > div.col > a`
Philadelphia `section.city-guides > div.expand-area > div.col > a`
Phoenix `section.city-guides > div.expand-area > div.col > a`
Saint Louis `section.city-guides > div.expand-area > div.col > a`

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

●Form elements have associated labels

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

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Intelius Logo `div#content-container > div#intelius-facebox > div.alert-body > img`	i1.ypcdn.com/ypu/images/intelius-logo.png?7e79470	261 x 40 (6.53)	250 x 27 (9.26)
Intelius Logo `body > div#intelius-facebox > div.alert-body > img`	i1.ypcdn.com/ypu/images/intelius-logo.png?7e79470	261 x 40 (6.53)	250 x 27 (9.26)

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

●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

●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

○Use a strong HSTS policy

○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
www.yellowpages.com/marketing-services	Learn More

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Find People `div#browse > div#browse-menu > div.add-links > a.intelius-link_navbar`
Find People `div#home > div.top-bar > nav > a.intelius-link_navbar`

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

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid