Tools & Wizards About Us
jcb-eit.jp screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

jcb-eit.jp

JCB EIT（エイト）カード 年会費無料でポイントがたまるカード｜クレジットカードのお申し込みなら、JCBカード

Page Load Speed

5.7 sec in total

First Response

324 ms

Resources Loaded

4.9 sec

Page Rendered

452 ms

jcb-eit.jp screenshot

About Website

Visit jcb-eit.jp now to see the best up-to-date JCB EIT content for Japan and also check out these interesting facts you probably never knew about jcb-eit.jp

JCB EIT（エイト）カードのお申し込みはこちらから。オンライン入会申込や資料請求によるお申し込みもこちらから行えます。年会費無料でおトクにポイントがたまる便利なJCBクレジットカードに是非お申し込みください！

Visit jcb-eit.jp

Key Findings

We analyzed Jcb-eit.jp page load time and found that the first response time was 324 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

jcb-eit.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value23.5 s

0/100

25%

SI (Speed Index)

Value18.6 s

0/100

10%

TBT (Total Blocking Time)

Value12,660 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.215

58/100

15%

TTI (Time to Interactive)

Value33.7 s

0/100

10%

Network Requests Diagram

jcb-eit.jp

324 ms

jcb-eit.jp

680 ms

www.jcb-eit.jp

314 ms

www.jcb-eit.jp

679 ms

eit.html

220 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Jcb-eit.jp, 76% (62 requests) were made to Jcb.co.jp and 7% (6 requests) were made to Jcb.sitecorecontenthub.cloud. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Jcb.sitecorecontenthub.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 528.3 kB (49%)

Content Size

1.1 MB

After Optimization

560.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jcb-eit.jp main page is 1.1 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. 45% of websites need less resources to load. Javascripts take 873.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 42.8 kB

  • Original 52.5 kB
  • After minification 41.6 kB
  • After compression 9.7 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 10.9 kB, which is 21% 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 42.8 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 95 B

  • Original 42.8 kB
  • After minification 42.7 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. JCB EIT images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 476.3 kB

  • Original 873.6 kB
  • After minification 872.5 kB
  • After compression 397.3 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 476.3 kB or 55% of the original size.

CSS Optimization

-8%

Potential reduce by 9.1 kB

  • Original 119.5 kB
  • After minification 119.5 kB
  • After compression 110.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. Jcb-eit.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 60 (79%)

Requests Now

76

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JCB EIT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

jcb-eit.jp

jcb-eit.jp

324 ms

jcb-eit.jp

jcb-eit.jp

680 ms

www.jcb-eit.jp

www.jcb-eit.jp

314 ms

www.jcb-eit.jp

www.jcb-eit.jp

679 ms

eit.html

eit.html

220 ms

eit.html

eit.html

212 ms

satelliteLib-bb5c97e29061c1386e42a23b9dec83f3bfbc862f.js

satelliteLib-bb5c97e29061c1386e42a23b9dec83f3bfbc862f.js

23 ms

normalize.min.css

normalize.min.css

40 ms

swiper-8.4.4.min.css

swiper-8.4.4.min.css

36 ms

main.css

main.css

45 ms

module.css

module.css

39 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

55 ms

swiper-8.4.4.js

swiper-8.4.4.js

57 ms

plugins_jq3.js

plugins_jq3.js

55 ms

main_jq3.js

main_jq3.js

57 ms

matchMedia.js

matchMedia.js

54 ms

jquery.tile.min.js

jquery.tile.min.js

56 ms

module_jq3.js

module_jq3.js

83 ms

modal_window.js

modal_window.js

91 ms

search_tool_n3.js

search_tool_n3.js

123 ms

carddetail_jq3.js

carddetail_jq3.js

71 ms

jquery.cookie.js

jquery.cookie.js

73 ms

CardAPI.js

CardAPI.js

73 ms

cardapi_lib_jq3.js

cardapi_lib_jq3.js

326 ms

scrollto_h1_next.js

scrollto_h1_next.js

90 ms

gtm.js

gtm.js

114 ms

90220_pic_check.png

90220_pic_check.png

1284 ms

90670_pic_myjcb.png

90670_pic_myjcb.png

1778 ms

90796_pic_point.png

90796_pic_point.png

1728 ms

90736_pic_pen.png

90736_pic_pen.png

2404 ms

90766_pic_plus.png

90766_pic_plus.png

1769 ms

90422_pic_faq.png

90422_pic_faq.png

1808 ms

header-logo.png

header-logo.png

68 ms

r_img01.gif

r_img01.gif

69 ms

eit_icon_img01.gif

eit_icon_img01.gif

75 ms

eit_icon_img02.gif

eit_icon_img02.gif

82 ms

eit_icon_img03.gif

eit_icon_img03.gif

87 ms

eit_icon_img04.gif

eit_icon_img04.gif

78 ms

eit_icon_img05.gif

eit_icon_img05.gif

85 ms

eit_icon_img06.gif

eit_icon_img06.gif

93 ms

eit_icon_img08.gif

eit_icon_img08.gif

89 ms

eit_card_img01.gif

eit_card_img01.gif

97 ms

eit_card_img07.gif

eit_card_img07.gif

101 ms

eit_card_img09.gif

eit_card_img09.gif

101 ms

eit_card_img05.gif

eit_card_img05.gif

104 ms

eit_card_img03.gif

eit_card_img03.gif

116 ms

eit_card_img11.gif

eit_card_img11.gif

304 ms

quicpay.png

quicpay.png

118 ms

applepay_img_eit_5.jpg

applepay_img_eit_5.jpg

117 ms

icon_sns_fb.png

icon_sns_fb.png

120 ms

icon_sns_x.png

icon_sns_x.png

121 ms

icon_sns_yt.png

icon_sns_yt.png

146 ms

footer_logo.png

footer_logo.png

143 ms

main-blessed1.css

main-blessed1.css

136 ms

header-bg.png

header-bg.png

190 ms

taglineXL.png

taglineXL.png

187 ms

icon-search.png

icon-search.png

28 ms

icon_gnavtoggle.png

icon_gnavtoggle.png

188 ms

icon_blank8.png

icon_blank8.png

678 ms

opacity_black.png

opacity_black.png

39 ms

icon_arrow-breadcrumbs.png

icon_arrow-breadcrumbs.png

44 ms

icon_next.png

icon_next.png

53 ms

icon_check.png

icon_check.png

275 ms

icon_anchor-blue.png

icon_anchor-blue.png

65 ms

icon_arrow-blue.png

icon_arrow-blue.png

75 ms

icon_blank10-blue.png

icon_blank10-blue.png

745 ms

icon_blank10.png

icon_blank10.png

201 ms

icon_fb.png

icon_fb.png

377 ms

icon_tw.png

icon_tw.png

839 ms

icon_app.png

icon_app.png

220 ms

icon_pagetop.png

icon_pagetop.png

233 ms

icon_navdisc.png

icon_navdisc.png

251 ms

icon_blank10-gray.png

icon_blank10-gray.png

915 ms

utag.js

utag.js

77 ms

tag.js

tag.js

23 ms

icon_prev.png

icon_prev.png

275 ms

utag.5.js

utag.5.js

68 ms

i.gif

i.gif

19 ms

utag.v.js

utag.v.js

2 ms

print.css

print.css

20 ms

i_search_assist_n3.js

i_search_assist_n3.js

5 ms

new_ac.css

new_ac.css

17 ms

Accessibility Review

jcb-eit.jp accessibility score

62

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jcb-eit.jp best practices score

67

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

jcb-eit.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jcb-eit.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 Jcb-eit.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

jcb-eit.jp

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