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
cmp.inmobi.com/tcfv2/56/cmp2.js?referer=cplusplus.com	900.0 s	112.5 KiB
cplusplus.com/v3.3.4/bg.png	0.0 ms	98.1 KiB
cmp.inmobi.com/tcfv2/56/cmp2ui-en.js	900.0 s	104.5 KiB
cdn.fuseplatform.net/publift/tags/2/4030/fuse.js	1800.0 s	102.5 KiB
cplusplus.com/v3.3.4/main.js	0.0 ms	39.4 KiB
cplusplus.com/v3.3.4/site.css	0.0 ms	19.9 KiB
ssl.google-analytics.com/ga.js	7200.0 s	17.4 KiB
cplusplus.com/img/progress.gif	0.0 ms	8.5 KiB
cplusplus.com/img/bg_ref.gif	0.0 ms	5.2 KiB
cplusplus.com/img/bg_info.gif	0.0 ms	3.8 KiB
cse.google.com/cse.js?cx=partner-pub-7688470879129516:0646519325	0.0 ms	3.6 KiB
cplusplus.com/img/bg_doc.gif	0.0 ms	3.3 KiB
www.google.com/cse/static/style/look/v6/default.css	3000.0 s	1.2 KiB
cmp.inmobi.com/choice/PRrmquD1Ggcb1/cplusplus.com/choice.js?tag_version=V3	900.0 s	413 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
tr > td.top > a > span.C_ico `tr > td.top > a > span.C_ico`	cplusplus.com/v3.3.4/bg.png	97.9 KiB	83.3 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:317.891 label:Time to first byte subpart:timeToFirstByte] map[duration:2190.673 label:Element render delay subpart:elementRenderDelay]]

lhId: page-1-DIV

nodeLabel: We and our partners store and/or access information on a device, such as cookie…

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

selector: div.qc-cmp2-consent-info > div.qc-cmp2-publisher-logo-container > div.qc-cmp2-summary-info > div

snippet: <div class="">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
cplusplus.com/	http/1.1
cplusplus.com/v3.3.4/site.css	http/1.1
cplusplus.com/v3.3.4/main.js	http/1.1
cplusplus.com/img/progress.gif	http/1.1
cplusplus.com/img/bg_info.gif	http/1.1
cplusplus.com/img/bg_ref.gif	http/1.1
cplusplus.com/img/bg_doc.gif	http/1.1
cplusplus.com/v3.3.4/bg.png	http/1.1
cplusplus.com/favicon.ico	http/1.1

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
cplusplus.com/v3.3.4/main.js	39.4 KiB	1.3 s
cplusplus.com/v3.3.4/site.css	19.9 KiB	506 ms
/css2?family=Oswald:wght@400&family=Roboto+Condensed:wght...	2.6 KiB	832 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

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 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: 200 ms 26.7 KiB

URL	Transfer Size	Est Savings
cplusplus.com/v3.3.4/site.css	19.7 KiB	15.2 KiB
www.google.com/cse/static/element/dc329f57de078f5d/default_v6+en.css	11.9 KiB	11.5 KiB

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: 2.8 s 564.8 KiB

URL	Transfer Size	Est Savings
cdn.fuseplatform.net/prebid/prebid-8.52.0-8822dbc4ab242268baafd46f1f4123ad.js	171.7 KiB	136.8 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	123.4 KiB
cmp.inmobi.com/tcfv2/56/cmp2.js?referer=cplusplus.com	112.0 KiB	55.6 KiB
/cse/static/element/dc329f57de078f5d/cse_element__en.js?u...	102.7 KiB	54.0 KiB
cmp.inmobi.com/tcfv2/56/cmp2ui-en.js	104.0 KiB	49.7 KiB
cdn.fuseplatform.net/publift/tags/2/4030/fuse.js	101.9 KiB	46.8 KiB
fundingchoicesmessages.google.com/i/190286186?ers=3	68.7 KiB	37.2 KiB
cse.google.com/adsense/search/async-ads.js	43.3 KiB	31.5 KiB
cplusplus.com/v3.3.4/main.js	39.1 KiB	29.9 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
cmp.inmobi.com/tcfv2/56/cmp2.js?referer=cplusplus.com	425 ms	273 ms	35 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	289 ms	237 ms	46 ms
cdn.fuseplatform.net/publift/tags/2/4030/fuse.js	269 ms	200 ms	33 ms
Unattributable	246 ms	12 ms	0.0 ms
cplusplus.com/	235 ms	19 ms	3.1 ms
cmp.inmobi.com/tcfv2/56/cmp2ui-en.js	227 ms	174 ms	33 ms
fundingchoicesmessages.google.com/i/190286186?ers=3	182 ms	153 ms	17 ms
cdn.fuseplatform.net/prebid/prebid-8.52.0-8822dbc4ab242268baafd46f1f4123ad.js	163 ms	120 ms	42 ms
cse.google.com/cse.js?cx=partner-pub-7688470879129516:0646519325	93 ms	71 ms	0.9 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	75 ms	64 ms	9.8 ms
/cse/static/element/dc329f57de078f5d/cse_element__en.js?u...	51 ms	23 ms	26 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	1.5 s
Other	411 ms
Script Parsing & Compilation	266 ms
Style & Layout	215 ms
Parse HTML & CSS	23 ms
Rendering	23 ms
Garbage Collection	20 ms

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

URL	Transfer Size	Est Savings
www.google.com/cse/static/element/dc329f57de078f5d/default_v6+en.css	12.0 KiB	3.3 KiB

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

●Font display

●Forced reflow

●Optimize viewport for mobile

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,454 KiB

●Avoid long main-thread tasks 12 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 30 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 110 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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.

Names and labels

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
C++ Language: Learn this versatile and powerful programming language. Includes … `div#I_content > div.hags > div.bid > li`

These are opportunities to improve the experience of reading tabular or list data using 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`

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

●Form elements have associated labels

●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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○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 a valid value for its `[lang]` attribute

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

○Image elements have `[alt]` attributes

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

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

○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

●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

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`