12.3 sec in total
2.6 sec
9.2 sec
549 ms
Visit kanahashi.co.jp now to see the best up-to-date Kanahashi content for Japan and also check out these interesting facts you probably never knew about kanahashi.co.jp
Visit kanahashi.co.jpWe analyzed Kanahashi.co.jp page load time and found that the first response time was 2.6 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
kanahashi.co.jp performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value13.5 s
0/100
25%
Value11.5 s
5/100
10%
Value240 ms
85/100
30%
Value0.554
13/100
15%
Value10.9 s
21/100
10%
2589 ms
376 ms
964 ms
581 ms
420 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 97% of them (149 requests) were addressed to the original Kanahashi.co.jp, 1% (2 requests) were made to Tr.find-a.jp and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Kanahashi.co.jp.
Page size can be reduced by 71.4 kB (27%)
260.6 kB
189.3 kB
In fact, the total size of Kanahashi.co.jp main page is 260.6 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. 60% of websites need less resources to load. Images take 172.6 kB which makes up the majority of the site volume.
Potential reduce by 31.6 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 31.6 kB or 78% of the original size.
Potential reduce by 15.4 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. Kanahashi images are well optimized though.
Potential reduce by 5.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 5.4 kB or 22% of the original size.
Potential reduce by 18.9 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. Kanahashi.co.jp needs all CSS files to be minified and compressed as it can save up to 18.9 kB or 85% of the original size.
Number of requests can be reduced by 24 (16%)
153
129
The browser has sent 153 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kanahashi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
kanahashi.co.jp
2589 ms
reset.css
376 ms
interface2.css
964 ms
AC_RunActiveContent.js
581 ms
rollover.js
420 ms
getseal
151 ms
tl.php
618 ms
backgrund.gif
189 ms
header_bg.jpg
386 ms
header_logo.gif
212 ms
header_phone2.gif
372 ms
hd_0287.gif
195 ms
btn_01_o.gif
376 ms
btn_02.gif
387 ms
btn_03.gif
603 ms
btn_04.gif
416 ms
btn_05.gif
556 ms
btn_06.gif
562 ms
btn_07.gif
575 ms
side_bg_red.gif
577 ms
m_regist.gif
624 ms
btn_regist.gif
740 ms
m_member.gif
747 ms
btn_login.gif
766 ms
viewcart.gif
769 ms
otodoke.gif
800 ms
btn_staffdiary.gif
830 ms
m_ranking.gif
923 ms
pre4056_56d4c45a7c585_3.gif
934 ms
pre4170_56ae8c744c8eb_3.gif
958 ms
pre1047_56332869abc3c_3.gif
1193 ms
pre4078_55f628839efc6_3.gif
1400 ms
pre1127_4ddde6b08fda8_1.jpg
1454 ms
side_n_118s3.gif
1109 ms
0a_side_8.gif
1307 ms
sdn02_01091.gif
1150 ms
side_osusume_3.gif
1663 ms
sdn02_01106.gif
1343 ms
sdn02_01094.gif
1577 ms
sdn02_01071.gif
1496 ms
sdn02_01173.gif
1727 ms
sdn02_0363.gif
2402 ms
tl.php
652 ms
sdn02_01224.gif
1650 ms
ga.js
29 ms
__utm.gif
11 ms
sdn02_01225.gif
1506 ms
1i1.gif
1970 ms
3i1.gif
1671 ms
sdn02_044.gif
1672 ms
gotyuui1.gif
1507 ms
side_n_068s3.gif
1547 ms
side_n_075s3.gif
1704 ms
icn_03a3.gif
1651 ms
sdn02_065.gif
1758 ms
sdn02_01160.gif
1851 ms
0a_side_11.gif
1682 ms
sdn02_01114.gif
1719 ms
0a_side_13.gif
1755 ms
onlinetrust.jpg
2006 ms
title_news.gif
1765 ms
icn_072.gif
1759 ms
icn_083.gif
1780 ms
icn_091.gif
1840 ms
icn_148.gif
1797 ms
icn_059.gif
1882 ms
icn_089.gif
1774 ms
top_06_283.gif
2188 ms
top_06_263.gif
2008 ms
top_06_172.gif
1906 ms
top_06_258.gif
1851 ms
top_04_0487.gif
1697 ms
top_06_277.gif
2026 ms
top_06_278.gif
2124 ms
top_04_0526.gif
1752 ms
top_06_209.gif
1924 ms
top_06_196.gif
1719 ms
top_04_0344.gif
1739 ms
top_06_279.gif
1859 ms
top_06_280.gif
1953 ms
top_06_198.gif
2016 ms
top_06_259.gif
2023 ms
top_06_247.gif
1881 ms
top_04_0348.gif
1787 ms
top_05_0373.gif
1786 ms
top_06_167.gif
1985 ms
top_05_0347.gif
1984 ms
top_05_0485.gif
2004 ms
top_05_0344.gif
1922 ms
top_05_0345.gif
1918 ms
top_05_0346.gif
1838 ms
top_04_0346.gif
1914 ms
top_05_0667.gif
1889 ms
top_05_0283.gif
1863 ms
top_04_0347.gif
1874 ms
top_05_0282.gif
1818 ms
top_05_0280.gif
1878 ms
top_05_0281.gif
1880 ms
top_06_226.gif
1838 ms
top_05_0541.gif
2030 ms
title_todaysprodust.gif
1848 ms
osupre1341_562743dddbeda_3.gif
1815 ms
osupre1391_4ce0e297a9e6c_1.jpg
1880 ms
osupre3864_54e514505b9ff_3.gif
1739 ms
title_pictup.gif
1664 ms
pre2560_546c43c4226ed_3.gif
1666 ms
pre157_540cf653ccb1a_3.gif
1683 ms
pre3478_4f1e61384c8c3_7.gif
1679 ms
pre4090_561db887bbfb6_3.gif
1676 ms
m_knowledge.gif
1604 ms
knowledge_btn01.gif
1506 ms
knowledge_btn02.gif
1526 ms
m_net_auction.gif
1507 ms
net_auction_ph.jpg
1542 ms
net_auction_btn.gif
1490 ms
title_abotus.jpg
1392 ms
ph_aboutus.jpg
1367 ms
btn_ussecret.gif
1354 ms
btn_usshop.gif
1364 ms
btn_usstaff.gif
1467 ms
pay_hikikae.gif
1442 ms
pay_bank.gif
1185 ms
pay_JNB.gif
1183 ms
pay_visa_n.jpg
1169 ms
pay_master_n.jpg
1175 ms
pay_jcb_n.jpg
1253 ms
pay_diners_n.jpg
1231 ms
pay_cedyna_omc_cf.jpg
1205 ms
pay_aeon_n.jpg
1191 ms
pay_nicos_n.jpg
1176 ms
pay_jaccs_n.jpg
1169 ms
pay_circleksunks_n.jpg
1249 ms
pay_daily_n.jpg
1212 ms
pay_ministop_n.jpg
1213 ms
pay_familymart_n.jpg
1199 ms
pay_seicomart_new.gif
1161 ms
pay_lawson_n.jpg
1129 ms
pay_seveneleven.gif
1165 ms
bontents_bg.gif
1157 ms
ico_news.gif
1205 ms
knowledge_bg.jpg
1192 ms
net_auction_btm.gif
1179 ms
aboutshop_bg.gif
1131 ms
aboutshop_btm.gif
1143 ms
bg_address.gif
1160 ms
btn_02_o.gif
190 ms
btn_03_o.gif
195 ms
btn_04_o.gif
210 ms
btn_05_o.gif
187 ms
btn_06_o.gif
195 ms
btn_07_o.gif
203 ms
btn_regist_o.gif
373 ms
btn_login_o.gif
377 ms
viewcart_o.gif
386 ms
kanahashi.co.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
kanahashi.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
kanahashi.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 Kanahashi.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 Kanahashi.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.
kanahashi.co.jp
Open Graph description is not detected on the main page of Kanahashi. 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: