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
notepad-plus-plus.org/assets/images/notepad4ever.png	0.0 ms	34.7 KiB
notepad-plus-plus.org/images/logo.svg	0.0 ms	31.3 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
notepad-plus-plus.org/css/fonts/miriamlibre-bold.woff2	0.0 ms	11.9 KiB
cdn.carbonads.com/carbon.js?serve=CKYIE53I&placement=notepad-plus-plusorg	0.0 ms	10.6 KiB
notepad-plus-plus.org/js/prism.js	0.0 ms	5.2 KiB
notepad-plus-plus.org/css/styles.css	0.0 ms	4.7 KiB
notepad-plus-plus.org/js/dom-scripts.js	0.0 ms	1.5 KiB
srv.carbonads.net/static/30242/6d8988794d4c3f29275f187830980a61c8e59feb	604800.0 s	14.6 KiB
notepad-plus-plus.org/css/prism.css	0.0 ms	1.3 KiB
insight.adsrvr.org/track/pxl/?adv=t3k9qrj&ct=0:djrfa1z&fmt=3&orderid=&v=	0.0 ms	149 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.18346400000000002] map[node:map[boundingRect:map[bottom:1591 height:1063 left:0 right:412 top:528 width:412] lhId:page-1-DIV nodeLabel:What is Notepad++ Notepad++ is a free (as in “free speech” and also as in “fre… path:1,HTML,1,BODY,2,DIV,1,DIV selector:body > div.wrapper > div.main-and-footer snippet:<div class="main-and-footer"> type:node] score:0.128468 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1351 height:172 left:39 right:373 top:1179 width:334] lhId:page-2-IMG nodeLabel:div > main#main > p > img path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,0,MAIN,3,P,0,IMG selector:div > main#main > p > img snippet:<img src="/assets/images/notepad4ever.png" alt=""> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1591 height:1063 left:0 right:412 top:528 width:412] lhId:page-1-DIV nodeLabel:What is Notepad++ Notepad++ is a free (as in “free speech” and also as in “fre… path:1,HTML,1,BODY,2,DIV,1,DIV selector:body > div.wrapper > div.main-and-footer snippet:<div class="main-and-footer"> type:node] score:0.027498 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1351 height:172 left:39 right:373 top:1179 width:334] lhId:page-2-IMG nodeLabel:div > main#main > p > img path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,0,MAIN,3,P,0,IMG selector:div > main#main > p > img snippet:<img src="/assets/images/notepad4ever.png" alt=""> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1591 height:1063 left:0 right:412 top:528 width:412] lhId:page-1-DIV nodeLabel:What is Notepad++ Notepad++ is a free (as in “free speech” and also as in “fre… path:1,HTML,1,BODY,2,DIV,1,DIV selector:body > div.wrapper > div.main-and-footer snippet:<div class="main-and-footer"> type:node] score:0.027498 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1351 height:172 left:39 right:373 top:1179 width:334] lhId:page-2-IMG nodeLabel:div > main#main > p > img path:1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,0,MAIN,3,P,0,IMG selector:div > main#main > p > img snippet:<img src="/assets/images/notepad4ever.png" alt=""> type:node]]] type:subitems]]]

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
div > main#main > p > img `div > main#main > p > img`	notepad-plus-plus.org/assets/images/notepad4ever.png	34.5 KiB	32.6 KiB
ads via Carbon `span > span.carbon-wrap > a.carbon-img > img`	srv.carbonads.net/static/30242/6d8988794d4c3f29275f187830980a61c8e59feb	14.8 KiB	13.2 KiB

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

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
notepad-plus-plus.org/css/fonts/miriamlibre-bold.woff2	20 ms

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
notepad-plus-plus.org/css/styles.css	4.7 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
What is Notepad++ Notepad++ is a free (as in “free speech” and also as in “fre… `body > div.wrapper > div.main-and-footer`	0.128
What is Notepad++ Notepad++ is a free (as in “free speech” and also as in “fre… `body > div.wrapper > div.main-and-footer`	0.027
What is Notepad++ Notepad++ is a free (as in “free speech” and also as in “fre… `body > div.wrapper > div.main-and-footer`	0.027

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

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-06CVYXZPHS&cx=c&gtm=4e64h1	162.8 KiB	67.5 KiB
www.googletagmanager.com/gtag/js?id=UA-148378786-1	125.1 KiB	63.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 > main#main > p > img `div > main#main > p > img`	notepad-plus-plus.org/assets/images/notepad4ever.png
div > div.intro > a.logo > img `div > div.intro > a.logo > img`	notepad-plus-plus.org/images/logo.svg

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

●Document request latency

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

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.7 s

●Avoid long main-thread tasks 3 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 160 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

○LCP request discovery

○Avoid non-composited animations

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

●Form elements have associated labels

●`[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 are distinguishable without relying on color.

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○`<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)
ads via Carbon `span > span.carbon-wrap > a.carbon-img > img`	srv.carbonads.net/static/30242/6d8988794d4c3f29275f187830980a61c8e59feb	81 x 100 (0.81)	260 x 200 (1.30)

●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

●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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid