10.8 sec in total
1.5 sec
8.7 sec
611 ms
Click here to check amazing E MAIL content for Japan. Otherwise, check out these important facts you probably never knew about e-mail.jp
永く使えるメールアドレス、@e-mail.jpを作成する有料メールサービス。500MBのメールボックスを提供。
Visit e-mail.jpWe analyzed E-mail.jp page load time and found that the first response time was 1.5 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
e-mail.jp performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value12.9 s
0/100
25%
Value13.4 s
2/100
10%
Value60 ms
100/100
30%
Value0.036
100/100
15%
Value11.6 s
18/100
10%
1463 ms
63 ms
883 ms
1600 ms
1067 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 63% of them (45 requests) were addressed to the original E-mail.jp, 15% (11 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain E-mail.jp.
Page size can be reduced by 1.8 MB (73%)
2.5 MB
695.4 kB
In fact, the total size of E-mail.jp main page is 2.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. CSS take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 38.5 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 9.0 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 38.5 kB or 83% of the original size.
Potential reduce by 17.3 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. E MAIL images are well optimized though.
Potential reduce by 452.0 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 452.0 kB or 68% of the original size.
Potential reduce by 1.3 MB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. E-mail.jp needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 86% of the original size.
Number of requests can be reduced by 29 (54%)
54
25
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E MAIL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.e-mail.jp
1463 ms
css
63 ms
bootstrap.min.css
883 ms
essentials.css
1600 ms
layout.css
1067 ms
layout-font-rewrite.css
366 ms
header-1.css
368 ms
blue.css
397 ms
footer-white.png
550 ms
header-black.png
548 ms
black-1.png
987 ms
large-01.gif
562 ms
large-02.gif
562 ms
large-03.gif
744 ms
large-04.gif
745 ms
large-05.gif
879 ms
large-07.gif
929 ms
large-08.gif
930 ms
large-09.gif
1011 ms
large-10.gif
1055 ms
large-11.gif
1069 ms
large-12.gif
1114 ms
jquery-2.1.4.min.js
1408 ms
scripts.js
1764 ms
check
1888 ms
1.jpg
580 ms
0096.jpg
421 ms
world-map.png
215 ms
footer_sprite.png
215 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
55 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
64 ms
0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf
118 ms
1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf
153 ms
MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf
154 ms
xkvoNo9fC8O2RDydKj12b8DdSZkkecOE1hvV7ZHvhyU.ttf
153 ms
JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf
153 ms
CcKI4k9un7TZVWzRVT-T88DdSZkkecOE1hvV7ZHvhyU.ttf
153 ms
UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf
152 ms
-_Ctzj9b56b8RgXW8FAricDdSZkkecOE1hvV7ZHvhyU.ttf
153 ms
61V2bQZoWB5DkWAUJStypevvDin1pK8aKteLpeZ5c0A.ttf
153 ms
fontawesome-webfont.woff
209 ms
et-line.woff
483 ms
glyphicons-halflings-regular.woff
294 ms
analytics.js
26 ms
tag.js
9 ms
bootstrap.min.js
876 ms
tag
8 ms
collect
37 ms
collect
57 ms
ga-audiences
90 ms
owl.carousel.min.js
187 ms
jquery.mixitup.min.js
214 ms
jquery.simple-text-rotator.min.js
201 ms
bootstrap.min.css
759 ms
essentials.css
1751 ms
layout.css
1276 ms
layout-font-rewrite.css
680 ms
header-1.css
683 ms
blue.css
710 ms
jquery-2.1.4.min.js
1219 ms
scripts.js
1413 ms
fontawesome-webfont.woff
378 ms
analytics.js
50 ms
tag.js
30 ms
bootstrap.min.js
186 ms
tag
27 ms
collect
9 ms
ya.js
729 ms
ya.js
379 ms
pb.js
578 ms
333 ms
326 ms
e-mail.jp accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
e-mail.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
e-mail.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-mail.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that E-mail.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
e-mail.jp
Open Graph description is not detected on the main page of E MAIL. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: