11.6 sec in total
598 ms
10.8 sec
221 ms
Visit chocom.jp now to see the best up-to-date Chocom content for Japan and also check out these interesting facts you probably never knew about chocom.jp
NTTスマートトレードが提供する簡単・便利なネット専用電子マネー「ちょコムeマネー」。
Visit chocom.jpWe analyzed Chocom.jp page load time and found that the first response time was 598 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
chocom.jp performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value13.5 s
0/100
25%
Value27.0 s
0/100
10%
Value16,930 ms
0/100
30%
Value0.514
15/100
15%
Value32.5 s
0/100
10%
598 ms
580 ms
768 ms
366 ms
738 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 85% of them (100 requests) were addressed to the original Chocom.jp, 5% (6 requests) were made to Omt.shinobi.jp and 2% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Chocom.jp.
Page size can be reduced by 179.5 kB (13%)
1.3 MB
1.2 MB
In fact, the total size of Chocom.jp main page is 1.3 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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 19.4 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 19.4 kB or 74% of the original size.
Potential reduce by 435 B
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. Chocom images are well optimized though.
Potential reduce by 84.5 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 84.5 kB or 51% of the original size.
Potential reduce by 75.1 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. Chocom.jp needs all CSS files to be minified and compressed as it can save up to 75.1 kB or 84% of the original size.
Number of requests can be reduced by 47 (42%)
112
65
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chocom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
chocom.jp
598 ms
www.chocom.jp
580 ms
index.html
768 ms
frame.css
366 ms
content_index_new.css
738 ms
content_index.css
760 ms
top.css
394 ms
common.js
395 ms
rollover.js
750 ms
jquery.js
1342 ms
jquery.page-scroller.js
776 ms
jquery.js
1360 ms
jquery.timer.js
1099 ms
ntt.chocom.banner.js
1123 ms
frame.css
1136 ms
frame_base.css
824 ms
frame_layout.css
1502 ms
copyright.js
1146 ms
conversion.js
36 ms
ga.js
29 ms
redirect_cp03.gif
742 ms
bg.gif
205 ms
illust_new.gif
385 ms
site_logo.gif
388 ms
gm01_v.jpg
392 ms
gm04.jpg
393 ms
gm03.jpg
401 ms
gm05.jpg
601 ms
gm06.jpg
768 ms
btn_point.gif
771 ms
head_icon.gif
769 ms
head_search_ttl.gif
768 ms
head_search_btn.gif
789 ms
language_c.gif
968 ms
language_e.gif
1137 ms
t_btn.gif
1145 ms
m_btn.gif
1150 ms
s_btn.gif
1155 ms
img_30.jpg
2315 ms
nav_prev.gif
1345 ms
nav_next.gif
1521 ms
news_title.gif
1523 ms
news_btn.gif
1532 ms
topics_title.gif
1551 ms
topics_btn.gif
1722 ms
top_left_title12.jpg
2122 ms
use_img.jpg
4100 ms
cn_btn.jpg
1911 ms
en_btn.jpg
1935 ms
facebook_btn.jpg
2105 ms
twitter_btn.jpg
2302 ms
btn_pagetop.gif
2320 ms
menu_01.jpg
2675 ms
menu_02.jpg
2525 ms
smt.gif
2693 ms
btn_payback.jpg
3070 ms
b3e841219aa466ef14cd6c0bc14e8687
1055 ms
master_btn.jpg
3448 ms
__utm.gif
11 ms
chocomk.jpg
2939 ms
bn_present.jpg
2862 ms
bn_present2.jpg
2686 ms
monitor_btn.jpg
3254 ms
bn_bingo.jpg
3066 ms
top_s_bana03.jpg
3370 ms
attention_btn.jpg
3213 ms
btn_bokin.jpg
3287 ms
bana-travelers_card.jpg
3880 ms
logo_ntt.gif
3262 ms
ninja_onetag.css
347 ms
trac.js
498 ms
tit.gif
2747 ms
border.gif
2796 ms
box_bg_top.gif
3002 ms
box_bg_bottom.gif
3035 ms
bg.gif
3061 ms
ico01.gif
3136 ms
copyright2012.gif
3197 ms
40 ms
tweet_button.html
29 ms
facebook_share_ninja_l.png
176 ms
thumb_27.gif
3342 ms
google_plusone_ninja_l.png
343 ms
hatena_ninja_l.png
346 ms
line_ninja_30x30.png
352 ms
jot
93 ms
51 ms
thumb_28.gif
3311 ms
thumb_11.gif
3327 ms
43 ms
cookiesync
548 ms
gm04_o.jpg
200 ms
gm03_o.jpg
199 ms
gm05_o.jpg
385 ms
gm06_o.jpg
386 ms
btn_point_o.gif
388 ms
language_c_o.gif
398 ms
language_e_o.gif
567 ms
t_btn_o.gif
581 ms
m_btn_o.gif
758 ms
s_btn_o.gif
777 ms
news_btn_o.gif
783 ms
topics_btn_o.gif
775 ms
btn_pagetop_o.gif
948 ms
menu_01_o.jpg
1345 ms
menu_02_o.jpg
1134 ms
smt_o.gif
1151 ms
btn_payback_o.jpg
1348 ms
chocomk_o.jpg
1383 ms
bn_present_o.jpg
1347 ms
bn_present2_o.jpg
1512 ms
monitor_btn_o.jpg
1534 ms
bn_bingo_o.jpg
1718 ms
top_s_bana03_o.jpg
1914 ms
attention_btn_o.jpg
1731 ms
btn_bokin_o.jpg
1955 ms
bana-travelers_card_o.jpg
2458 ms
chocom.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
Links do not have a discernible name
<object> elements do not have alternate text
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>).
chocom.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
Browser errors were logged to the console
Page has valid source maps
chocom.jp SEO score
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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chocom.jp 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 Chocom.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.
chocom.jp
Open Graph description is not detected on the main page of Chocom. 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: