6.8 sec in total
888 ms
5.5 sec
370 ms
Welcome to kansyokan.co.jp homepage info - get ready to check Kansyokan best content for Japan right away, or after learning these important things about kansyokan.co.jp
Yumemi no Yado Kansyokan in Mogami Town, Yamagata Prefecture, offers Yamagata delicacies unique to this gastronomic inn, including the best local produce and regional dishes. Relax in your room overlo...
Visit kansyokan.co.jpWe analyzed Kansyokan.co.jp page load time and found that the first response time was 888 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
kansyokan.co.jp performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value9.4 s
0/100
25%
Value22.3 s
0/100
10%
Value320 ms
76/100
30%
Value0.015
100/100
15%
Value13.2 s
12/100
10%
888 ms
317 ms
329 ms
349 ms
343 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 50% of them (68 requests) were addressed to the original Kansyokan.co.jp, 9% (12 requests) were made to Static.xx.fbcdn.net and 7% (9 requests) were made to Plugins.mixi.jp. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Kansyokan.co.jp.
Page size can be reduced by 455.3 kB (50%)
911.3 kB
456.0 kB
In fact, the total size of Kansyokan.co.jp main page is 911.3 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. 75% 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. Javascripts take 490.7 kB which makes up the majority of the site volume.
Potential reduce by 25.1 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 25.1 kB or 72% of the original size.
Potential reduce by 14.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. Kansyokan images are well optimized though.
Potential reduce by 349.1 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 349.1 kB or 71% of the original size.
Potential reduce by 66.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. Kansyokan.co.jp needs all CSS files to be minified and compressed as it can save up to 66.7 kB or 80% of the original size.
Number of requests can be reduced by 77 (57%)
134
57
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kansyokan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
kansyokan.co.jp
888 ms
import.css
317 ms
smartRollover.js
329 ms
swfobject_modified.js
349 ms
behavior.js
343 ms
jsapi
19 ms
blog_news.js
340 ms
egin1.0.js
207 ms
base.css
166 ms
contents.css
186 ms
home.css
181 ms
room.css
191 ms
spa.css
164 ms
cuisine.css
181 ms
access.css
184 ms
story.css
180 ms
sightseeing.css
324 ms
facilities.css
350 ms
about.css
354 ms
club.css
351 ms
pamphlet.css
352 ms
privacy.css
371 ms
faq.css
483 ms
ask.css
520 ms
special.css
523 ms
sitemap.css
525 ms
global.css
525 ms
hack.css
553 ms
plusone.js
94 ms
26 ms
default+en.css
15 ms
default+en.I.js
19 ms
base_bg.gif
473 ms
get_flash_player.gif
27 ms
head_logo.png
307 ms
head_b_reserve.gif
287 ms
n_room_off.gif
302 ms
n_spa_off.gif
304 ms
n_cuisine_off.gif
305 ms
n_facilities_off.gif
470 ms
n_story_off.gif
469 ms
n_sightseeing_off.gif
469 ms
n_access_off.gif
467 ms
bnr_cuisine.jpg
645 ms
bnr_rooms.jpg
940 ms
recommend_title.gif
653 ms
recommend_link.gif
667 ms
rec_img1.jpg
678 ms
rec_img6.jpg
699 ms
rec_img2.jpg
930 ms
rec_img4.jpg
953 ms
rec_img5.jpg
937 ms
news_title.gif
953 ms
btn_news.gif
954 ms
title_search.gif
1172 ms
btn_search.jpg
1170 ms
bnr_privilege.jpg
1121 ms
bnr_panf.gif
1171 ms
bnr_inq.gif
1169 ms
bnr_member.gif
1206 ms
bnr_shop.gif
1246 ms
pagetop.gif
1330 ms
foot_logo.png
1341 ms
foot_tel_02.gif
1332 ms
foot_b_reserve.gif
1330 ms
foot_inq.gif
1385 ms
foot_panf.gif
1402 ms
all.js
18 ms
head_bg.gif
1908 ms
flash_bg.jpg
2196 ms
widgets.js
214 ms
cb=gapi.loaded_0
136 ms
likebox.php
297 ms
recommend_bg.gif
1715 ms
recommend_point.gif
1269 ms
134 ms
xd_arbiter.php
52 ms
xd_arbiter.php
137 ms
tit_bg.jpg
1122 ms
410ucuAGgaJ.css
150 ms
tSbl8xBI27R.css
139 ms
1kPfZUdGrka.js
176 ms
Yuj_Y8xNH2C.js
200 ms
Mpe38fuBVZ2.js
144 ms
n8qIhCw3vMx.js
208 ms
plugins.js
526 ms
footer_bg.gif
1316 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
330 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
400 ms
cb=gapi.loaded_1
68 ms
fastbutton
295 ms
postmessageRelay
408 ms
like.php
401 ms
188230_449468711793074_663849798_n.jpg
351 ms
390840_217810811625533_1556652217_n.jpg
320 ms
12310699_10153251586393870_3735859784201980514_n.jpg
387 ms
11872_311106422370116_1011442261_n.jpg
396 ms
12745530_1665139483751298_4135346128972007958_n.jpg
404 ms
540441_100803570071110_2072189448_n.jpg
395 ms
wL6VQj7Ab77.png
170 ms
s7jcwEQH7Sx.png
171 ms
cb=gapi.loaded_0
153 ms
cb=gapi.loaded_1
141 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
316 ms
syndication
265 ms
345689471246794752
405 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
132 ms
8i5wLKr4CIi.js
176 ms
LVx-xkvaJ0b.png
119 ms
3193398744-postmessagerelay.js
240 ms
rpc:shindig_random.js
126 ms
VXcANLwwL5J.js
25 ms
AmlxWlqMvlv.js
24 ms
cb=gapi.loaded_0
4 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
15 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
18 ms
image_normal.jpg
379 ms
QfFS-z6z_normal.jpg
354 ms
CLhq_akVAAE6K4x.jpg:small
349 ms
Gfeeds
685 ms
favorite.pl
336 ms
jot.html
2 ms
mixi_check_entry.css
11 ms
errorreport.production.js
297 ms
json.js
301 ms
underscore-string-1.3.3-2.0.0-compress.js
303 ms
namespace-brook-compress.js
308 ms
prototype-effects-1.6.1-1.8.3-compress.js
446 ms
mixi.js
311 ms
favorite.production.js
588 ms
jquery-1.7.1.min-noconflict-compress.js
736 ms
news_arrow.gif
178 ms
analytics.js
31 ms
comment001.gif
10 ms
favorite_button004.png
6 ms
comment_content_top001.gif
302 ms
kansyokan.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.
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
kansyokan.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
kansyokan.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
EN
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kansyokan.co.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Kansyokan.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
kansyokan.co.jp
Open Graph description is not detected on the main page of Kansyokan. 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: