Alertnet.org Test Results

Alertnet.org Mobile Performance: 27/100
Quick overview:
Time to Interactive
28.3 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.
First Meaningful Paint
9.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Max Potential First Input Delay
790 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.

Alertnet.org Mobile SEO: 93/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.

Alertnet.org Mobile Best Practices: 33/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more about unload event listeners
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Browser errors were logged to the console
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
Uses third-party cookies
3 cookies found
Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.
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.
Alertnet.org 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.
Alertnet.org Mobile Accessibility: 81/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.
Links do not have a discernible name
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.
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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar tests
www.alertnet.com
www.alertnet.net
www.alertnet.org
www.alertnet.info
www.alertnet.biz
www.alertnet.us
www.alertnet.mobi
www.lertnet.org
www.alertnet.org
www.qlertnet.org
www.aqlertnet.org
www.qalertnet.org
www.wlertnet.org
www.awlertnet.org
www.walertnet.org
www.slertnet.org
www.aslertnet.org
www.salertnet.org
www.zlertnet.org
www.azlertnet.org
www.zalertnet.org
www.aertnet.org
www.apertnet.org
www.alpertnet.org
www.aplertnet.org
www.aoertnet.org
www.aloertnet.org
www.aolertnet.org
www.akertnet.org
www.alkertnet.org
www.aklertnet.org
www.alrtnet.org
www.alwrtnet.org
www.alewrtnet.org
www.alwertnet.org
www.alsrtnet.org
www.alesrtnet.org
www.alsertnet.org
www.aldrtnet.org
www.aledrtnet.org
www.aldertnet.org
www.alrrtnet.org
www.alerrtnet.org
www.alrertnet.org
www.aletnet.org
www.aleetnet.org
www.aleretnet.org
www.aleertnet.org
www.aledtnet.org
www.alerdtnet.org
www.aleftnet.org
www.alerftnet.org
www.alefrtnet.org
www.alettnet.org
www.alerttnet.org
www.aletrtnet.org
www.alernet.org
www.alerrnet.org
www.alertrnet.org
www.alerfnet.org
www.alertfnet.org
www.alergnet.org
www.alertgnet.org
www.alergtnet.org
www.alerynet.org
www.alertynet.org
www.alerytnet.org
www.alertet.org
www.alertbet.org
www.alertnbet.org
www.alertbnet.org
www.alerthet.org
www.alertnhet.org
www.alerthnet.org
www.alertjet.org
www.alertnjet.org
www.alertjnet.org
www.alertmet.org
www.alertnmet.org
www.alertmnet.org
www.alertnt.org
www.alertnwt.org
www.alertnewt.org
www.alertnwet.org
www.alertnst.org
www.alertnest.org
www.alertnset.org
www.alertndt.org
www.alertnedt.org
www.alertndet.org
www.alertnrt.org
www.alertnert.org
www.alertnret.org
www.alertne.org
www.alertner.org
www.alertnetr.org
www.alertnef.org
www.alertnetf.org
www.alertneft.org
www.alertneg.org
www.alertnetg.org
www.alertnegt.org
www.alertney.org
www.alertnety.org
www.alertneyt.org
Last Tested: