Tools & Wizards About Us
chocom.jp screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    48% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 81% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

chocom.jp

電子マネー ちょコムeマネー

Page Load Speed

6.5 sec in total

First Response

517 ms

Resources Loaded

5 sec

Page Rendered

1 sec

chocom.jp screenshot

About Website

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

Key Findings

We analyzed Chocom.jp page load time and found that the first response time was 517 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

chocom.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.53

14/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

chocom.jp

517 ms

chocom.jp

1192 ms

frame.css

513 ms

content_index_new.css

687 ms

top.css

525 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 80% of them (66 requests) were addressed to the original Chocom.jp, 6% (5 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Chocom.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 780.1 kB (34%)

Content Size

2.3 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chocom.jp main page is 2.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. Only a small number of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 81.6 kB

  • Original 95.5 kB
  • After minification 82.5 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 13.0 kB, which is 14% 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 81.6 kB or 85% of the original size.

Image Optimization

-21%

Potential reduce by 373.7 kB

  • Original 1.8 MB
  • After minification 1.4 MB

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, Chocom needs image optimization as it can save up to 373.7 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 159.1 kB

  • Original 221.1 kB
  • After minification 219.3 kB
  • After compression 61.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 159.1 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 165.7 kB

  • Original 194.8 kB
  • After minification 149.0 kB
  • After compression 29.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 165.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (24%)

Requests Now

74

After Optimization

56

  • Images
  • JavaScript
  • CSS

The browser has sent 74 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 9 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

chocom.jp

chocom.jp

517 ms

chocom.jp

chocom.jp

1192 ms

frame.css

frame.css

513 ms

content_index_new.css

content_index_new.css

687 ms

top.css

top.css

525 ms

css2

css2

35 ms

css

css

51 ms

swiper.min.js

swiper.min.js

1217 ms

swiper.min.css

swiper.min.css

531 ms

jquery.js

jquery.js

835 ms

jquery.page-scroller.js

jquery.page-scroller.js

683 ms

all.css

all.css

1230 ms

minimal-modal.min.js

minimal-modal.min.js

554 ms

conversion.js

conversion.js

101 ms

imageMapResizer.min.js

imageMapResizer.min.js

30 ms

frame_base.css

frame_base.css

342 ms

frame_layout.css

frame_layout.css

346 ms

css2

css2

17 ms

icon

icon

24 ms

gtm.js

gtm.js

149 ms

docomo_buisiness_logo.png

docomo_buisiness_logo.png

260 ms

chocomlogo.svg

chocomlogo.svg

256 ms

chocom_logo.png

chocom_logo.png

256 ms

sitemap.svg

sitemap.svg

256 ms

gaku_btn_mobile.gif

gaku_btn_mobile.gif

571 ms

soukin_btn_mobile.png

soukin_btn_mobile.png

254 ms

slide_exchange_bg.png

slide_exchange_bg.png

405 ms

slide_exchange_2.png

slide_exchange_2.png

569 ms

slide_exchange_3.png

slide_exchange_3.png

721 ms

slide_exchange_4.png

slide_exchange_4.png

404 ms

slide_exchange_5.png

slide_exchange_5.png

405 ms

slide_exchange_6.png

slide_exchange_6.png

573 ms

slide_exchange_7.png

slide_exchange_7.png

574 ms

slide_exchange_bg.png

slide_exchange_bg.png

579 ms

slide_exchange_1.png

slide_exchange_1.png

748 ms

slide_exchange_2.png

slide_exchange_2.png

751 ms

slide_exchange_3.png

slide_exchange_3.png

914 ms

slide_exchange_4.png

slide_exchange_4.png

747 ms

slide_exchange_5.png

slide_exchange_5.png

756 ms

slide_dcp2024_pc.jpg

slide_dcp2024_pc.jpg

1387 ms

slide_dcp2024_sp.jpg

slide_dcp2024_sp.jpg

1309 ms

slide_ga1_b.png

slide_ga1_b.png

920 ms

slide_ga1_1.png

slide_ga1_1.png

929 ms

slide_ga1_2.png

slide_ga1_2.png

935 ms

slide_ga1_3.png

slide_ga1_3.png

1087 ms

slide_ga1_4.png

slide_ga1_4.png

1093 ms

slide_ga1_5.png

slide_ga1_5.png

1106 ms

slide_ga1_6.png

slide_ga1_6.png

1112 ms

slide_ga1_b.png

slide_ga1_b.png

1259 ms

slide_ga1_1.png

slide_ga1_1.png

1268 ms

slide_ga1_2.png

slide_ga1_2.png

1286 ms

slide_ga1_3.png

slide_ga1_3.png

1289 ms

slide_ga1_4.png

slide_ga1_4.png

1433 ms

slide_ga1_5.png

slide_ga1_5.png

1441 ms

slide_ga1_6.png

slide_ga1_6.png

1465 ms

ms_1_b.png

ms_1_b.png

1639 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

119 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

379 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

422 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

234 ms

101 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

20 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A99d.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A99d.ttf

96 ms

js

js

75 ms

nttsmarttrade-logo_white.svg

nttsmarttrade-logo_white.svg

1237 ms

ms_1_1.png

ms_1_1.png

1309 ms

ms_1_2.png

ms_1_2.png

1358 ms

ms_1_3.png

ms_1_3.png

1366 ms

ms_1_b.png

ms_1_b.png

1393 ms

50 ms

135 ms

ms_1_1.png

ms_1_1.png

1264 ms

ms_1_2.png

ms_1_2.png

1330 ms

ms_1_3.png

ms_1_3.png

1380 ms

mid-panel2.png

mid-panel2.png

1225 ms

mid-panel3.png

mid-panel3.png

1253 ms

mid-panel4.png

mid-panel4.png

1255 ms

banner_dcard2024.jpg

banner_dcard2024.jpg

1271 ms

coin.png

coin.png

1327 ms

coin2.png

coin2.png

1237 ms

chocom_map.jpg

chocom_map.jpg

1723 ms

btn_pagetop.gif

btn_pagetop.gif

1254 ms

border.gif

border.gif

1254 ms

Accessibility Review

chocom.jp accessibility score

93

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

Links do not have a discernible name

High

<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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

chocom.jp 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

High

Page has valid source maps

SEO Factors

chocom.jp SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

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

Social Sharing Optimization

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: