myfreemail.net

myfreemail.net is SSL secured

Free website and domain report on myfreemail.net

Last Updated: 19th April, 2024
Overview

Snoop Summary for myfreemail.net

This is a free and comprehensive report about myfreemail.net. Our records indicate that myfreemail.net is privately registered by Your Whois Privacy Ltd. If myfreemail.net was to be sold it would possibly be worth $77 USD (based on the daily revenue potential of the website over a 24 month period). Myfreemail.net is slightly popular with an estimated 32 daily unique visitors. This report was last updated 19th April, 2024.

About myfreemail.net

Site Preview: myfreemail.net myfreemail.net
Title: MyFreeMail
Description:
Keywords and Tags: business
Related Terms:
Fav Icon:
Age: Over 10 years old
Domain Created: 14th March, 2014
Domain Updated: 15th March, 2024
Domain Expires: 14th March, 2025
Review

Snoop Score

1/5

Valuation

$77 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 9,425,897
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: 32
Monthly Visitors: 974
Yearly Visitors: 11,680
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $3 USD
Yearly Revenue: $33 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: myfreemail.net 14
Domain Name: myfreemail 10
Extension (TLD): net 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 73
Performance 96
Accessibility 91
Best Practices 75
SEO 80
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
96

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 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).
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
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://myfreemail.net/
http/1.1
0
239.65600004885
351
0
302
text/html
https://www.myfreemail.net/
http/1.1
239.97500003316
1088.1369999843
4459
4176
200
text/html
Document
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
http/1.1
1096.5149999829
1929.1090000188
12120
11785
200
text/css
Stylesheet
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
http/1.1
1096.8880000291
2193.797999993
97512
97162
200
application/javascript
Script
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
http/1.1
1096.9899999909
2101.069000084
56565
56216
200
application/javascript
Script
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
http/1.1
2230.4030000232
2816.0560000688
72544
72206
200
image/jpeg
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/myfreemailnet-logo.png
http/1.1
2230.6129999924
2716.688000015
10851
10515
200
image/png
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-mail.png
http/1.1
2231.7899999907
3004.6720000682
1580
1246
200
image/png
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-pass.png
http/1.1
2236.067000078
2716.1750000669
1543
1209
200
image/png
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/arrow.png
http/1.1
2237.0450000744
3010.1840000134
1320
987
200
image/png
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/dot.png
http/1.1
2237.9750000546
3057.8049999895
1318
985
200
image/png
Image
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)
1093.276
11.095
2204.03
18.803
2222.866
5.771
2228.647
23.349
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Myfreemail.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Myfreemail.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Myfreemail.net should consider minifying CSS files.
Minify JavaScript — Potential savings of 26 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Myfreemail.net should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56565
26265
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Myfreemail.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 97 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
97512
63536
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56565
35990
Efficiently encode images — Potential savings of 36 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
72206
36944
Serve images in next-gen formats — Potential savings of 59 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
72206
60193.7
Enable text compression — Potential savings of 119 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
97162
63370
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56216
46053
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
11785
9332
https://www.myfreemail.net/
4176
2693
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Myfreemail.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://myfreemail.net/
190
https://www.myfreemail.net/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Myfreemail.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 — Potential savings of 30 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
30
Avoids enormous network payloads — Total size was 254 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
97512
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
72544
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56565
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
12120
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/myfreemailnet-logo.png
10851
https://www.myfreemail.net/
4459
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-mail.png
1580
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-pass.png
1543
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/arrow.png
1320
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/dot.png
1318
Avoids an excessive DOM size — 42 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
42
Maximum DOM Depth
9
Maximum Child Elements
5
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Myfreemail.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
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.
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)
Script Evaluation
30.489
Other
25.01
Style & Layout
17.424
Rendering
6.162
Script Parsing & Compilation
5.231
Parse HTML & CSS
3.722
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 — 11 requests • 254 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
11
260163
Script
2
154077
Image
6
89156
Stylesheet
1
12120
Document
1
4459
Other
1
351
Media
0
0
Font
0
0
Third-party
0
0
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of myfreemail.net on mobile screens.
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.

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.

Metrics

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

Other

Eliminate render-blocking resources — Potential savings of 360 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Myfreemail.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
12120
70
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
97512
310
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56565
230

Other

Reduce initial server response time — Root document took 850 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)
https://www.myfreemail.net/
849.156
Serve static assets with an efficient cache policy — 9 resources found
Myfreemail.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)
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
0
97512
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
0
72544
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
0
56565
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
0
12120
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/myfreemailnet-logo.png
0
10851
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-mail.png
0
1580
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-pass.png
0
1543
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/arrow.png
0
1320
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/dot.png
0
1318
91

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of myfreemail.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.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<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.
Links 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.
`<object>` elements have alternate 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.

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"]`
Myfreemail.net may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

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

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.
75

Best Practices

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

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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel 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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
>= 2.0.0 & <= 2.3.2
jQuery
1.12.4
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 — 1 insecure request 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://myfreemail.net/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

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

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of myfreemail.net on mobile screens.
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.

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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
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.

Content Best Practices

Document does not have 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.

Crawling and Indexing

Page is 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.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of myfreemail.net on mobile screens.

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

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.
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 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) 72
Performance 89
Accessibility 91
Best Practices 75
SEO 83
PWA 20
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.myfreemail.net/
Updated: 2nd November, 2022
Simulate loading on mobile
89

Performance

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

Metrics

Time to Interactive — 2.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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
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://myfreemail.net/
http/1.1
0
245.31699996442
351
0
302
text/html
https://www.myfreemail.net/
http/1.1
245.66299992148
763.45899992157
4459
4176
200
text/html
Document
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
http/1.1
775.56300000288
1267.4829999451
12120
11785
200
text/css
Stylesheet
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
http/1.1
777.46399992611
1362.5479999464
97512
97162
200
application/javascript
Script
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
http/1.1
777.64899993781
1456.6179999383
56565
56216
200
application/javascript
Script
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
http/1.1
1467.2639999771
2439.973999979
72544
72206
200
image/jpeg
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/myfreemailnet-logo.png
http/1.1
1467.4409999279
2248.3389999252
10851
10515
200
image/png
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-mail.png
http/1.1
1468.3849998983
1952.8979999013
1580
1246
200
image/png
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-pass.png
http/1.1
1472.0429999288
1952.3029999109
1543
1209
200
image/png
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/arrow.png
http/1.1
1473.1829999946
2245.0170000084
1320
987
200
image/png
Image
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/dot.png
http/1.1
1473.3530000085
2252.3250000086
1318
985
200
image/png
Image
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)
768.664
12.747
1373.503
19.134
1466.888
20.375
1487.276
8.494
1956.569
8.221
2382.825
5.441
2442.008
17.927
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Myfreemail.net should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Myfreemail.net should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Myfreemail.net should consider minifying CSS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Myfreemail.net should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
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 520 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)
https://www.myfreemail.net/
518.784
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Myfreemail.net should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://myfreemail.net/
630
https://www.myfreemail.net/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Myfreemail.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.
Avoids enormous network payloads — Total size was 254 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
97512
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
72544
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56565
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
12120
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/myfreemailnet-logo.png
10851
https://www.myfreemail.net/
4459
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-mail.png
1580
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-pass.png
1543
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/arrow.png
1320
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/dot.png
1318
Avoids an excessive DOM size — 42 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
42
Maximum DOM Depth
9
Maximum Child Elements
5
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Myfreemail.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.2 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)
https://www.myfreemail.net/
213.516
17.484
7.936
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
181.952
109.744
8.86
Unattributable
94.576
7.316
0
Minimizes main-thread work — 0.5 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
198.192
Script Evaluation
142.424
Rendering
69.648
Style & Layout
63.188
Script Parsing & Compilation
22.672
Parse HTML & CSS
13.52
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 — 11 requests • 254 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
11
260163
Script
2
154077
Image
6
89156
Stylesheet
1
12120
Document
1
4459
Other
1
351
Media
0
0
Font
0
0
Third-party
0
0
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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 — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
2220
77
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
2297
72
https://www.myfreemail.net/
1410
51
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of myfreemail.net on mobile screens.
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.

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.

Metrics

First Contentful Paint — 2.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 4.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.7 s
The timing of the largest text or image that is painted.

Audits

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

Other

Minify JavaScript — Potential savings of 26 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Myfreemail.net should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56565
26265
Reduce unused JavaScript — Potential savings of 97 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
97512
63536
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56565
35990
Efficiently encode images — Potential savings of 36 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
72206
36944
Serve images in next-gen formats — Potential savings of 59 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
72206
60193.7
Enable text compression — Potential savings of 119 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
97162
63370
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56216
46053
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
11785
9332
https://www.myfreemail.net/
4176
2692

Other

Eliminate render-blocking resources — Potential savings of 1,200 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Myfreemail.net should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
12120
180
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
97512
630
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
56565
480
Serve static assets with an efficient cache policy — 9 resources found
Myfreemail.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)
https://www.myfreemail.net/assets/2d95c7d8/jquery.min.js
0
97512
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/background.jpg
0
72544
https://www.myfreemail.net/assets/7c9471e7/js/bootstrap.js
0
56565
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/mailService.css
0
12120
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/myfreemailnet-logo.png
0
10851
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-mail.png
0
1580
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/icon-pass.png
0
1543
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/arrow.png
0
1320
https://www.myfreemail.net/themes/mailService/mfm/sass/stylesheets/images/dot.png
0
1318
First Contentful Paint (3G) — 5550 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
91

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of myfreemail.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.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<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.
Links 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.
`<object>` elements have alternate 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.

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"]`
Myfreemail.net may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

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

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.
75

Best Practices

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

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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel 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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
>= 2.0.0 & <= 2.3.2
jQuery
1.12.4
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 — 1 insecure request 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://myfreemail.net/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
4
Medium

Audits

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

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of myfreemail.net on mobile screens.
Document uses legible font sizes — 100% legible text
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.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
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.

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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
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.

Content Best Practices

Document does not have 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.

Crawling and Indexing

Page is 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.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
20

PWA

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

PWA Optimized

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

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

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.
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
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for 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.
Hosting

Server Location

Server IP Address: 54.75.169.70
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Amazon Technologies Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Your Whois Privacy Ltd
Organization:
Country: GB
City: Milton Keynes
State: Bucks
Post Code: MK14 6LS
Email: domains@yourwhoisprivacy.com
Phone: +44.1908200022
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Safenames Ltd 45.223.58.112
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.myfreemail.net
Issued By: Amazon RSA 2048 M02
Valid From: 6th December, 2023
Valid To: 3rd January, 2025
Subject: CN = *.myfreemail.net
Hash: 038dcf98
Issuer: CN = Amazon RSA 2048 M02
O = Amazon
S = US
Version: 2
Serial Number: 18280016912883825908104886079384944502
Serial Number (Hex): 0DC09A6B0796F2F4E89EFA865AEF7F76
Valid From: 6th December, 2024
Valid To: 3rd January, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:C0:31:52:CD:5A:50:C3:82:7C:74:71:CE:CB:E9:9C:F9:7A:EB:82:E2
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.r2m02.amazontrust.com/r2m02.crl

Certificate Policies: Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://ocsp.r2m02.amazontrust.com
CA Issuers - URI:http://crt.r2m02.amazontrust.com/r2m02.cer

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
Timestamp : Dec 6 00:33:03.370 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:21:B4:19:53:4A:82:CE:15:25:C0:16:EC:
C5:97:66:43:79:99:5D:AB:C4:74:DA:23:C9:EA:80:B4:
A3:56:7F:A1:02:21:00:C6:61:D6:9A:7E:31:9C:94:08:
4E:15:A0:DF:9F:97:88:C4:86:FE:73:5E:CA:36:2E:7C:
B7:6B:16:C8:9D:47:C6
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
Timestamp : Dec 6 00:33:03.456 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:68:A9:69:A4:74:56:B6:69:2E:D5:75:EA:
D5:F0:E3:E5:FA:E9:7A:FD:EC:44:8C:E5:13:0E:51:FC:
B8:B6:4B:BA:02:20:49:60:1F:3A:8A:C5:3C:46:1C:CA:
DB:DD:37:A5:C3:2E:96:E4:24:46:5F:F3:04:AF:8E:E9:
D7:A3:07:7D:2C:F2
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
Timestamp : Dec 6 00:33:03.429 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:68:92:23:FF:EC:5B:66:7E:CF:A5:FC:38:
C6:42:EA:F4:74:97:BD:3C:18:91:AB:5E:E9:62:5F:7B:
27:FE:5B:5F:02:20:78:65:10:97:E8:5B:F2:51:02:60:
84:0A:58:0F:94:8D:11:2A:FC:0A:57:B4:B8:D4:71:0C:
1F:6D:47:AB:F9:E8
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:myfreemail.net
DNS:*.myfreemail.net
Technical

DNS Lookup

A Records

Host IP Address Class TTL
myfreemail.net. 54.229.5.20 IN 60
myfreemail.net. 54.75.169.70 IN 60

NS Records

Host Nameserver Class TTL
myfreemail.net. ns-1442.awsdns-52.org. IN 21600
myfreemail.net. ns-1748.awsdns-26.co.uk. IN 21600
myfreemail.net. ns-357.awsdns-44.com. IN 21600
myfreemail.net. ns-591.awsdns-09.net. IN 21600

MX Records

Priority Host Server Class TTL
10 myfreemail.net. inbound-smtp.eu-west-1.amazonaws.com. IN 300

SOA Records

Domain Name Primary NS Responsible Email TTL
myfreemail.net. ns-1442.awsdns-52.org. awsdns-hostmaster.amazon.com. 900

TXT Records

Host Value Class TTL
myfreemail.net. v=spf1 IN 300

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 19th April, 2024
Content-Type: text/html; charset=UTF-8
Server: nginx
Connection: keep-alive
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block

Whois Lookup

Created: 14th March, 2014
Changed: 15th March, 2024
Expires: 14th March, 2025
Registrar: Safenames Ltd
Status: ok
Nameservers: ns-1442.awsdns-52.org
ns-1748.awsdns-26.co.uk
ns-357.awsdns-44.com
ns-591.awsdns-09.net
Owner Name: Your Whois Privacy Ltd
Owner Street: Safenames House
Sunrise Parkway, Linford Wood
Owner Post Code: MK14 6LS
Owner City: Milton Keynes
Owner State: Bucks
Owner Country: GB
Owner Phone: +44.1908200022
Owner Email: domains@yourwhoisprivacy.com
Admin Name: Your Whois Privacy
Admin Street: PO Box 5085
Admin Post Code: MK6 3ZE
Admin City: Milton Keynes MLO
Admin Country: GB
Admin Phone: +44.1908200022
Admin Email: domains@yourwhoisprivacy.com
Tech Name: Your Whois Privacy
Tech Street: PO Box 5085
Tech Post Code: MK6 3ZE
Tech City: Milton Keynes MLO
Tech Country: GB
Tech Phone: +44.1908200022
Tech Email: domains@yourwhoisprivacy.com
Full Whois: Domain Name: MYFREEMAIL.NET
Registry Domain ID: 1850468220_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.safenames.net
Registrar URL: http://www.safenames.net
Updated Date: 2024-03-15T00:54:49Z
Creation Date: 2014-03-14T15:44:00Z
Registrar Registration Expiration Date: 2025-03-14T15:44:00Z
Registrar: Safenames Ltd
Registrar IANA ID: 447
Registrar Abuse Contact Email: abuse@safenames.net
Registrar Abuse Contact Phone: +44.1908200022
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: Not Available From Registry
Registrant Name: Your Whois Privacy Ltd
Registrant Organisation: Your Whois Privacy Ltd
Registrant Street: Safenames House
Registrant Street: Sunrise Parkway, Linford Wood
Registrant City: Milton Keynes
Registrant State/Province: Bucks
Registrant Postal Code: MK14 6LS
Registrant Country: GB
Registrant Phone: +44.1908200022
Registrant Fax: +44.1908325192
Registrant Email: domains@yourwhoisprivacy.com
Registry Admin ID: Not Available From Registry
Admin Name: Your Whois Privacy
Admin Organisation: Your Whois Privacy Ltd
Admin Street: PO Box 5085
Admin Street:
Admin City: Milton Keynes MLO
Admin State/Province:
Admin Postal Code: MK6 3ZE
Admin Country: GB
Admin Phone: +44.1908200022
Admin Fax:
Admin Email: domains@yourwhoisprivacy.com
Registry Tech ID: Not Available From Registry
Tech Name: Your Whois Privacy
Tech Organisation: Your Whois Privacy Ltd
Tech Street: PO Box 5085
Tech Street:
Tech City: Milton Keynes MLO
Tech State/Province:
Tech Postal Code: MK6 3ZE
Tech Country: GB
Tech Phone: +44.1908200022
Tech Fax:
Tech Email: domains@yourwhoisprivacy.com
Name Server: ns-1442.awsdns-52.org
Name Server: ns-1748.awsdns-26.co.uk
Name Server: ns-357.awsdns-44.com
Name Server: ns-591.awsdns-09.net
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-03-15T00:54:49Z <<<

"For more information on Whois status codes, please visit https://icann.org/epp"

Safenames - Experts in Global Domain Management and Online Brand Protection

Domain Registration in over 1400 different extensions
Enterprise Domain Management since 1999
Mark Protect™ Online Brand Monitoring and Enforcement
Domain Consulting and Strategy
Domain Name Acquisition
Domain Disputes and Recovery

Visit Safenames at www.safenames.net
+1 703 574 5313 in the US/Canada
+44 1908 200022 in Europe

The Data in the Safenames Registrar WHOIS database is provided by Safenames for
information purposes only, and to assist persons in obtaining information about
or related to a domain name registration record. Safenames does not guarantee
its accuracy. Additionally, the data may not reflect updates to billing
contact information.

By submitting a WHOIS query, you agree to use this Data only for lawful purposes
and that under no circumstances will you use this Data to:

(1) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via e-mail, telephone, or facsimile; or
(2) enable high volume, automated, electronic processes that apply to Safenames
(or its computer systems). The compilation, repackaging, dissemination or
other use of this Data is expressly prohibited without the prior written
consent of Safenames. Safenames reserves the right to terminate your access to
the Safenames Registrar WHOIS database in its sole discretion, including
without limitation, for excessive querying of the WHOIS database or for failure
to otherwise abide by this policy. Safenames reserves the right to modify
these terms at any time. By submitting this query, you agree to abide by this
policy.


Nameservers

Name IP Address
ns-1442.awsdns-52.org 205.251.197.162
ns-1748.awsdns-26.co.uk 205.251.198.212
ns-357.awsdns-44.com 205.251.193.101
ns-591.awsdns-09.net 205.251.194.79
Related

Subdomains

Domain Subdomain
sara2cool

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address