11.8 sec in total
1.4 sec
9.8 sec
653 ms
Visit kanape-yokohama.com now to see the best up-to-date Kanape Yokohama content for Japan and also check out these interesting facts you probably never knew about kanape-yokohama.com
かなっぺは神奈川県の様々なジャンルのお店のチラシ、クーポン情報が満載!
Visit kanape-yokohama.comWe analyzed Kanape-yokohama.com page load time and found that the first response time was 1.4 sec and then it took 10.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.
kanape-yokohama.com performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value12.1 s
0/100
25%
Value11.9 s
4/100
10%
Value550 ms
53/100
30%
Value0.002
100/100
15%
Value11.0 s
21/100
10%
1369 ms
290 ms
449 ms
465 ms
11 ms
Our browser made a total of 177 requests to load all elements on the main page. We found that 53% of them (94 requests) were addressed to the original Kanape-yokohama.com, 11% (20 requests) were made to Pbs.twimg.com and 5% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Kanape-yokohama.com.
Page size can be reduced by 956.5 kB (34%)
2.8 MB
1.8 MB
In fact, the total size of Kanape-yokohama.com main page is 2.8 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 44.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 44.6 kB or 76% of the original size.
Potential reduce by 637.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. Obviously, Kanape Yokohama needs image optimization as it can save up to 637.7 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 115.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 115.4 kB or 47% of the original size.
Potential reduce by 158.8 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. Kanape-yokohama.com needs all CSS files to be minified and compressed as it can save up to 158.8 kB or 90% of the original size.
Number of requests can be reduced by 56 (32%)
173
117
The browser has sent 173 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kanape Yokohama. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
kanape-yokohama.com
1369 ms
index.css
290 ms
footer.css
449 ms
common.js
465 ms
jquery-1.10.2.js
11 ms
xdr.js
491 ms
heightLine.js
472 ms
async-script.js
515 ms
top.css
586 ms
layout.css
731 ms
jquery.ui.core.css
736 ms
jquery.ui.tabs.css
782 ms
jquery.cookie.js
769 ms
jquery-ui.js
16 ms
adsbygoogle.js
15 ms
common.css
737 ms
widgets.js
24 ms
plusone.js
216 ms
like.php
167 ms
bnr_2_20150701162725965.png
423 ms
logoBg.png
361 ms
search.png
359 ms
searchC.jpg
362 ms
btnSearch.png
407 ms
nav01.png
344 ms
nav02.png
670 ms
nav03.png
647 ms
nav04.png
674 ms
nav05.png
625 ms
top.png
850 ms
top.png
724 ms
top.png
994 ms
top.png
1024 ms
top.png
1516 ms
top.png
1027 ms
top.png
1025 ms
map_20150709_142450765.jpg
1225 ms
cms_20151027_110938100.jpg
1620 ms
cms_20150806_144939648.jpg
1591 ms
cms_20150806_145117741.jpg
1880 ms
cms_20150806_145217681.jpg
1620 ms
cms_20150629_120111158.jpg
1520 ms
cms_20151027_175413361.jpg
2282 ms
A4BC2D0E38FE6F0C79EA31F9CA5B3920.jpg
2005 ms
FD69823EA62DAE721C75620A325F837B.jpg
1868 ms
B58E3C64CE8BE9EAD702B1B1487CF856.jpg
1903 ms
8388157001CC885C95F555E884A44B35.jpg
2776 ms
05CBE5B41C6C038929075714768EB045.jpg
2896 ms
F8D5DDC1FFBF2ABC7185A105C612AFD3.jpg
2186 ms
writer.jpg
2375 ms
jimoneta.jpg
2484 ms
cms_20150924_145522415.jpg
3233 ms
to-shonan_l.gif
2550 ms
to-sagami.gif
2652 ms
cms_20151125_113556463.jpg
2960 ms
ca-pub-8976746382469102.js
187 ms
zrt_lookup.html
185 ms
show_ads_impl.js
130 ms
qeKvIRsJabD.js
260 ms
LVx-xkvaJ0b.png
272 ms
cb=gapi.loaded_0
110 ms
cb=gapi.loaded_1
129 ms
fastbutton
186 ms
analytics.js
122 ms
js
775 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
169 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
169 ms
ads
329 ms
osd.js
76 ms
ads
329 ms
2705 ms
image.php
3020 ms
image.php
3630 ms
postmessageRelay
114 ms
collect
38 ms
image.php
3398 ms
cb=gapi.loaded_0
47 ms
cb=gapi.loaded_1
37 ms
image.php
3287 ms
image.php
3643 ms
collect
81 ms
syndication
110 ms
658892984885219328
218 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
26 ms
3193398744-postmessagerelay.js
39 ms
rpc:shindig_random.js
76 ms
cb=gapi.loaded_0
6 ms
s_0RQ5KKaoTA_1363564438.html
56 ms
image.php
3341 ms
5849029694711780155
49 ms
abg.js
58 ms
m_js_controller.js
83 ms
googlelogo_color_112x36dp.png
40 ms
ico_star_5.png
2993 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
12 ms
0_P7cjNgCh.jpg
433 ms
dvtp_src.js
423 ms
creative_add_on.js
422 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
14 ms
ico_star_4.png
3302 ms
cms_20150924_173228714.jpg
3530 ms
EYxn8m82_normal.jpg
337 ms
CdeFrrBUMAACeFI.jpg:small
354 ms
CdeErosVIAAsxbS.jpg:small
336 ms
Cclpr01UcAAJSMo.jpg:small
414 ms
CbPCYU9UEAAUPT8.jpg:small
412 ms
Ca2O6HpXEAEumeA.jpg:small
411 ms
CZnex2VWcAE2BIX.jpg:small
413 ms
CZjwpnuVIAAOC-N.jpg:small
511 ms
CZO_TflWkAAIvSa.jpg:small
510 ms
CZJumz7UsAA676x.jpg:small
625 ms
CY-8ZVvUAAEn1lA.jpg:small
512 ms
CYvrni6UAAAJxOi.jpg:small
540 ms
CYq1Xp6UwAErwwC.jpg:small
513 ms
CYpokuiU0AAOD05.jpg:small
623 ms
CYmE7kgU0AAu5Sj.jpg:small
533 ms
CYL8f2TU0AA3eiR.jpg:small
642 ms
CYBaZ02UsAAjoA3.jpg:small
641 ms
CYBaUVLUsAAxSez.jpg:small
650 ms
CYBYpmrVAAAaoED.jpg:small
723 ms
CX8uJg-UEAEwMPh.jpg:small
653 ms
x_button_blue2.png
280 ms
s
277 ms
image.php
4079 ms
cms_20150924_200504573.png
3326 ms
cms_20150924_172751104.gif
4553 ms
481 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
25 ms
cms_20150929_174617793.jpg
3623 ms
3.png
3505 ms
b1.jpg
3467 ms
dvtp_src_internal26.js
28 ms
surly.js
141 ms
dvtp_src.js
109 ms
t2tv7.html
209 ms
visit.js
148 ms
b2.jpg
3330 ms
ba.html
100 ms
4.gif
120 ms
visit.js
45 ms
jot.html
19 ms
2532.js
54 ms
event.gif
75 ms
avs5639.js
46 ms
event.gif
87 ms
event.jpg
32 ms
box_19_top-right.png
31 ms
ci.png
54 ms
digest.jpg
3281 ms
digest.jpg
3282 ms
digest.jpg
3261 ms
digest.jpg
3302 ms
digest.JPG
3482 ms
itemBackground.png
3582 ms
shopSearchBg.png
3523 ms
mapTitBg.png
3658 ms
mapSearchIco01.png
3876 ms
presentTitBg.png
3387 ms
infoTitBg.png
3393 ms
icoListBtn02.png
3344 ms
activeview
15 ms
tipsTitBg.png
3822 ms
icoListBtn03.png
3307 ms
newsTitBg.png
3221 ms
flyerTitBg.png
3167 ms
bbsTitBg.png
3411 ms
icoGood.gif
3196 ms
reviewTitBg.png
3145 ms
newshopTitBg.png
3625 ms
rankTitBg.png
3058 ms
icoRank.jpg
2813 ms
linkTitBg.png
2800 ms
link2TitBg.png
3458 ms
noImage.png
2617 ms
sn_2016030912291869.JPG
3048 ms
sn_20160108172918835.JPG
3331 ms
icoNew.gif
2733 ms
kanape-yokohama.com 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-*] attributes do not match their roles
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.
Definition list items are not wrapped in <dl> elements
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
Image elements do not have [alt] attributes
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
kanape-yokohama.com 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
kanape-yokohama.com 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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kanape-yokohama.com 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 Kanape-yokohama.com 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.
kanape-yokohama.com
Open Graph data is detected on the main page of Kanape Yokohama. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: