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/ga.js	7200.0 s	17.4 KiB
www.city-data.com/js/cookie_notifier_js.php	0.0 ms	242 B

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:41.058 source:map[column:30286 line:2 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:41.058 source:map[column:31379 line:1 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js urlProvider:network]]]

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

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

URL	Time Spent
city-data.com/	963 ms
www.city-data.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: 760 ms 138.8 KiB

URL	Transfer Size	Est Savings
www.city-data.com/	78.3 KiB	78.3 KiB
www.googletagmanager.com/gtag/js?id=G-VPW5MZTH4E	152.8 KiB	60.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
USA navigation map `div.col-md-12 > div#by_state_map > div > img#states_nav_map`
City-Data Blog `div.container > div.col-md-12 > div.col-md-3 > img.lazy`
City-Data Blog `div.container > div.col-md-12 > div.col-md-3 > img.lazy`
Compare two cities `div.col-md-12 > div.col-md-6 > a > img.featurette-image`
https://www.city-data.com/advanced/search.php `div.col-md-12 > div.col-md-6 > a > img.featurette-image`
https://www.city-data.com/MeetingPlace/ `div.col-md-12 > div.col-md-6 > a > img.featurette-image`
Travel Time Maps `div.col-md-12 > div.col-md-6 > a > img.featurette-image`
Gasoline Usage Calculators `div.col-md-12 > div.col-md-6 > a > img.featurette-image`
Canada navigation map `div.col-md-12 > div.col-md-6 > div > img#canada_nav_map`
google custom search `form#search_bar_box > div#search_box_under > p > img#search_o_google`

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 559 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.6 s

●Avoid long main-thread tasks 6 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 60 ms

●Server Backend Latencies 90 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○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
CA `div#quickview_tabSelected > p > a > span.badge`
CA `div#quickview_tabSelected > p > a > span.badge`
CA `div#quickview_tabSelected > p > a > span.badge`
CA `div#quickview_tabSelected > p > a > span.badge`
Loading data... please wait `div#mapOSM > div#loadingMSG > center > strong`
Loading data... please wait `div#interactiveBoxMap > div#mapBox > div#lastCont > div#mapOSM_legend`
City-Data Blog `div.col-md-12 > div.col-md-9 > p.textowo > a`
Popular New Year’s resolutions `div.blog-articles > ul.list-inline > li > a`
Dec 31 `div.blog-articles > ul.list-inline > li > i`
Christmas is America’s favorite holiday season `div.blog-articles > ul.list-inline > li > a`
Dec 24 `div.blog-articles > ul.list-inline > li > i`
Fish in the American dish: recreational fishing `div.blog-articles > ul.list-inline > li > a`
Dec 10 `div.blog-articles > ul.list-inline > li > i`
American hunting and wildlife `div.blog-articles > ul.list-inline > li > a`
Nov 19 `div.blog-articles > ul.list-inline > li > i`
The National Football League is an American treasure `div.blog-articles > ul.list-inline > li > a`
Nov 12 `div.blog-articles > ul.list-inline > li > i`
city guides `div.col-md-12 > div.col-md-9 > p.textowo > a`
Alberta `div.col-md-6 > ul.canada_list > li > a`
British Columbia `div.col-md-6 > ul.canada_list > li > a`
Manitoba `div.col-md-6 > ul.canada_list > li > a`
New Brunswick `div.col-md-6 > ul.canada_list > li > a`
Newfoundland and Labrador `div.col-md-6 > ul.canada_list > li > a`
Northwest Territories `div.col-md-6 > ul.canada_list > li > a`
Nova Scotia `div.col-md-6 > ul.canada_list > li > a`
Nunavut `div.col-md-6 > ul.canada_list > li > a`
Ontario `div.col-md-6 > ul.canada_list > li > a`
Prince Edward Island `div.col-md-6 > ul.canada_list > li > a`
Quebec `div.col-md-6 > ul.canada_list > li > a`
Saskatchewan `div.col-md-6 > ul.canada_list > li > a`
Yukon Territory `div.col-md-6 > ul.canada_list > li > a`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
City-Data Blog. `div.col-md-9 > h2.featurette-heading > span.text-muted > a`
City-Data Blog `div.col-md-12 > div.col-md-9 > p.textowo > a`
City-Data Forum. `div.col-md-9 > h2.featurette-heading > span.text-muted > a`
city guides `div.col-md-12 > div.col-md-9 > p.textowo > a`
Top 100 City Lists `div.container > div.col-md-7 > p > a`
Top 101 City Lists `div.container > div.col-md-7 > p > a`
random city pictures `div.container > div.col-md-7 > p > a`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Our California data `div.col-md-12 > div#by_state_map > div#quickview_tabSelected > h4`
Cities `div#tabs_by_category > div.tab-content > div#home1 > h4.h4-lista`
Compare two cities `div.container > div.col-md-12 > div.col-md-6 > h4`
Local data `div.container > div.col-md-6 > div.col-md-12 > h4.h4-lista-footer`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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#mapBox > div#firstCont > div#map_searchPanel > input#sbox `div#mapBox > div#firstCont > div#map_searchPanel > input#sbox`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Median household income ($) Median household income (% change since 2000) House… `div#interactiveBoxMap > div#mapBox > div#firstCont > select#selmapOSM`

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
div.navbar > div.container-menu > div.navbar-header > a.navbar-brand `div.navbar > div.container-menu > div.navbar-header > a.navbar-brand`

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

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
div.navbar > div.container-menu > div.navbar-header > a.navbar-brand `div.navbar > div.container-menu > div.navbar-header > a.navbar-brand`
OK `div.col-md-12 > div#by_state_map > div > a.states_map_links`
ND `div.col-md-12 > div#by_state_map > div > a.states_map_links`
SD `div.col-md-12 > div#by_state_map > div > a.states_map_links`
NE `div.col-md-12 > div#by_state_map > div > a.states_map_links`
KS `div.col-md-12 > div#by_state_map > div > a.states_map_links`
AR `div.col-md-12 > div#by_state_map > div > a.states_map_links`
LA `div.col-md-12 > div#by_state_map > div > a.states_map_links`
MS `div.col-md-12 > div#by_state_map > div > a.states_map_links`
AL `div.col-md-12 > div#by_state_map > div > a.states_map_links`
GA `div.col-md-12 > div#by_state_map > div > a.states_map_links`
SC `div.col-md-12 > div#by_state_map > div > a.states_map_links`
IL `div.col-md-12 > div#by_state_map > div > a.states_map_links`
MI `div.col-md-12 > div#by_state_map > div > a.states_map_links`
IN `div.col-md-12 > div#by_state_map > div > a.states_map_links`
OH `div.col-md-12 > div#by_state_map > div > a.states_map_links`
TN `div.col-md-12 > div#by_state_map > div > a.states_map_links`
KY `div.col-md-12 > div#by_state_map > div > a.states_map_links`
NC `div.col-md-12 > div#by_state_map > div > a.states_map_links`
WV `div.col-md-12 > div#by_state_map > div > a.states_map_links`
VA `div.col-md-12 > div#by_state_map > div > a.states_map_links`
PA `div.col-md-12 > div#by_state_map > div > a.states_map_links`
NY `div.col-md-12 > div#by_state_map > div > a.states_map_links`
VT `div.col-md-12 > div#by_state_map > div > a.states_map_links`
NH `div.col-md-12 > div#by_state_map > div > a.states_map_links`
RI `div.col-md-12 > div#by_state_map > div > a.states_map_links`
CT `div.col-md-12 > div#by_state_map > div > a.states_map_links`
NJ `div.col-md-12 > div#by_state_map > div > a.states_map_links`
DE `div.col-md-12 > div#by_state_map > div > a.states_map_links`
MD `div.col-md-12 > div#by_state_map > div > a.states_map_links`
MA `div.col-md-12 > div#by_state_map > div > a.states_map_links`
DC `div.col-md-12 > div#by_state_map > div > a.states_map_links`
div#firstCont > label#CM_seriesSwitch > div > input `div#firstCont > label#CM_seriesSwitch > div > input`
YT `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
NT `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
NU `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
BC `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
AB `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
MB `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
ON `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
PE `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
NS `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
NB `div.col-md-12 > div.col-md-6 > div > a.canada_map_links`
Nova Scotia `div.col-md-6 > ul.canada_list > li > a`
Nunavut `div.col-md-6 > ul.canada_list > li > a`
Ontario `div.col-md-6 > ul.canada_list > li > a`
Saskatchewan `div.col-md-6 > ul.canada_list > li > a`
Yukon Territory `div.col-md-6 > ul.canada_list > li > a`
Forum Archive 1, `div.col-md-3 > ul.footer-lista > li > a`
2, `div.col-md-3 > ul.footer-lista > li > a`
3, `div.col-md-3 > ul.footer-lista > li > a`
4, `div.col-md-3 > ul.footer-lista > li > a`
5, `div.col-md-3 > ul.footer-lista > li > a`
6, `div.col-md-3 > ul.footer-lista > li > a`
7, `div.col-md-3 > ul.footer-lista > li > a`
8, `div.col-md-3 > ul.footer-lista > li > a`
9, `div.col-md-3 > ul.footer-lista > li > a`
10, `div.col-md-3 > ul.footer-lista > li > a`
11, `div.col-md-3 > ul.footer-lista > li > a`
12, `div.col-md-3 > ul.footer-lista > li > a`
13, `div.col-md-3 > ul.footer-lista > li > a`
14, `div.col-md-3 > ul.footer-lista > li > a`
15, `div.col-md-3 > ul.footer-lista > li > a`
16, `div.col-md-3 > ul.footer-lista > li > a`
17, `div.col-md-3 > ul.footer-lista > li > a`
18, `div.col-md-3 > ul.footer-lista > li > a`
19, `div.col-md-3 > ul.footer-lista > li > a`
20, `div.col-md-3 > ul.footer-lista > li > a`
21, `div.col-md-3 > ul.footer-lista > li > a`
22, `div.col-md-3 > ul.footer-lista > li > a`
23, `div.col-md-3 > ul.footer-lista > li > a`
24, `div.col-md-3 > ul.footer-lista > li > a`
25, `div.col-md-3 > ul.footer-lista > li > a`
26, `div.col-md-3 > ul.footer-lista > li > a`
27, `div.col-md-3 > ul.footer-lista > li > a`
28, `div.col-md-3 > ul.footer-lista > li > a`
29, `div.col-md-3 > ul.footer-lista > li > a`
30, `div.col-md-3 > ul.footer-lista > li > a`
31 `div.col-md-3 > ul.footer-lista > li > 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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○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

○`[aria-*]` attributes have valid values

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

○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 type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○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 natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
USA navigation map `div.col-md-12 > div#by_state_map > div > img#states_nav_map`		322 x 195	256 x 155	483 x 293

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
pics3.city-data.com/fonts/glyphicons-halflings-regular.woff2	`Failed to load resource: net::ERR_CONNECTION_REFUSED`
pics3.city-data.com/css/bootstrap.min.css	`Failed to load resource: net::ERR_CONNECTION_REFUSED`
pics3.city-data.com/fonts/city-data.woff?73345346	`Failed to load resource: net::ERR_CONNECTION_REFUSED`
pics3.city-data.com/assets/mobile/bg/1background.jpg	`Failed to load resource: net::ERR_CONNECTION_REFUSED`
pics3.city-data.com/fonts/city-data.ttf?73345346	`Failed to load resource: net::ERR_CONNECTION_REFUSED`
pics3.city-data.com/fonts/glyphicons-halflings-regular.woff	`Failed to load resource: net::ERR_CONNECTION_REFUSED`
pics3.city-data.com/fonts/glyphicons-halflings-regular.ttf	`Failed to load resource: net::ERR_CONNECTION_REFUSED`
pics3.city-data.com/assets/mobile/maps/states_bg.png	`Failed to load resource: net::ERR_CONNECTION_REFUSED`

●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

●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

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`