13.9 sec in total
531 ms
11.6 sec
1.8 sec
Welcome to cardclub.co.jp homepage info - get ready to check Cardclub best content for Japan right away, or after learning these important things about cardclub.co.jp
Visit cardclub.co.jpWe analyzed Cardclub.co.jp page load time and found that the first response time was 531 ms and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cardclub.co.jp performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value11.6 s
0/100
25%
Value9.3 s
12/100
10%
Value130 ms
96/100
30%
Value0.317
36/100
15%
Value10.7 s
22/100
10%
531 ms
1279 ms
336 ms
503 ms
357 ms
Our browser made a total of 208 requests to load all elements on the main page. We found that 56% of them (116 requests) were addressed to the original Cardclub.co.jp, 14% (30 requests) were made to Image.rakuten.co.jp and 6% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Cardclub.co.jp.
Page size can be reduced by 553.1 kB (12%)
4.5 MB
4.0 MB
In fact, the total size of Cardclub.co.jp main page is 4.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 69.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 69.9 kB or 80% of the original size.
Potential reduce by 75.5 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. Cardclub images are well optimized though.
Potential reduce by 360.4 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 360.4 kB or 66% of the original size.
Potential reduce by 47.2 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. Cardclub.co.jp needs all CSS files to be minified and compressed as it can save up to 47.2 kB or 80% of the original size.
Number of requests can be reduced by 68 (33%)
204
136
The browser has sent 204 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cardclub. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
cardclub.co.jp
531 ms
www.cardclub.co.jp
1279 ms
import.css
336 ms
mt.js
503 ms
cube.site.js
357 ms
cube.win_op.js
358 ms
jquery-1.8.3.min.js
14 ms
jquery.easing.1.3.js
360 ms
jquery.mousewheel.js
690 ms
jquery.rollOver.js
715 ms
jquery.slideImage.js
711 ms
jquery.fullSlide.js
712 ms
jquery.customScroll.js
847 ms
jquery.droppy.js
880 ms
fixHeight.js
1020 ms
shadowbox.js
1382 ms
js
28 ms
config.js.php
1070 ms
ga.js
1065 ms
plusone.js
182 ms
bookmark_button.js
370 ms
base.css
874 ms
content.css
885 ms
dmanager.css
1026 ms
shop.css
1272 ms
shop-other.css
1101 ms
shadowbox.css
1233 ms
extra.css
1242 ms
w_js.php
1384 ms
conversion.js
14 ms
s_retargeting.js
521 ms
analytics.js
63 ms
cb=gapi.loaded_0
53 ms
button-only@2x.png
264 ms
3100010017849-1.jpg
752 ms
bg.jpg
2107 ms
container-bg.jpg
361 ms
container-inner-bg.jpg
1097 ms
logo.jpg
558 ms
header-tel.png
557 ms
header-info1.png
532 ms
header-info2.png
757 ms
header-info3.png
890 ms
header-info4.png
915 ms
header-nav1.jpg
913 ms
header-nav2.jpg
1094 ms
header-nav3.jpg
1224 ms
header-nav4.jpg
1248 ms
shop-search-btn.jpg
1270 ms
p1.jpg
3024 ms
gnav01.jpg
1448 ms
gnav02.jpg
1576 ms
gnav03.jpg
1604 ms
gnav04.jpg
1624 ms
gnav05.jpg
1806 ms
group-title.png
2110 ms
group-image01.png
1958 ms
group-image02.png
1980 ms
group-image03.png
2165 ms
group-image04.png
2314 ms
group-image05.png
2335 ms
mainserch-title.png
3446 ms
shop-search-btn2.jpg
2466 ms
201631204443-thumb-350x243-443_170xauto.jpg
2703 ms
201631203448_170xauto.JPG
2670 ms
201616101921_170xauto.jpg
2869 ms
201631202840_170xauto.JPG
3038 ms
maindata-title-yu.jpg
3203 ms
maindata-title-do.jpg
3274 ms
3100010054851-1.jpg
735 ms
3100010016170-1.jpg
260 ms
3100010017320-1.jpg
732 ms
3100010016750-1.jpg
592 ms
3100000429348-1.jpg
744 ms
3100010342392-1.jpg
523 ms
3100000548490-1.jpg
1155 ms
3100010091955-1.jpg
1175 ms
3100010037625-1.jpg
1228 ms
3100000311643-1.jpg
945 ms
3100010017306-1.jpg
1437 ms
3100000569273-1.jpg
1133 ms
3100000343118-1.jpg
1356 ms
3100000520618-1.jpg
1616 ms
3100000606350-1.jpg
1707 ms
3100000424565-1.jpg
1407 ms
3100000489472-1.jpg
1920 ms
3100000587673-1.jpg
2215 ms
3100000563998-1.jpg
1868 ms
3100000395469-1.jpg
1644 ms
3100000563875-1.jpg
2015 ms
3100000563950-1.jpg
1871 ms
3100000528638-1.jpg
2291 ms
3100000593667-1.jpg
2262 ms
3100000602888-1.jpg
2425 ms
3100000588762-1.jpg
2648 ms
3100000646332-1.jpg
2377 ms
3100000602901-1.jpg
2476 ms
3100000646424-1.jpg
3042 ms
widgets.js
31 ms
maindata-title-ai.jpg
3345 ms
like.php
204 ms
collect
50 ms
maindata-title-va.jpg
3305 ms
rU2ubZ6l1Q5.js
77 ms
LVx-xkvaJ0b.png
67 ms
271 ms
cb=gapi.loaded_1
32 ms
fastbutton
209 ms
likebox.php
192 ms
200 ms
postmessageRelay
242 ms
blade_track_jp.js
503 ms
mainban1-title.jpg
3183 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
135 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
132 ms
C-D3sjGKj3j.css
80 ms
zEMlMNmIXUJ.css
81 ms
_rx8naC75Dy.js
99 ms
b94UUzHjapV.js
118 ms
0wM5s1Khldu.js
98 ms
TTCre3391I0.js
90 ms
cb=gapi.loaded_0
63 ms
cb=gapi.loaded_1
218 ms
mainban1-1.jpg
3177 ms
reset.css
57 ms
entry-button.css
61 ms
213 ms
219 ms
mainban1-2.jpg
3258 ms
mainban1-3.jpg
4073 ms
api.js
176 ms
core:rpc:shindig.random:shindig.sha1.js
247 ms
2536007149-postmessagerelay.js
233 ms
bbtn-s_v3.png
142 ms
1424371_639722912747376_1446372537_n.png
146 ms
1017034_609364855783182_96844684_n.jpg
127 ms
10003505_1573093476242769_5759129264812856654_n.jpg
131 ms
1379841_10150004552801901_469209496895221757_n.jpg
128 ms
12239492_454864318054818_7453660653006426142_n.jpg
129 ms
10647138_307189022813978_1759498243678764829_n.jpg
130 ms
wL6VQj7Ab77.png
60 ms
s7jcwEQH7Sx.png
60 ms
syndication
151 ms
369880055175856128
223 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
31 ms
mainban2.jpg
4108 ms
I6-MnjEovm5.js
7 ms
f6T91Deal_q.js
6 ms
cookie_enabled_get.html
356 ms
message-title.jpg
3189 ms
img4.jpg
3146 ms
message-img2.jpg
3330 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
8 ms
7c42735802dfb2cf6b73c2201b0e5b93_normal.jpeg
177 ms
newblog-title.jpg
3261 ms
sideshopcart-title.jpg
3270 ms
bl_track.cgi
352 ms
sideshopcart-btn.jpg
3186 ms
sidebantel.png
3354 ms
data-130711130352.png
3445 ms
jot.html
2 ms
sideshopcat-title.jpg
3320 ms
sideban1.jpg
3368 ms
sideban2.jpg
3531 ms
sideban3.jpg
3581 ms
sideban4.jpg
3438 ms
sidelogin-title.jpg
3169 ms
sidelogin-mail.jpg
3239 ms
sidelogin-pass.jpg
3181 ms
sidelogin-btn.jpg
3351 ms
sideban2-1.jpg
3683 ms
snav-contents-title.jpg
3240 ms
bnr_game.png
3441 ms
bnr_keitai.png
3275 ms
bnr_yugioh.jpg
3141 ms
bnr_aikatsu.jpg
3289 ms
bnr_dbh.jpg
3182 ms
onflash-topic.png
3079 ms
onflash-gnav-bg.png
3072 ms
mainserch-bg.png
3945 ms
entry-title-bg.jpg
2930 ms
message-end.jpg
2982 ms
message-bg.jpg
2964 ms
newblog-end.jpg
2895 ms
shopsidepartscart-bg.jpg
2891 ms
level1-bg.jpg
2857 ms
shop-category-btn-bg.jpg
2875 ms
category36.jpg
2690 ms
category42.jpg
2861 ms
category40.jpg
2739 ms
category41.jpg
2746 ms
category35.jpg
2613 ms
category53.jpg
2832 ms
category52.jpg
2837 ms
category34.jpg
2685 ms
category57.jpg
2843 ms
sidelogin-end.jpg
2688 ms
snav-end.jpg
2649 ms
snav-bg.jpg
2657 ms
common.js
5 ms
util.js
22 ms
stats.js
22 ms
AuthenticationService.Authenticate
210 ms
snav-btn-bg.jpg
2545 ms
footer-bg.jpg
2657 ms
footer-inner-bg.jpg
3379 ms
2659 ms
cardclub.co.jp accessibility score
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.
cardclub.co.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
Detected JavaScript libraries
Browser errors were logged to the console
cardclub.co.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 doesn't use legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cardclub.co.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 Cardclub.co.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.
cardclub.co.jp
Open Graph description is not detected on the main page of Cardclub. 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: