Nmb.gov Test Results
Nmb.gov Mobile Performance: 77/100
Quick overview:
Time to Interactive
4.5 s
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.
Max Potential First Input Delay
150 ms
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.
First Meaningful Paint
2.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Diagnostics
Collection of useful page vitals.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Server Backend Latencies
300 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Script Treemap Data
Used for treemap app
Metrics
Collects all available metrics.
Network Requests
Lists the network requests that were made during page load.
Final Screenshot
The last screenshot captured of the pageload.
2481720577206
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Nmb.gov Mobile SEO: 85/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Nmb.gov Mobile Best Practices: 77/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Nmb.gov Mobile PWA: 38/100
Quick overview:
PWA Optimized
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons. No manifest was fetched
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more about manifest installability requirements.
Nmb.gov Mobile Accessibility: 94/100
Quick overview:
Names and labels
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Similar sites
Similar tests
www.nmb.com
www.nmb.net
www.nmb.org
www.nmb.info
www.nmb.biz
www.nmb.us
www.nmb.mobi
www.mb.gov
www.nmb.gov
www.bmb.gov
www.nbmb.gov
www.bnmb.gov
www.hmb.gov
www.nhmb.gov
www.hnmb.gov
www.jmb.gov
www.njmb.gov
www.jnmb.gov
www.mmb.gov
www.nmmb.gov
www.mnmb.gov
www.nb.gov
www.nnb.gov
www.nmnb.gov
www.nnmb.gov
www.njb.gov
www.nmjb.gov
www.nkb.gov
www.nmkb.gov
www.nkmb.gov
www.nm.gov
www.nmv.gov
www.nmbv.gov
www.nmvb.gov
www.nmg.gov
www.nmbg.gov
www.nmgb.gov
www.nmh.gov
www.nmbh.gov
www.nmhb.gov
www.nmn.gov
www.nmbn.gov
www.nmb.net
www.nmb.org
www.nmb.info
www.nmb.biz
www.nmb.us
www.nmb.mobi
www.mb.gov
www.nmb.gov
www.bmb.gov
www.nbmb.gov
www.bnmb.gov
www.hmb.gov
www.nhmb.gov
www.hnmb.gov
www.jmb.gov
www.njmb.gov
www.jnmb.gov
www.mmb.gov
www.nmmb.gov
www.mnmb.gov
www.nb.gov
www.nnb.gov
www.nmnb.gov
www.nnmb.gov
www.njb.gov
www.nmjb.gov
www.nkb.gov
www.nmkb.gov
www.nkmb.gov
www.nm.gov
www.nmv.gov
www.nmbv.gov
www.nmvb.gov
www.nmg.gov
www.nmbg.gov
www.nmgb.gov
www.nmh.gov
www.nmbh.gov
www.nmhb.gov
www.nmn.gov
www.nmbn.gov