Inee.org Site Title

Hello | INEE

Inee.org Meta Description

Our goal is to ensure quality, safe, and relevant education for all persons affected by emergencies.

Inee.org Test Results

Inee.org Desktop Performance: 94/100
Quick overview:
First Meaningful Paint
1.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Metrics
Collects all available metrics.
Final Screenshot
The last screenshot captured of the pageload.

1056063305778

Script Treemap Data
Used for treemap app
Tasks
Lists the toplevel main thread tasks that executed during page load.
Network Requests
Lists the network requests that were made during page load.
Diagnostics
Collection of useful page vitals.
Server Backend Latencies
220 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.
Network Round Trip Times
10 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.

Inee.org Desktop SEO: 83/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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Inee.org Desktop Best Practices: 73/100
Quick overview:
General
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.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
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
Inee.org Desktop PWA: 71/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: Manifest does not have `name`.
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.
Inee.org Desktop Accessibility: 91/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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
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.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Touch targets have sufficient size and spacing.
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.
Similar sites
Similar tests
www.inee.com
www.inee.net
www.inee.org
www.inee.info
www.inee.biz
www.inee.us
www.inee.mobi
www.nee.org
www.inee.org
www.unee.org
www.iunee.org
www.uinee.org
www.jnee.org
www.ijnee.org
www.jinee.org
www.knee.org
www.iknee.org
www.kinee.org
www.onee.org
www.ionee.org
www.oinee.org
www.iee.org
www.ibee.org
www.inbee.org
www.ibnee.org
www.ihee.org
www.inhee.org
www.ihnee.org
www.ijee.org
www.injee.org
www.imee.org
www.inmee.org
www.imnee.org
www.ine.org
www.inwe.org
www.inewe.org
www.inwee.org
www.inse.org
www.inese.org
www.insee.org
www.inde.org
www.inede.org
www.indee.org
www.inre.org
www.inere.org
www.inree.org
www.inew.org
www.ineew.org
www.ines.org
www.inees.org
www.ined.org
www.ineed.org
www.iner.org
www.ineer.org
Last Tested: