8.9 sec in total
1.4 sec
7.4 sec
163 ms
Visit withcard.co.jp now to see the best up-to-date Withcard content for Japan and also check out these interesting facts you probably never knew about withcard.co.jp
井筒屋ウィズカードの公式サイトです。
Visit withcard.co.jpWe analyzed Withcard.co.jp page load time and found that the first response time was 1.4 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
withcard.co.jp performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value11.5 s
0/100
25%
Value14.1 s
1/100
10%
Value180 ms
91/100
30%
Value0.467
19/100
15%
Value6.4 s
59/100
10%
1355 ms
348 ms
524 ms
1089 ms
548 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 99% of them (152 requests) were addressed to the original Withcard.co.jp, 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Withcard.co.jp.
Page size can be reduced by 203.4 kB (35%)
585.8 kB
382.4 kB
In fact, the total size of Withcard.co.jp main page is 585.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 337.8 kB which makes up the majority of the site volume.
Potential reduce by 29.3 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 29.3 kB or 78% of the original size.
Potential reduce by 37.6 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, Withcard needs image optimization as it can save up to 37.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 98.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 98.9 kB or 60% of the original size.
Potential reduce by 37.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. Withcard.co.jp needs all CSS files to be minified and compressed as it can save up to 37.7 kB or 82% of the original size.
Number of requests can be reduced by 32 (21%)
153
121
The browser has sent 153 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Withcard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.withcard.co.jp
1355 ms
import.css
348 ms
typography.css
524 ms
jquery-1.4.4.min.js
1089 ms
util.share.js
548 ms
jquery.cookie.js
413 ms
util.fontsizeswitch.js
519 ms
jquery.watermark-3.0.8.min.js
539 ms
util.dropmenu.js
610 ms
spin.min.js
692 ms
jquery.carouFredSel-5.5.2-packed.js
1046 ms
withWatch.js
719 ms
ccm.base.css
555 ms
ccm.base.js
631 ms
view.css
689 ms
base.css
556 ms
share.css
567 ms
contents.css
854 ms
fontset.css
691 ms
withconc.css
736 ms
ga.js
71 ms
bg.png
371 ms
logo.gif
185 ms
b_h_faq.gif
176 ms
b_h_counter.gif
177 ms
b_h_lost.gif
191 ms
b_h_sitemap.gif
199 ms
b_home.png
348 ms
b_withcard.png
351 ms
b_card.png
366 ms
b_shopping.png
371 ms
b_cashing.png
395 ms
b_service.png
521 ms
b_apply.png
526 ms
b_sim.gif
547 ms
b_app.gif
550 ms
b_qa.gif
554 ms
b_store.gif
591 ms
sf.gif
692 ms
t_webservice.gif
700 ms
b_login.png
729 ms
b_new.png
732 ms
qrcode.gif
736 ms
banner_01.gif
787 ms
banner_02.gif
863 ms
2_withlink.gif
873 ms
kameitenkyoudou.gif
908 ms
saiyou.gif
909 ms
bc_about.png
916 ms
bc_about2.png
983 ms
bc_about3.png
1035 ms
red.gif
1046 ms
h_qa.gif
1089 ms
h_page.gif
1089 ms
h_topicsnews.gif
1099 ms
icon_new.gif
1178 ms
withWatch.json
1153 ms
__utm.gif
12 ms
b_list_new.gif
1086 ms
h_campaign.gif
1100 ms
b_list_camp.gif
1096 ms
h_info.gif
1098 ms
b_list_info.gif
1186 ms
h_use.gif
1041 ms
b_list_use.gif
1053 ms
bnr_izutsuya.gif
1092 ms
gopagetop.gif
1090 ms
search_btn.gif
1099 ms
copyright.gif
1184 ms
fontsize_t.gif
1039 ms
fontsize_b.gif
1051 ms
bg_menu.png
1092 ms
bg_webservice_head.gif
1090 ms
bg_webservice.gif
1098 ms
bullet_a.gif
1141 ms
bullet_b.gif
1059 ms
cover.png
1273 ms
bullet_submenu_blue.gif
1091 ms
bullet.gif
1088 ms
search_bg.gif
1097 ms
b_h_faq_2.gif
1122 ms
b_h_counter_2.gif
1062 ms
b_h_lost_2.gif
1129 ms
b_h_sitemap_2.gif
1093 ms
b_home_2.png
1105 ms
b_withcard_2.png
1158 ms
b_card_2.png
1116 ms
b_shopping_2.png
1131 ms
b_cashing_2.png
1133 ms
b_service_2.png
1091 ms
b_apply_2.png
1104 ms
b_sim_2.gif
1148 ms
b_app_2.gif
1095 ms
b_qa_2.gif
1111 ms
b_store_2.gif
1107 ms
b_login_2.png
1094 ms
b_new_2.png
1106 ms
b_list_new_2.gif
1140 ms
b_list_camp_2.gif
1074 ms
b_list_info_2.gif
1160 ms
b_list_use_2.gif
1147 ms
gopagetop_2.gif
1108 ms
bg_withwatch.gif
1105 ms
3_info_izutsuya659.gif
1302 ms
3_info_izutsuya659_a.gif
1070 ms
3_info_izutsuya659_b.gif
1153 ms
3_info_izutsuya656_a.gif
1152 ms
3_info_izutsuya656_b.gif
1108 ms
3_info_izutsuya656.gif
1124 ms
3_info_izutsuya643_a.gif
1154 ms
3_info_izutsuya643_b.gif
1179 ms
3_info_izutsuya643.gif
1162 ms
3_info_izutsuya663_a.gif
1109 ms
3_info_izutsuya663_b.gif
1139 ms
3_info_izutsuya663.gif
1111 ms
prev.gif
1070 ms
next.gif
1165 ms
tab01.gif
1122 ms
info_kamei1.png
1655 ms
info_kamei1.gif
1112 ms
info_kamei1_2.gif
1141 ms
tab02.gif
1078 ms
3_info_izutsuya675.gif
1171 ms
3_info_izutsuya675_a.gif
1106 ms
3_info_izutsuya675_b.gif
1106 ms
3_info_izutsuya670_a.gif
1146 ms
3_info_izutsuya670_b.gif
1157 ms
3_info_izutsuya670.gif
1205 ms
3_info_izutsuya671_a.gif
1181 ms
3_info_izutsuya671_b.gif
1100 ms
3_info_izutsuya671.gif
1140 ms
3_info_izutsuya672_a.gif
1186 ms
3_info_izutsuya672_b.gif
1257 ms
3_info_izutsuya672.gif
1217 ms
3_info_izutsuya674_a.gif
1184 ms
3_info_izutsuya674_b.gif
1136 ms
3_info_izutsuya674.gif
1203 ms
3_info_izutsuya669_a.gif
1255 ms
3_info_izutsuya669_b.gif
1247 ms
3_info_izutsuya669.gif
1194 ms
3_info_izutsuya673_a.gif
1114 ms
3_info_izutsuya673_b.gif
1128 ms
3_info_izutsuya673.gif
1201 ms
3_info_izutsuya6_a.gif
1223 ms
3_info_izutsuya6_a_2.gif
1231 ms
3_info_izutsuya6.gif
1201 ms
3_info_izutsuya4_a.gif
1115 ms
3_info_izutsuya4_a_2.gif
1121 ms
3_info_izutsuya4.gif
1216 ms
3_info_izutsuya5_a.gif
1214 ms
3_info_izutsuya5_a_2.gif
1222 ms
3_info_izutsuya5.gif
1208 ms
tab03.gif
1117 ms
print.css
183 ms
withcard.co.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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
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>).
withcard.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
withcard.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
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 Withcard.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 Withcard.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.
withcard.co.jp
Open Graph data is detected on the main page of Withcard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: