13.1 sec in total
567 ms
12.3 sec
253 ms
Click here to check amazing Chuo Contact content for Japan. Otherwise, check out these important facts you probably never knew about chuo-contact.co.jp
中央コンタクト・フラワーコンタクトは全国160店舗、会員数250万人以上のコンタクトレンズ専門店。国内外全メーカーの商品を取り扱い。ケア用品まで豊富な品揃えが御座います。お得な割引クーポンやキャンペーン多数掲載中!
Visit chuo-contact.co.jpWe analyzed Chuo-contact.co.jp page load time and found that the first response time was 567 ms and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
chuo-contact.co.jp performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value9.2 s
1/100
25%
Value10.1 s
9/100
10%
Value340 ms
75/100
30%
Value0.221
56/100
15%
Value15.4 s
7/100
10%
567 ms
1259 ms
1175 ms
1228 ms
532 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 67% of them (90 requests) were addressed to the original Chuo-contact.co.jp, 5% (7 requests) were made to Apis.google.com and 3% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Chuo-contact.co.jp.
Page size can be reduced by 370.3 kB (15%)
2.4 MB
2.0 MB
In fact, the total size of Chuo-contact.co.jp main page is 2.4 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. 50% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 45.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. 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 45.7 kB or 78% of the original size.
Potential reduce by 3.0 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. Chuo Contact images are well optimized though.
Potential reduce by 265.6 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 265.6 kB or 70% of the original size.
Potential reduce by 56.0 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. Chuo-contact.co.jp needs all CSS files to be minified and compressed as it can save up to 56.0 kB or 84% of the original size.
Number of requests can be reduced by 36 (28%)
128
92
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chuo Contact. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
chuo-contact.co.jp
567 ms
www.chuo-contact.co.jp
1259 ms
content.css
1175 ms
jquery.js
1228 ms
content.js
532 ms
adlpo.js
968 ms
hlogo.gif
509 ms
slide1.jpg
2010 ms
slide2.jpg
2012 ms
slide3.jpg
2113 ms
slide4.jpg
2125 ms
slide5.jpg
2257 ms
thumb1.jpg
1242 ms
thumb2.jpg
1926 ms
thumb3.jpg
2614 ms
thumb4.jpg
2713 ms
thumb5.jpg
2735 ms
bnr01.jpg
3268 ms
bnr02.jpg
3284 ms
title1.gif
2618 ms
title2.gif
2986 ms
coupon.gif
3406 ms
topt.gif
3155 ms
title10.gif
3254 ms
tcolumn.gif
3986 ms
title3.gif
3516 ms
115.jpg
3822 ms
35.jpg
3885 ms
110.jpg
3921 ms
33.jpg
3986 ms
32.jpg
4276 ms
45.jpg
4431 ms
107.jpg
4471 ms
41.jpg
4515 ms
51.jpg
4807 ms
53.jpg
4830 ms
56.jpg
4861 ms
116.jpg
4984 ms
118.jpg
5097 ms
121.jpg
5184 ms
gtm.js
62 ms
92.jpg
5328 ms
c.js
589 ms
conversion_async.js
17 ms
www.chuo-contact.co.jp.js
349 ms
conversion.js
513 ms
s_retargeting.js
568 ms
44 ms
48 ms
42 ms
45 ms
40 ms
34 ms
105.jpg
5056 ms
basecamp.js
18 ms
96.jpg
4937 ms
analytics.js
30 ms
plusone.js
90 ms
tag.js
7 ms
fbds.js
79 ms
widgets.js
106 ms
all.js
201 ms
tag
11 ms
ecommerce.js
11 ms
collect
11 ms
collect
72 ms
148 ms
cb=gapi.loaded_0
35 ms
cb=gapi.loaded_1
54 ms
fastbutton
100 ms
ga-audiences
27 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
182 ms
postmessageRelay
82 ms
cb=gapi.loaded_0
37 ms
cb=gapi.loaded_1
36 ms
48 ms
xd_arbiter.php
138 ms
xd_arbiter.php
269 ms
api.js
33 ms
core:rpc:shindig.random:shindig.sha1.js
79 ms
2536007149-postmessagerelay.js
58 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
45 ms
jot
80 ms
title4.gif
4140 ms
title5.gif
3603 ms
title6.gif
3553 ms
more.gif
3698 ms
sns_line.png
3620 ms
flogo.gif
3868 ms
headerbg.gif
3579 ms
favbg.gif
3522 ms
favbtn.gif
3462 ms
arrow.gif
3381 ms
sinput.gif
3338 ms
srbtn.gif
3201 ms
fontbg.gif
3197 ms
fontbtn.gif
3161 ms
menu.gif
3528 ms
storebg.gif
3568 ms
prodbg.gif
3694 ms
suppbg.gif
3007 ms
commbg.gif
2913 ms
bg.gif
3057 ms
thumbbg.gif
2970 ms
shadow.gif
3128 ms
thumbborder.png
3176 ms
mainmap.gif
3332 ms
topbnrbg.gif
3163 ms
topbnrbtn.gif
2964 ms
toptabs.gif
3326 ms
shadow2.gif
2685 ms
tabprice.gif
2874 ms
map1.gif
3142 ms
map2.gif
2868 ms
map3.gif
2816 ms
map4.gif
2776 ms
map6.gif
2865 ms
map7.gif
2826 ms
map8.gif
2824 ms
map9.gif
3000 ms
prev.png
2796 ms
next.png
2830 ms
prodmenu.gif
3335 ms
shadow3.gif
2825 ms
tfmenu.gif
3139 ms
hshadow.png
2666 ms
fshadow.png
2706 ms
footerbg.gif
2748 ms
farrow.gif
2836 ms
ptop.gif
2880 ms
21 ms
like.php
53 ms
vpc6VNjRPXV.js
282 ms
LVx-xkvaJ0b.png
314 ms
chuo-contact.co.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
chuo-contact.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
Issues were logged in the Issues panel in Chrome Devtools
chuo-contact.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Chuo-contact.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 Chuo-contact.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.
chuo-contact.co.jp
Open Graph description is not detected on the main page of Chuo Contact. 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: