7.9 sec in total
760 ms
6.7 sec
448 ms
Click here to check amazing Tone content for Japan. Otherwise, check out these important facts you probably never knew about tone.ne.jp
インターネット使い放題で月額1100円(動画は1GBまで)からご利用いただけるスマホです。子供の安全を守る充実の見守り機能とガラケーからのお乗り換えなどはじめてのスマホとして最適な機能やサポートが充実。
Visit tone.ne.jpWe analyzed Tone.ne.jp page load time and found that the first response time was 760 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
tone.ne.jp performance score
name
value
score
weighting
Value4.3 s
19/100
10%
Value9.6 s
1/100
25%
Value10.9 s
7/100
10%
Value1,740 ms
11/100
30%
Value0.478
18/100
15%
Value17.2 s
5/100
10%
760 ms
335 ms
1040 ms
518 ms
349 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 77% of them (85 requests) were addressed to the original Tone.ne.jp, 3% (3 requests) were made to V2.zopim.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Tone.ne.jp.
Page size can be reduced by 551.5 kB (47%)
1.2 MB
629.5 kB
In fact, the total size of Tone.ne.jp main page is 1.2 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. Images take 663.6 kB which makes up the majority of the site volume.
Potential reduce by 37.9 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 37.9 kB or 77% of the original size.
Potential reduce by 191.0 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, Tone needs image optimization as it can save up to 191.0 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 106.9 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 106.9 kB or 49% of the original size.
Potential reduce by 215.7 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. Tone.ne.jp needs all CSS files to be minified and compressed as it can save up to 215.7 kB or 86% of the original size.
Number of requests can be reduced by 35 (33%)
106
71
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
tone.ne.jp
760 ms
normalize.min.css
335 ms
bootstrap.css
1040 ms
bootstrap-responsive.css
518 ms
common.css
349 ms
layout.css
524 ms
style.css
873 ms
top-special.css
706 ms
modernizr-2.6.2-respond-1.1.0.min.js
730 ms
jquery.min.js
34 ms
vender.js
680 ms
script.js
675 ms
bootstrap-dropdown.js
886 ms
announce.js
902 ms
tw_timeline.js
1020 ms
main.js
1016 ms
top.min.js
1398 ms
top.js
1192 ms
jquery.scrolldepth.min.js
1197 ms
conversion.js
15 ms
analytics.js
35 ms
header-menu-txt-1.png
402 ms
header-menu-txt-2.png
523 ms
header-menu-txt-3.png
521 ms
header-menu-txt-4.png
1035 ms
top_logo_tsutaya.png
706 ms
logo-sub.png
792 ms
global-nav-txt-1.png
1035 ms
global-nav-txt-2.png
970 ms
global-nav-txt-3.png
971 ms
global-nav-txt-4.png
1086 ms
global-nav-txt-5.png
1142 ms
logo-fixed.png
1213 ms
header-fixed-txt-1.png
1241 ms
header-fixed-txt-2.png
1722 ms
header-fixed-txt-3.png
1722 ms
header-fixed-txt-4.png
1727 ms
header-fixed-txt-5.png
1728 ms
header-fixed-txt-6.png
1730 ms
slider-menu-01-txt-inv.jpg
2198 ms
slider-menu-02-txt-inv.jpg
2203 ms
slider-menu-03-txt-inv.jpg
1904 ms
purchase_title.png
1787 ms
purchase_title.png
1828 ms
purchase_item1.png
1899 ms
purchase_item1.png
2327 ms
purchase_item_figure1.png
2327 ms
purchase_item2.png
2234 ms
purchase_item2.png
2431 ms
all.js
74 ms
purchase_item_figure2.png
2549 ms
purchase_item3.png
2562 ms
collect
34 ms
purchase_item3.png
2675 ms
collect
84 ms
70 ms
xd_arbiter.php
72 ms
xd_arbiter.php
149 ms
purchase_item_figure3.png
2717 ms
section-infos-h2.png
2565 ms
section-infos_oyako.jpg
2773 ms
section-infos_tvcm.jpg
2731 ms
section-infos_simulator.jpg
2714 ms
section-infos-9-h3.png
2735 ms
section-infos_kenko.jpg
2737 ms
tag.js
10 ms
86 ms
section-infos-3-h3.png
2994 ms
tag
51 ms
fbm_top_json.php
743 ms
fbm_top_json.php
1131 ms
ping
63 ms
ya.js
408 ms
blade_track_jp.js
404 ms
37 ms
section-infos-6-h3.png
2712 ms
section-infos-10-h3.png
2879 ms
widget_v2.132.js
14 ms
__$$__stringtable_lang_ja.js
21 ms
section-news-h2.png
2501 ms
back-to-top-txt.png
2616 ms
footer-nav-1-txt-1.png
2580 ms
footer-nav-1-txt-2.png
2725 ms
cookie_enabled_get.html
688 ms
pb.js
691 ms
685 ms
footer-nav-1-txt-3.png
2740 ms
footer-nav-1-txt-4.png
2736 ms
footer-nav-1-txt-5.png
2697 ms
footer-nav-2-txt-1.png
2699 ms
avatar_simple_visitor.png
102 ms
footer-nav-2-txt-2.png
2331 ms
footer-nav-2-txt-3.png
2383 ms
footer-nav-3-txt-1.png
2446 ms
footer-nav-3-txt-2.png
2518 ms
footer-nav-3-txt-3.png
2539 ms
aL63HcygAAVYuCCsAAA==
10 ms
bl_track.cgi
376 ms
footer-nav-3-txt-4.png
2502 ms
footer-nav-3-txt-5.png
2552 ms
footer-nav-3-txt-6.png
2536 ms
footer-nav-3-txt-7.png
2624 ms
copy.png
2383 ms
header-menu-li-bg.png
2407 ms
purchase_item1-ov.png
2425 ms
purchase_item2-ov.png
2406 ms
purchase_item3-ov.png
2470 ms
section-infos-more-bg.png
2430 ms
footer-nav-5-line.gif
2382 ms
dummy.png
2378 ms
balloon_cm.jpg
2305 ms
tone.ne.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
tone.ne.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
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
tone.ne.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 doesn't use 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 Tone.ne.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 Tone.ne.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.
tone.ne.jp
Open Graph data is detected on the main page of Tone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: