7.7 sec in total
1.2 sec
5.9 sec
582 ms
Visit yunishigawa.co.jp now to see the best up-to-date Yunishigawa content for Japan and also check out these interesting facts you probably never knew about yunishigawa.co.jp
彩り湯かしき花と華では、心づくしの5つのおもてなしの数々で旅の夢路を花咲かせます。公式サイトで予約いただくと7大特典付きとベストレート保証です。
Visit yunishigawa.co.jpWe analyzed Yunishigawa.co.jp page load time and found that the first response time was 1.2 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
yunishigawa.co.jp performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value22.4 s
0/100
25%
Value31.9 s
0/100
10%
Value460 ms
62/100
30%
Value1
2/100
15%
Value16.4 s
5/100
10%
1206 ms
357 ms
558 ms
1199 ms
402 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 91% of them (95 requests) were addressed to the original Yunishigawa.co.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Yunishigawa.co.jp.
Page size can be reduced by 153.4 kB (16%)
945.9 kB
792.5 kB
In fact, the total size of Yunishigawa.co.jp main page is 945.9 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. 35% of websites need less resources to load. Images take 792.0 kB which makes up the majority of the site volume.
Potential reduce by 33.2 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 33.2 kB or 76% of the original size.
Potential reduce by 53.3 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. Yunishigawa images are well optimized though.
Potential reduce by 46.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 46.1 kB or 53% of the original size.
Potential reduce by 20.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. Yunishigawa.co.jp needs all CSS files to be minified and compressed as it can save up to 20.8 kB or 86% of the original size.
Number of requests can be reduced by 25 (24%)
103
78
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yunishigawa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
yunishigawa.co.jp
1206 ms
import.css
357 ms
homepage.css
558 ms
jquery-1.3.2.min.js
1199 ms
jquery.scrollTo.js
402 ms
settings.js
424 ms
heightLine.js
534 ms
imgfade.js
602 ms
jqbookmark.js
635 ms
swf_top.js
716 ms
default.css
388 ms
common.css
441 ms
print.css
447 ms
search_hotelstory.js
453 ms
googleanalytics.js
302 ms
logo.jpg
606 ms
bn_hotspring.jpg
402 ms
bn_dining.jpg
603 ms
bn_rooms.jpg
534 ms
bn_appealpoints.jpg
677 ms
bn_hprivate.jpg
560 ms
bn_oneday.jpg
603 ms
bn_dish.jpg
1067 ms
st_recommended.gif
747 ms
st_best3.gif
803 ms
img_1359977077_3.jpg
805 ms
ic_pack.gif
806 ms
line_pack.gif
889 ms
img_1359976624_3.jpg
933 ms
img_1331972150_3.jpg
1203 ms
st_reccompack.gif
1006 ms
img_1368023705_3.jpg
1008 ms
img_1311564756_3.jpg
1310 ms
img_1368023208_3.jpg
1120 ms
st_newpack.gif
1209 ms
img_1457950429_3.jpg
1210 ms
img_1457950040_3.jpg
1244 ms
img_1428060467_3.jpg
1307 ms
st_news.gif
1405 ms
img_1458394152_4_t.jpg
1409 ms
img_1458266346_4_t.jpg
1410 ms
img_1458011523_4_t.jpg
1423 ms
img_1457953228_4_t.jpg
1493 ms
img_1457184524_4_t.jpg
1521 ms
img_1456659680_4_t.jpg
1604 ms
img_1456398583_4_t.jpg
1608 ms
img_1455457377_4_t.jpg
1610 ms
img_1455103591_4_t.jpg
1601 ms
img_1455076576_4_t.jpg
1679 ms
bn_benefits.jpg
1944 ms
sdk.js
163 ms
st_search.gif
1779 ms
ga.js
16 ms
73 ms
xd_arbiter.php
165 ms
xd_arbiter.php
288 ms
st_searchbycase.gif
1409 ms
btn_search_pack.gif
1281 ms
btn_search_room.gif
1256 ms
btn_packlist.gif
1269 ms
btn_resv_change.gif
1360 ms
btn_member.gif
1406 ms
btn_mbm_change.gif
1337 ms
btn_passlost.gif
1269 ms
bn_review.gif
1254 ms
img_resv_phone.gif
1357 ms
st_info.gif
1334 ms
btn_contact.gif
1324 ms
btn_access.gif
1281 ms
btn_sightseeing.gif
1209 ms
btn_faq.gif
1234 ms
btn_favourits.gif
1255 ms
bn_mobile.gif
1252 ms
bn_blog.jpg
1210 ms
bn_okami_blog.jpg
1207 ms
st_fb.png
1405 ms
line_fb.png
1186 ms
st_link.gif
1190 ms
img_yajirushi.gif
1276 ms
bn_kuriyama.gif
1209 ms
bn_weathernews.gif
1207 ms
ic_arrow_white.gif
1203 ms
logo_foot.gif
1252 ms
bg_flash.jpg
1513 ms
bg_gnav.jpg
1468 ms
gnav.jpg
1614 ms
bg_appeal.jpg
1217 ms
bg_contents.jpg
1208 ms
bg_pack.jpg
1243 ms
bg_img_pack.jpg
1337 ms
bg_news.gif
1240 ms
bg_search.jpg
1227 ms
bg_fb.gif
1365 ms
bg_link.gif
1617 ms
bg_fnav.jpg
1353 ms
fnav.gif
1276 ms
bg_menu_foot.jpg
1431 ms
bg_menu01.jpg
1353 ms
ic_arrow_pink.gif
1407 ms
bg_contact_foot.jpg
1608 ms
__utm.gif
27 ms
like.php
68 ms
wy1X4hBW7e7.js
303 ms
LVx-xkvaJ0b.png
336 ms
yunishigawa.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
yunishigawa.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
yunishigawa.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 Yunishigawa.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 Yunishigawa.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.
yunishigawa.co.jp
Open Graph description is not detected on the main page of Yunishigawa. 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: