Skip to content
https://ntp.org

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

34

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.

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.528257] map[node:map[boundingRect:map[bottom:1239 height:1239 left:0 right:412 top:0 width:412] lhId:page-1-BODY nodeLabel:body path:1,HTML,1,BODY selector:body snippet:<body style="--bs-body-text-align: center;"> type:node] score:0.489121 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1048 height:16 left:172 right:188 top:1032 width:16] lhId:page-12-IMG nodeLabel:section.min-vh-100 > button.btn > a.btn > img path:1,HTML,1,BODY,4,SECTION,4,BUTTON,0,A,1,IMG selector:section.min-vh-100 > button.btn > a.btn > img snippet:<img src="https://www.ntp.org/images/icons/download.svg"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1086 height:857 left:0 right:412 top:229 width:412] lhId:page-6-SECTION nodeLabel:Your Donations Help Support NTP -- Donate Today! Welcome to the home of the Net… path:1,HTML,1,BODY,4,SECTION selector:body > section.min-vh-100 snippet:<section class="min-vh-100 mt-auto"> type:node] score:0.024259 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1048 height:16 left:172 right:188 top:1032 width:16] lhId:page-12-IMG nodeLabel:section.min-vh-100 > button.btn > a.btn > img path:1,HTML,1,BODY,4,SECTION,4,BUTTON,0,A,1,IMG selector:section.min-vh-100 > button.btn > a.btn > img snippet:<img src="https://www.ntp.org/images/icons/download.svg"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:700 height:230 left:0 right:412 top:470 width:412] lhId:page-0-P nodeLabel:The NTP Project conducts Research and Development in NTP, a protocol designed t… path:1,HTML,1,BODY,4,SECTION,1,DIV,2,DIV,1,P selector:section.min-vh-100 > div.container > div.row > p snippet:<p> type:node] score:0.007798 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1048 height:16 left:172 right:188 top:1032 width:16] lhId:page-12-IMG nodeLabel:section.min-vh-100 > button.btn > a.btn > img path:1,HTML,1,BODY,4,SECTION,4,BUTTON,0,A,1,IMG selector:section.min-vh-100 > button.btn > a.btn > img snippet:<img src="https://www.ntp.org/images/icons/download.svg"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:970 height:592 left:0 right:412 top:378 width:412] lhId:page-11-DIV nodeLabel:Welcome to the home of the Network Time Protocol (NTP) Project. The NTP Proj… path:1,HTML,1,BODY,4,SECTION,1,DIV selector:body > section.min-vh-100 > div.container snippet:<div class="container" style="--bs-body-text-align: start;"> type:node] score:0.007079 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1048 height:16 left:172 right:188 top:1032 width:16] lhId:page-12-IMG nodeLabel:section.min-vh-100 > button.btn > a.btn > img path:1,HTML,1,BODY,4,SECTION,4,BUTTON,0,A,1,IMG selector:section.min-vh-100 > button.btn > a.btn > img snippet:<img src="https://www.ntp.org/images/icons/download.svg"> type:node]]] type:subitems]]]

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.

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.

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.

URLResource SizeEst Savings
section.min-vh-100 > div.card > div.card-body > img.figure-img section.min-vh-100 > div.card > div.card-body > img.figure-img
www.nwtime.org/images/support.jpg18.2 KiB15.8 KiB
div.container-fluid > div > a.navbar-brand > img div.container-fluid > div > a.navbar-brand > img
www.ntp.org/images/logo.png6.1 KiB4.4 KiB

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: 1.5 s
URLTime Spent
ntp.org/1.5 s
www.ntp.org/0.0 ms

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.

ElementLayout shift score
body body
0.489
Your Donations Help Support NTP -- Donate Today! Welcome to the home of the Net… body > section.min-vh-100
0.024
The NTP Project conducts Research and Development in NTP, a protocol designed t… section.min-vh-100 > div.container > div.row > p
0.008
Welcome to the home of the Network Time Protocol (NTP) Project. The NTP Proj… body > section.min-vh-100 > div.container
0.007

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: 310 ms 76.3 KiB
URLTransfer SizeEst Savings
www.ntp.org/scss/nwtime.min.33139960351778bcc5aee21b22a8ddf3.css82.4 KiB76.3 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: 620 ms 140.6 KiB

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 2.8 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
section.min-vh-100 > div.card > div.card-body > img.figure-img section.min-vh-100 > div.card > div.card-body > img.figure-img
www.nwtime.org/images/support.jpg
section.min-vh-100 > button.btn > a.btn > img section.min-vh-100 > button.btn > a.btn > img
www.ntp.org/images/icons/download.svg
section.min-vh-100 > button.btn > a.btn > img section.min-vh-100 > button.btn > a.btn > img
www.ntp.org/images/icons/bug.svg

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

Optimize DOM size
Font display
Forced reflow
LCP breakdown
Optimize viewport for mobile
Minify JavaScript
Avoids enormous network payloads Total size was 564 KiB
User Timing marks and measures 7 user timings
JavaScript execution time 1.0 s
Minimizes main-thread work 1.7 s
Avoid long main-thread tasks 5 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 220 ms
Server Backend Latencies 170 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 180 ms
INP breakdown
LCP request discovery
Avoid non-composited animations
79

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
SUPPORT div.container-fluid > div > button.btn > a.nav-item
REFERENCE LIBRARY div.container-fluid > div > button.btn > a.nav-item
DOCUMENTATION div.container-fluid > div > button.btn > a.nav-item
DONATE div.container-fluid > div > button.btn > a.nav-item
DOWNLOAD NTP body > section.min-vh-100 > button.btn > a.btn
REPORT A BUG body > section.min-vh-100 > button.btn > a.btn
© 2026 Network Time Foundation nav.site-footer > div.container > ul.mx-auto > p
Network Time Foundation div.container > ul.mx-auto > p > a.navbar-text

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
section.min-vh-100 > div.card > div.card-body > img.figure-img section.min-vh-100 > div.card > div.card-body > img.figure-img
section.min-vh-100 > button.btn > a.btn > img section.min-vh-100 > button.btn > a.btn > img
section.min-vh-100 > button.btn > a.btn > img section.min-vh-100 > button.btn > a.btn > img
ul.navbar-nav > li.nav-item > a.nav-link > img ul.navbar-nav > li.nav-item > a.nav-link > img
ul.navbar-nav > li.nav-item > a.nav-link > img ul.navbar-nav > li.nav-item > a.nav-link > img
ul.navbar-nav > li.nav-item > a.nav-link > img ul.navbar-nav > li.nav-item > a.nav-link > img
ul.navbar-nav > li.nav-item > a.nav-link > img ul.navbar-nav > li.nav-item > a.nav-link > img

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
nav.navbar > div.container-fluid > div > a.navbar-brand nav.navbar > div.container-fluid > div > a.navbar-brand
div.container > ul.navbar-nav > li.nav-item > a.nav-link div.container > ul.navbar-nav > li.nav-item > a.nav-link
div.container > ul.navbar-nav > li.nav-item > a.nav-link div.container > ul.navbar-nav > li.nav-item > a.nav-link
div.container > ul.navbar-nav > li.nav-item > a.nav-link div.container > ul.navbar-nav > li.nav-item > a.nav-link
div.container > ul.navbar-nav > li.nav-item > a.nav-link div.container > ul.navbar-nav > li.nav-item > a.nav-link

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
© 2026 Network Time Foundation body > nav.site-footer > div.container > ul.mx-auto

These are opportunities to improve the experience of reading tabular or list data using 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
SUPPORT nav.navbar > div.container-fluid > div > button.btn
SUPPORT div.container-fluid > div > button.btn > a.nav-item
REFERENCE LIBRARY nav.navbar > div.container-fluid > div > button.btn
REFERENCE LIBRARY div.container-fluid > div > button.btn > a.nav-item
DOCUMENTATION nav.navbar > div.container-fluid > div > button.btn
DOCUMENTATION div.container-fluid > div > button.btn > a.nav-item
DONATE nav.navbar > div.container-fluid > div > button.btn
DOWNLOAD NTP body > section.min-vh-100 > button.btn
REPORT A BUG body > section.min-vh-100 > button.btn

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
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
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.
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Heading elements appear in a sequentially-descending order
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
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.
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
Page has valid source maps
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
92

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

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
section.min-vh-100 > div.card > div.card-body > img.figure-img section.min-vh-100 > div.card > div.card-body > img.figure-img
section.min-vh-100 > button.btn > a.btn > img section.min-vh-100 > button.btn > a.btn > img
section.min-vh-100 > button.btn > a.btn > img section.min-vh-100 > button.btn > a.btn > img
ul.navbar-nav > li.nav-item > a.nav-link > img ul.navbar-nav > li.nav-item > a.nav-link > img
ul.navbar-nav > li.nav-item > a.nav-link > img ul.navbar-nav > li.nav-item > a.nav-link > img
ul.navbar-nav > li.nav-item > a.nav-link > img ul.navbar-nav > li.nav-item > a.nav-link > img
ul.navbar-nav > li.nav-item > a.nav-link > img ul.navbar-nav > li.nav-item > a.nav-link > img

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
Document has a meta description
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`

Send Feedback