8.3 sec in total
903 ms
7.2 sec
266 ms
Click here to check amazing Hundredstay content for Japan. Otherwise, check out these important facts you probably never knew about hundredstay.jp
1泊から宿泊可の高級家具付きサービスアパートメントハンドレッドステイ東京新宿ではお客様のご要望にお応えした様々な部屋を御用意させて頂いております。
Visit hundredstay.jpWe analyzed Hundredstay.jp page load time and found that the first response time was 903 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hundredstay.jp performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value8.5 s
2/100
25%
Value4.9 s
65/100
10%
Value100 ms
98/100
30%
Value0.311
37/100
15%
Value7.5 s
47/100
10%
903 ms
354 ms
510 ms
349 ms
511 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 81% of them (83 requests) were addressed to the original Hundredstay.jp, 9% (9 requests) were made to Apis.google.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Hundredstay.jp.
Page size can be reduced by 109.1 kB (13%)
844.3 kB
735.2 kB
In fact, the total size of Hundredstay.jp main page is 844.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. 55% of websites need less resources to load. Images take 713.1 kB which makes up the majority of the site volume.
Potential reduce by 15.9 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 15.9 kB or 74% of the original size.
Potential reduce by 18.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. Hundredstay images are well optimized though.
Potential reduce by 54.3 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 54.3 kB or 65% of the original size.
Potential reduce by 20.2 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. Hundredstay.jp needs all CSS files to be minified and compressed as it can save up to 20.2 kB or 79% of the original size.
Number of requests can be reduced by 49 (49%)
101
52
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hundredstay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
hundredstay.jp
903 ms
import.css
354 ms
header.css
510 ms
footer.css
349 ms
thickbox.css
511 ms
styleswitcher.js
342 ms
rollover.js
678 ms
jsapi
19 ms
jquery.slides.js
845 ms
thickbox.js
854 ms
reset.css
522 ms
font.css
486 ms
style.css
651 ms
common.css
640 ms
jquery.min.js
32 ms
plusone.js
229 ms
img_logo.png
570 ms
btn_upper_07.png
597 ms
btn_upper_12.gif
570 ms
btn_upper_13.gif
570 ms
btn_upper_08.gif
384 ms
btn_upper_09.gif
414 ms
btn_upper_10.gif
743 ms
btn_upper_11.gif
731 ms
btn_fb_link.png
901 ms
btn_upper_01.png
913 ms
btn_upper_02.png
910 ms
btn_upper_03.png
925 ms
btn_upper_04.png
1097 ms
btn_upper_05.png
1108 ms
btn_upper_06.png
1256 ms
img_mainphoto2.jpg
2929 ms
btn_main01.png
1584 ms
btn_main02.png
1643 ms
img_title_01.png
1451 ms
btn_news.png
1431 ms
img_news_under.png
1576 ms
btn_faq.gif
1773 ms
img_title_02.png
1773 ms
btn_plan01.gif
1907 ms
plan-therapy.jpg
2264 ms
plan-ecology.jpg
2330 ms
btn_plan.gif
2121 ms
img_title_03b.png
2181 ms
img_style_title01.png
2254 ms
img_style_lead01.png
2461 ms
img_style_photo01.jpg
2850 ms
btn_under.gif
2574 ms
img_style_title02.png
2600 ms
img_style_lead02.png
2661 ms
img_style_photo02.jpg
2956 ms
img_under_title.png
2892 ms
gtm.js
154 ms
analytics.js
67 ms
like.php
374 ms
cb=gapi.loaded_0
63 ms
cb=gapi.loaded_1
95 ms
fastbutton
135 ms
collect
45 ms
postmessageRelay
124 ms
rs=AGLTcCNm3zONMmI-Y35gAfHAUpOk7SvjgQ
45 ms
news.html
2774 ms
img_header_back.gif
2602 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
42 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
179 ms
3193398744-postmessagerelay.js
125 ms
rpc:shindig_random.js
82 ms
img_content_back.gif
2639 ms
img_news_upper.png
2669 ms
img_news_middle.png
2719 ms
fy8tT2klpgR.js
65 ms
LVx-xkvaJ0b.png
68 ms
img_plan_back.gif
2733 ms
cb=gapi.loaded_0
20 ms
img_under_back01.png
2627 ms
img_style_back01.png
2749 ms
img_style_back02.png
2624 ms
img_under_back02.png
2656 ms
img_footer_back.gif
2710 ms
loadingAnimation.gif
2890 ms
news.css
708 ms
btn_upper_07_on.png
335 ms
btn_upper_12_on.gif
573 ms
btn_upper_13_on.gif
576 ms
btn_upper_08_on.gif
414 ms
btn_upper_09_on.gif
413 ms
btn_upper_10_on.gif
419 ms
btn_upper_11_on.gif
668 ms
btn_fb_link_on.png
741 ms
btn_upper_01_on.png
1018 ms
btn_upper_02_on.png
1028 ms
btn_upper_03_on.png
1011 ms
btn_upper_04_on.png
1015 ms
btn_upper_05_on.png
1019 ms
btn_upper_06_on.png
1059 ms
btn_main01_on.png
1647 ms
btn_main02_on.png
1678 ms
btn_news_on.png
1350 ms
btn_faq_on.gif
1365 ms
btn_plan01_on.gif
1374 ms
btn_plan_on.gif
1424 ms
btn_under_on.gif
1671 ms
hundredstay.jp accessibility score
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
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.
hundredstay.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
Browser errors were logged to the console
hundredstay.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 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 Hundredstay.jp 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 Hundredstay.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.
hundredstay.jp
Open Graph description is not detected on the main page of Hundredstay. 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: