8.8 sec in total
942 ms
6.6 sec
1.3 sec
Visit hotelstork.jp now to see the best up-to-date Hotelstork content for Japan and also check out these interesting facts you probably never knew about hotelstork.jp
那覇市の新都心の中心で、ビジネス、レジャー、お買い物などお客様の様々なニーズに合わせてご利用いただけるお気軽ホテルとして生まれました。宿泊などの費用をできるだけ抑えた分、お食事や、お買いものなどでプラスアルファのお楽しみ。
Visit hotelstork.jpWe analyzed Hotelstork.jp page load time and found that the first response time was 942 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hotelstork.jp performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value7.0 s
6/100
25%
Value6.2 s
44/100
10%
Value180 ms
92/100
30%
Value0.08
94/100
15%
Value6.7 s
56/100
10%
942 ms
323 ms
516 ms
680 ms
682 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 90% of them (86 requests) were addressed to the original Hotelstork.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 (2.2 sec) relates to the external source 489pro.com.
Page size can be reduced by 284.0 kB (13%)
2.2 MB
1.9 MB
In fact, the total size of Hotelstork.jp main page is 2.2 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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 28.4 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 28.4 kB or 76% of the original size.
Potential reduce by 58.2 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. Hotelstork images are well optimized though.
Potential reduce by 148.8 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 148.8 kB or 69% of the original size.
Potential reduce by 48.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. Hotelstork.jp needs all CSS files to be minified and compressed as it can save up to 48.7 kB or 88% of the original size.
Number of requests can be reduced by 28 (30%)
93
65
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hotelstork. 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 4 to 1 for CSS and as a result speed up the page load time.
hotelstork.jp
942 ms
default.css
323 ms
common.css
516 ms
homepage.css
680 ms
camera.css
682 ms
jquery-1.7.2.min.js
1131 ms
common.js
344 ms
analytics_hs.js
353 ms
jquery.easing.1.3.js
518 ms
heightLine.js
522 ms
jquery.fitted.js
522 ms
search.js
688 ms
camera.min.js
902 ms
top_ajax.js
688 ms
analytics.js
94 ms
logo.png
263 ms
btn_search.png
277 ms
btn_planlist.png
260 ms
st_intro.png
278 ms
st_intro02.png
277 ms
img_intro.png
1050 ms
st_point.png
417 ms
img_point01.png
1426 ms
img_pt01_wifi.png
465 ms
ic01.png
472 ms
st_point01.png
463 ms
ic02.png
663 ms
img_acc.jpg
667 ms
txt_sig.png
665 ms
ic03.png
665 ms
img_reasonable.jpg
719 ms
txt_reasonable.png
738 ms
ic04.png
739 ms
img_woman.jpg
737 ms
txt_woman.png
850 ms
ic05.png
920 ms
img_facilities.jpg
916 ms
txt_facilities.png
917 ms
st_news.png
1012 ms
2_20151221UfFMhzPt.jpg
1061 ms
st_info.png
1053 ms
bn_fb.jpg
1059 ms
bn_shunkashuto.gif
1192 ms
sst_mobile.gif
1212 ms
img_qr.gif
1235 ms
btn_pagetop.gif
1243 ms
f_logo.png
1238 ms
fnav_reserve.png
1379 ms
fnav_confirm.png
1404 ms
fnav_cancel.png
1407 ms
sdk.js
249 ms
fixnav_reserve.png
1370 ms
bg_bestrate.png
1181 ms
ic_square.png
1298 ms
ic_arrow_right.png
1333 ms
fixnav_tel.png
1332 ms
fixnav_english.png
1331 ms
collect
99 ms
bg_gnav.png
1145 ms
gnav_roo.png
1148 ms
gnav_fac.png
1260 ms
258 ms
gnav_sta.png
1277 ms
yproTopPlan.php
1727 ms
gnav_acc.png
1117 ms
gnav_sig.png
1124 ms
xd_arbiter.php
120 ms
xd_arbiter.php
196 ms
gnav_faq.png
1072 ms
gnav_new.png
1182 ms
gnav_pla.png
1215 ms
gnav_air.png
1218 ms
bg_btn_plan.jpg
1208 ms
like.php
96 ms
ic_arrow_white.png
1098 ms
ZJkxn0orVLU.js
203 ms
LVx-xkvaJ0b.png
223 ms
bg_point.jpg
1946 ms
ic_list.png
1193 ms
ic_triangle.png
1193 ms
bg_line_double.png
1116 ms
bg_line_footer.png
1098 ms
camera-loader.gif
1233 ms
camera_thumb.png
1226 ms
img_slide01.jpg
1604 ms
404.php
235 ms
404.php
290 ms
image_20160102211344_2.jpg
2165 ms
st_recommend.png
359 ms
ic_ichioshi.png
361 ms
bn_woman.png
359 ms
bn_one.png
523 ms
bn_early.png
616 ms
bn_day.png
659 ms
bn_stay.png
655 ms
img_slide02.jpg
692 ms
hotelstork.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
hotelstork.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hotelstork.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotelstork.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 Hotelstork.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.
hotelstork.jp
Open Graph data is detected on the main page of Hotelstork. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: