Tools & Wizards About Us
46mail.net screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

46mail.net

お気に入りのメルマガを迷惑メールフォルダーに入れない方法

Page Load Speed

23.3 sec in total

First Response

920 ms

Resources Loaded

22.1 sec

Page Rendered

271 ms

46mail.net screenshot

About Website

Welcome to 46mail.net homepage info - get ready to check 46 Mail best content for Japan right away, or after learning these important things about 46mail.net

お気に入りのメルマガや友だちからのメールを迷惑メールフォルダーに入れずに受信トレイに届かせる方法を各メールサービス、メールソフトごとに図解で紹介しているサイトです

Visit 46mail.net

Key Findings

We analyzed 46mail.net page load time and found that the first response time was 920 ms and then it took 22.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

46mail.net performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

46mail.net

920 ms

import.css

330 ms

jsapi

6 ms

rollover.js

370 ms

ez_so2css.php

189 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 45% of them (39 requests) were addressed to the original 46mail.net, 8% (7 requests) were made to Atoutts.sparkarea.com and 7% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Wj.ax.xrea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.8 kB (33%)

Content Size

354.1 kB

After Optimization

236.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 46mail.net main page is 354.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 269.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 33.8 kB

  • Original 43.6 kB
  • After minification 41.6 kB
  • After compression 9.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 33.8 kB or 78% of the original size.

Image Optimization

-22%

Potential reduce by 1.3 kB

  • Original 5.9 kB
  • After minification 4.6 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. Obviously, 46 Mail needs image optimization as it can save up to 1.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 53.0 kB

  • Original 269.5 kB
  • After minification 267.1 kB
  • After compression 216.6 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 53.0 kB or 20% of the original size.

CSS Optimization

-85%

Potential reduce by 29.7 kB

  • Original 35.1 kB
  • After minification 22.5 kB
  • After compression 5.4 kB

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. 46mail.net needs all CSS files to be minified and compressed as it can save up to 29.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (49%)

Requests Now

71

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 46 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 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

46mail.net

46mail.net

920 ms

import.css

import.css

330 ms

jsapi

jsapi

6 ms

rollover.js

rollover.js

370 ms

ez_so2css.php

ez_so2css.php

189 ms

jquery.js

jquery.js

189 ms

jquery.plugin.min.js

jquery.plugin.min.js

189 ms

jquery.cookie.js

jquery.cookie.js

189 ms

hgscripttmer.js

hgscripttmer.js

189 ms

jquery.scrolldepth.min.js

jquery.scrolldepth.min.js

189 ms

ez_so2.php

ez_so2.php

188 ms

bookmark_button.js

bookmark_button.js

14 ms

widgets.js

widgets.js

6 ms

loader.js

loader.js

23 ms

bookmark_button.js

bookmark_button.js

11 ms

2nd_gets.php

2nd_gets.php

346 ms

plusone.js

plusone.js

18 ms

l.j

l.j

339 ms

common.css

common.css

189 ms

pretty-colorg12.css

pretty-colorg12.css

329 ms

clearfix.css

clearfix.css

227 ms

print.css

print.css

326 ms

advanced.css

advanced.css

376 ms

jquery.min.js

jquery.min.js

55 ms

button-only.gif

button-only.gif

5 ms

bnr.gif

bnr.gif

33 ms

yahoo.gif

yahoo.gif

188 ms

gmail.gif

gmail.gif

190 ms

livedoor.gif

livedoor.gif

167 ms

au.gif

au.gif

191 ms

hotmail.gif

hotmail.gif

167 ms

infoseek.gif

infoseek.gif

191 ms

excite.gif

excite.gif

332 ms

goo.gif

goo.gif

331 ms

webr.gif

webr.gif

372 ms

inter7.gif

inter7.gif

375 ms

wlm.gif

wlm.gif

375 ms

wm.gif

wm.gif

378 ms

ol.gif

ol.gif

493 ms

b.gif

b.gif

497 ms

t.gif

t.gif

559 ms

mail.gif

mail.gif

561 ms

btn-mail01.gif

btn-mail01.gif

562 ms

btn-pagetop_off.png

btn-pagetop_off.png

566 ms

headlogo.gif

headlogo.gif

656 ms

gtm.js

gtm.js

30 ms

mainin-bg.gif

mainin-bg.gif

659 ms

button-only.gif

button-only.gif

12 ms

bg-contents-h2.gif

bg-contents-h2.gif

715 ms

icon-point02.png

icon-point02.png

719 ms

bg-contents-h3.gif

bg-contents-h3.gif

720 ms

icon-check08.png

icon-check08.png

725 ms

icon-check02-blue.png

icon-check02-blue.png

788 ms

gtm.js

gtm.js

68 ms

all.js

all.js

22 ms

side-contents-top.gif

side-contents-top.gif

758 ms

bg-sidebar-h3.gif

bg-sidebar-h3.gif

864 ms

icon-menu03.gif

icon-menu03.gif

870 ms

bg-footer.gif

bg-footer.gif

870 ms

bg-footer-h3.gif

bg-footer-h3.gif

876 ms

icon-menu01.gif

icon-menu01.gif

914 ms

logo4.gif

logo4.gif

337 ms

all.js

all.js

6 ms

analytics.js

analytics.js

5 ms

pta.js

pta.js

15 ms

linkid.js

linkid.js

7 ms

collect

collect

34 ms

collect

collect

37 ms

js

js

40 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

29 ms

fastbutton

fastbutton

27 ms

l174.f

l174.f

19872 ms

postmessageRelay

postmessageRelay

41 ms

developers.google.com

developers.google.com

330 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

28 ms

rpc:shindig_random.js

rpc:shindig_random.js

17 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

36 ms

like.php

like.php

229 ms

like.php

like.php

326 ms

settings

settings

100 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

embeds

embeds

28 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

15 ms

9RkfBY4NJsx.js

9RkfBY4NJsx.js

19 ms

FEppCFCt76d.png

FEppCFCt76d.png

11 ms

Accessibility Review

46mail.net accessibility score

91

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

46mail.net best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

46mail.net SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 46mail.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that 46mail.net 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.

Social Sharing Optimization

46mail.net

Open Graph description is not detected on the main page of 46 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: