Safe-mail - Safe-mail.net

Overview

Snoop Summary for safe-mail.net

This is a free and comprehensive report about safe-mail.net. The domain safe-mail.net is currently hosted on a server located in Giv‘atayim, Tel Aviv in Israel with the IP address 212.29.227.81, where ILS is the local currency and the local language is Arabic. Safe-mail.net has the potential to be earning an estimated $6 USD per day from advertising revenue. If safe-mail.net was to be sold it would possibly be worth $4,697 USD (based on the daily revenue potential of the website over a 24 month period). Safe-mail.net is quite popular with an estimated 2,253 daily unique visitors. This report was last updated 8th May, 2021.

About safe-mail.net

Site Preview:
Title:	Safe-mail.net
Description:	A free high security web-based e-mail system. Also offers the ability to start your own bulletin boards, an individual authentication facility and live chat.
Keywords and Tags:	web mail
Related Terms:	2 factor authentication, abp nl mail, hkt48 mail, intrinsically safe, is nicaragua safe, krypterad mail, myfastpage mail, owa mail, redid mail, saml authentication
Fav Icon:
Age:	Over 25 years old
Domain Created:	10th October, 1998
Domain Updated:	7th February, 2018
Domain Expires:	9th October, 2022

Review

Snoop Score

3/5 (Great!)

Valuation

$4,697 USD

Note: All valuation figures are estimates.

Popularity

Modest

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	226,733
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	0
Moz Page Authority:	0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	2,253
Monthly Visitors:	68,574
Yearly Visitors:	822,345

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$6 USD
Monthly Revenue:	$195 USD
Yearly Revenue:	$2,344 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	safe-mail.net	13
Domain Name:	safe-mail	9
Extension (TLD):	net	3

Expiry Check:

Page Speed Analysis

Average Load Time:	1.23 seconds
Load Time Comparison:	Faster than 70% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: http://safe-mail.net/

Updated: 8th May, 2021

1.45 seconds

First Contentful Paint (FCP)

65%

29%

6%

0.00 seconds

First Input Delay (FID)

100%

0%

Simulate loading on desktop

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for safe-mail.net. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.2 s
The time taken for the first image or text on the page to be rendered.

Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.

Largest Contentful Paint — 0.2 s
The timing of the largest text or image that is painted.

Time to Interactive — 0.2 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 0.2 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

First Meaningful Paint — 0.2 s
The time taken for the primary content of the page to be rendered.

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive safe-mail.net as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://safe-mail.net/	http/1.1	0	467.34400000423	13360	13039	200	text/html	Document
http://safe-mail.net/ui/default/tab.gif	http/1.1	485.04900000989	791.91100003663	345	43	200	image/gif	Image
http://safe-mail.net/ui/login/4/Welcome.gif	http/1.1	485.28799996711	956.95399993565	878	574	200	image/gif	Image
http://safe-mail.net/ui/login/4/Logo-5.jpg	http/1.1	488.72000002302	942.88200000301	9842	9535	200	image/jpeg	Image
http://safe-mail.net/ui/login/4/point-off.gif	http/1.1	488.98499994539	805.29499996919	584	281	200	image/gif	Image
http://safe-mail.net/ui/login/4/LoginFor.gif	http/1.1	489.26299996674	967.29599998798	1218	914	200	image/gif	Image
http://safe-mail.net/ui/login/4/Regist.gif	http/1.1	489.47699996643	1003.040999989	925	621	200	image/gif	Image
http://safe-mail.net/ui/login/4/QuickMail.gif	http/1.1	489.90799998865	971.09599993564	759	455	200	image/gif	Image
http://safe-mail.net/ui/login/4/WhatIsSafe-mail.gif	http/1.1	490.0970000308	977.76299994439	1092	788	200	image/gif	Image
http://safe-mail.net/ui/login/4/symphony.gif	http/1.1	490.35899993032	971.44100000151	784	480	200	image/gif	Image
http://safe-mail.net/ui/login/4/PremiumServices.gif	http/1.1	490.47399999108	945.32199995592	974	670	200	image/gif	Image
http://safe-mail.net/ui/login/4/Support.gif	http/1.1	490.59699999634	981.15699994378	702	398	200	image/gif	Image
http://safe-mail.net/ui/login/4/Documents.gif	http/1.1	490.76199997216	1209.5940000145	517	214	200	image/gif	Image
http://safe-mail.net/ui/login/4/point-on1.gif	http/1.1	490.98000000231	950.70099993609	917	613	200	image/gif	Image
http://safe-mail.net/ui/login/4/point-on.gif	http/1.1	491.13600002602	946.56800001394	585	281	200	image/gif	Image
http://safe-mail.net/ui/login/4/bg.gif	http/1.1	493.92199993599	977.46199998073	696	392	200	image/gif	Image
http://safe-mail.net/ui/login/4/hive.gif	http/1.1	494.1819999367	941.84799992945	525	222	200	image/gif	Image

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
502.474	10.444
515.244	8.04
523.323	21.955

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Safe-mail.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

Properly size images
Images can slow down the page's load time. Safe-mail.net should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Safe-mail.net should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Safe-mail.net should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Safe-mail.net should consider minifying JS files.

Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Safe-mail.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression — Potential savings of 9 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
http://safe-mail.net/	13039	9346

Show Details

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Initial server response time was short — Root document took 470 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
http://safe-mail.net/	468.308

Show Details

Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Safe-mail.net should avoid multiple or unnecessary page redirects.

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Safe-mail.net should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 34 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
http://safe-mail.net/	13360
http://safe-mail.net/ui/login/4/Logo-5.jpg	9842
http://safe-mail.net/ui/login/4/LoginFor.gif	1218
http://safe-mail.net/ui/login/4/WhatIsSafe-mail.gif	1092
http://safe-mail.net/ui/login/4/PremiumServices.gif	974
http://safe-mail.net/ui/login/4/Regist.gif	925
http://safe-mail.net/ui/login/4/point-on1.gif	917
http://safe-mail.net/ui/login/4/Welcome.gif	878
http://safe-mail.net/ui/login/4/symphony.gif	784
http://safe-mail.net/ui/login/4/QuickMail.gif	759

Show Details

Uses efficient cache policy on static assets — 16 resources found
Safe-mail.net can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Transfer Size (Bytes)
http://safe-mail.net/ui/login/4/Logo-5.jpg	0	9842
http://safe-mail.net/ui/login/4/LoginFor.gif	0	1218
http://safe-mail.net/ui/login/4/WhatIsSafe-mail.gif	0	1092
http://safe-mail.net/ui/login/4/PremiumServices.gif	0	974
http://safe-mail.net/ui/login/4/Regist.gif	0	925
http://safe-mail.net/ui/login/4/point-on1.gif	0	917
http://safe-mail.net/ui/login/4/Welcome.gif	0	878
http://safe-mail.net/ui/login/4/symphony.gif	0	784
http://safe-mail.net/ui/login/4/QuickMail.gif	0	759
http://safe-mail.net/ui/login/4/Support.gif	0	702
http://safe-mail.net/ui/login/4/bg.gif	0	696
http://safe-mail.net/ui/login/4/point-on.gif	0	585
http://safe-mail.net/ui/login/4/point-off.gif	0	584
http://safe-mail.net/ui/login/4/hive.gif	0	525
http://safe-mail.net/ui/login/4/Documents.gif	0	517
http://safe-mail.net/ui/default/tab.gif	0	345

Show Details

Avoids an excessive DOM size — 146 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		146
Maximum DOM Depth	Safe-mail is designed to provide maximum security and privacy without any compl…	19
Maximum Child Elements	please ignore messages from bogus Safe-mail.net address. Safe-mail.net users m…	12

Show Details

Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Safe-mail.net should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
http://safe-mail.net/	57.435	3.954	1.829

Show Details

Minimizes main-thread work — 0.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Other	30.462
Style & Layout	23.103
Rendering	10.891
Parse HTML & CSS	6.859
Script Evaluation	5.006
Script Parsing & Compilation	1.965

Show Details

All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

Keep request counts low and transfer sizes small — 17 requests • 34 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	17	34703
Image	16	21343
Document	1	13360
Stylesheet	0	0
Media	0	0
Font	0	0
Script	0	0
Other	0	0
Third-party	0	0

Show Details

Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
Change of terms Free registration is now restricted to 3 month. Also there is …

Show Details

Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.

Element	CLS Contribution
Change of terms Free registration is now restricted to 3 month. Also there is …	0.13200197608679
td	0.016412818618689
Safe-mail is designed to provide maximum security and privacy without any c…	0.013032593281455
td	0.0097182228353102
	0.0016404662871761

Show Details

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Diagnostics

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

URL	Failing Elements
http://safe-mail.net/ui/login/4/Logo-5.jpg	img
http://safe-mail.net/ui/login/4/LoginFor.gif	Login for Existing Users
http://safe-mail.net/ui/login/4/WhatIsSafe-mail.gif	What Is Safe-mail
http://safe-mail.net/ui/login/4/PremiumServices.gif	Premium Packages
http://safe-mail.net/ui/login/4/Regist.gif	Free Registration
http://safe-mail.net/ui/login/4/Welcome.gif	img
http://safe-mail.net/ui/login/4/symphony.gif	symphony
http://safe-mail.net/ui/login/4/QuickMail.gif	Quick Mail
http://safe-mail.net/ui/login/4/Support.gif	Support and help
http://safe-mail.net/ui/login/4/point-off.gif	img
http://safe-mail.net/ui/login/4/point-off.gif	img
http://safe-mail.net/ui/login/4/point-off.gif	img
http://safe-mail.net/ui/login/4/point-off.gif	img
http://safe-mail.net/ui/login/4/point-off.gif	img
http://safe-mail.net/ui/login/4/point-off.gif	img
http://safe-mail.net/ui/login/4/point-off.gif	img
http://safe-mail.net/ui/login/4/point-off.gif	img
http://safe-mail.net/ui/login/4/Documents.gif	Documents
http://safe-mail.net/ui/default/tab.gif	img

Show Details

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of safe-mail.net. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.

Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Safe-mail.net may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Show Details

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

Failing Elements
html

Show Details

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img

Show Details

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Failing Elements
a

Show Details

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.

Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.

The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.

User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.

Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.

Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.

Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.

HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that safe-mail.net should incorporate. This includes practices such as protecting pages with HTTPS.

Passing (14)
Failing (4)

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 17 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL	Request Resolution
http://safe-mail.net/	Allowed
http://safe-mail.net/ui/default/tab.gif	Allowed
http://safe-mail.net/ui/login/4/Welcome.gif	Allowed
http://safe-mail.net/ui/login/4/Logo-5.jpg	Allowed
http://safe-mail.net/ui/login/4/point-off.gif	Allowed
http://safe-mail.net/ui/login/4/LoginFor.gif	Allowed
http://safe-mail.net/ui/login/4/Regist.gif	Allowed
http://safe-mail.net/ui/login/4/QuickMail.gif	Allowed
http://safe-mail.net/ui/login/4/WhatIsSafe-mail.gif	Allowed
http://safe-mail.net/ui/login/4/symphony.gif	Allowed
http://safe-mail.net/ui/login/4/PremiumServices.gif	Allowed
http://safe-mail.net/ui/login/4/Support.gif	Allowed
http://safe-mail.net/ui/login/4/Documents.gif	Allowed
http://safe-mail.net/ui/login/4/point-on1.gif	Allowed
http://safe-mail.net/ui/login/4/point-on.gif	Allowed
http://safe-mail.net/ui/login/4/bg.gif	Allowed
http://safe-mail.net/ui/login/4/hive.gif	Allowed

Show Details

Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Failing Anchors
a

Show Details

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

URL	Displayed size	Actual size	Expected size
http://safe-mail.net/ui/default/tab.gif	19 x 19	1 x 1	19 x 19

Show Details

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for safe-mail.net. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of safe-mail.net on mobile screens.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img

Show Details

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of safe-mail.net. This includes details about web app manifests.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

Failure reason
No manifest was fetched

Show Details

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of safe-mail.net on mobile screens.

Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: http://safe-mail.net/

Updated: 8th May, 2021

1.09 seconds

First Contentful Paint (FCP)

74%

24%

2%

0.24 seconds

First Input Delay (FID)

3%

96%

1%

Simulate loading on mobile

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for safe-mail.net. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.

Speed Index — 2.6 s
The time taken for the page contents to be visibly populated.

Largest Contentful Paint — 0.7 s
The timing of the largest text or image that is painted.

Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 0.7 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive safe-mail.net as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://safe-mail.net/	http/1.1	0	326.03400014341	13360	13039	200	text/html	Document
http://safe-mail.net/ui/default/tab.gif	http/1.1	342.09499973804	664.87799957395	345	43	200	image/gif	Image
http://safe-mail.net/ui/login/4/Welcome.gif	http/1.1	342.28600002825	502.85500008613	877	574	200	image/gif	Image
http://safe-mail.net/ui/login/4/Logo-5.jpg	http/1.1	345.2309994027	641.07999950647	9842	9535	200	image/jpeg	Image
http://safe-mail.net/ui/login/4/point-off.gif	http/1.1	345.45500017703	677.36199963838	584	281	200	image/gif	Image
http://safe-mail.net/ui/login/4/LoginFor.gif	http/1.1	345.7929994911	1890.0830000639	1218	914	200	image/gif	Image
http://safe-mail.net/ui/login/4/Regist.gif	http/1.1	345.97400017083	643.69099959731	925	621	200	image/gif	Image
http://safe-mail.net/ui/login/4/QuickMail.gif	http/1.1	346.36199939996	640.61499945819	759	455	200	image/gif	Image
http://safe-mail.net/ui/login/4/WhatIsSafe-mail.gif	http/1.1	346.54300007969	652.0499996841	1092	788	200	image/gif	Image
http://safe-mail.net/ui/login/4/symphony.gif	http/1.1	346.71400021762	637.92299944907	784	480	200	image/gif	Image
http://safe-mail.net/ui/login/4/PremiumServices.gif	http/1.1	346.87799960375	653.28099951148	974	670	200	image/gif	Image
http://safe-mail.net/ui/login/4/Support.gif	http/1.1	347.04300016165	660.83899978548	702	398	200	image/gif	Image
http://safe-mail.net/ui/login/4/Documents.gif	http/1.1	347.47199993581	2841.1389999092	517	214	200	image/gif	Image
http://safe-mail.net/ui/login/4/point-on1.gif	http/1.1	347.72399999201	651.58399939537	917	613	200	image/gif	Image
http://safe-mail.net/ui/login/4/point-on.gif	http/1.1	347.8919994086	665.84599949419	585	281	200	image/gif	Image
http://safe-mail.net/ui/login/4/bg.gif	http/1.1	350.82899965346	2222.0709994435	696	392	200	image/gif	Image
http://safe-mail.net/ui/login/4/hive.gif	http/1.1	351.14500019699	2862.6239998266	525	222	200	image/gif	Image

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
363.39	9.617
374.863	8.458
383.339	18.89

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

First Contentful Paint (3G) — 1302 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.