25.4 sec in total
519 ms
22.1 sec
2.8 sec
Click here to check amazing Ybht content for Japan. Otherwise, check out these important facts you probably never knew about ybht.co.jp
みなとみらい駅直結。クイーンズスクエア横浜内に位置する「横浜ベイホテル東急」の公式サイト。人気レストランや横浜の美しい夜景、オーシャンビューなど心を尽くしたおもてなしで皆様をお迎えいたします。
Visit ybht.co.jpWe analyzed Ybht.co.jp page load time and found that the first response time was 519 ms and then it took 24.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
ybht.co.jp performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value0
0/100
25%
Value14.3 s
1/100
10%
Value1,640 ms
11/100
30%
Value0.191
64/100
15%
Value23.7 s
1/100
10%
519 ms
1250 ms
671 ms
502 ms
32 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 70% of them (73 requests) were addressed to the original Ybht.co.jp, 4% (4 requests) were made to Platform.twitter.com and 4% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Tripadvisor.com.
Page size can be reduced by 681.6 kB (14%)
4.8 MB
4.2 MB
In fact, the total size of Ybht.co.jp main page is 4.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. 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. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 132.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 132.6 kB or 80% of the original size.
Potential reduce by 59.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. Ybht images are well optimized though.
Potential reduce by 286.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 286.3 kB or 59% of the original size.
Potential reduce by 203.4 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. Ybht.co.jp needs all CSS files to be minified and compressed as it can save up to 203.4 kB or 90% of the original size.
Number of requests can be reduced by 28 (29%)
98
70
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ybht. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
ybht.co.jp
519 ms
ybht.co.jp
1250 ms
layout.css
671 ms
colorbox.css
502 ms
swiper-bundle.min.css
32 ms
style.css
862 ms
cookieconsent.min.css
40 ms
animate.css
891 ms
top.css
892 ms
mt_plan.css
667 ms
cookieconsent.min.js
16 ms
wejs
20440 ms
jquery.min.js
22 ms
swiper-bundle.min.js
25 ms
jquery-ui-1.10.0.custom.min.js
544 ms
jquery.ui.datepicker-ja.js
308 ms
jquery.colorbox-min.js
308 ms
picturefill.js
41 ms
custom.js
530 ms
wow.min.js
530 ms
tc_widget.js
1146 ms
directin-search.js
529 ms
talkappi.js
951 ms
analytics.js
104 ms
gtm.js
174 ms
CoE2017_WidgetAsset-14348-2.png
209 ms
mv01.jpg
719 ms
TC800hokkaidoDN2024_thumbnail-thumb-200xauto-8645.jpg
206 ms
SM800-AThokkaido2024_thumbnail-thumb-200xauto-8670.jpg
322 ms
QA800hokkaido2024-thumb-200xauto-8730.jpg
352 ms
SRC200-hamamatsuri2022_02-thumb-200xauto-7039.jpg
321 ms
TC800abudekadrink2024_02logo03-thumb-200xauto-8789.jpg
354 ms
SRC800-hokkaido2024_thumbnail-thumb-200xauto-8733.jpg
388 ms
SRC800-hinabe2024-thumb-200xauto-8794.jpg
483 ms
Stay800-nightblueoasis2024-thumb-200xauto-8833.jpg
484 ms
IRD800anniversary_cake2024_thumbnail_02-thumb-200xauto-8672.jpg
495 ms
RM200_propose2021-thumb-200xauto-6125.jpg
518 ms
eve200-halfbirthday2022-thumb-200xauto-6898.jpg
539 ms
bqt200-summerparty2016-thumb-200xauto-2274.jpg
649 ms
stay200-airweave-thumb-200xauto-1092.jpg
650 ms
Stay200_gardennecklace_lito2024-thumb-200xauto-8765.jpg
666 ms
Stay800-obento20240805_03-thumb-200xauto-8804.jpg
695 ms
TC800hokkaidoDN2024_thumbnail-thumb-200xauto-8663.jpg
716 ms
RM200_mothersfathersday2019-thumb-200xauto-4801.jpg
844 ms
IR200_BF2024-thumb-200xauto-8492.jpg
845 ms
SM800_SJpeach2024-thumb-200xauto-8797.jpg
846 ms
SM800_kakigori2024-thumb-200xauto-8821.jpg
870 ms
QS800_kanazawa2024_02-thumb-200xauto-8815.jpg
892 ms
QA800kanshasai202408-thumb-200xauto-8817.jpg
892 ms
SRC200-salon_de_chen2023_03-thumb-200xauto-7672.jpg
981 ms
eve200-secondhouse_campaign2024-thumb-200xauto-8773.jpg
982 ms
57583c2545cb165ee8276c54db99f00c8f460af3-thumb-200xauto-7706.jpg
1010 ms
EV200_charitykekka2023-thumb-200xauto-8457.jpg
1047 ms
EV200_gochojuoiwai-thumb-200xauto-6795.jpg
1071 ms
RM200_EXS_NIGHT-thumb-200xauto-6007.jpg
1075 ms
eve200-resipe2021_05-thumb-200xauto-6082.jpg
1147 ms
mvStay01.jpg
1649 ms
sdk.js
156 ms
embed
381 ms
picStay01.jpg
1502 ms
widgets.js
224 ms
webfont.js
70 ms
linkid.js
53 ms
picStay02.jpg
1245 ms
mvRest01.jpg
1622 ms
pic_restaurant01.jpg
1091 ms
collect
38 ms
collect
51 ms
sdk.js
9 ms
pic_restaurant02.jpg
1646 ms
css
59 ms
73 ms
pic_restaurant03.jpg
1225 ms
OD5DuM6Cyma8FnnsDzD3rA.ttf
46 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOtbHKrc.ttf
78 ms
pic_restaurant04.jpg
1261 ms
pic_restaurant05.jpg
1288 ms
pic_restaurant06.jpg
1695 ms
pic_restaurant07.jpg
1406 ms
pic_restaurant08.jpg
1400 ms
js
59 ms
pic_restaurant09.jpg
1338 ms
picBanq01.jpg
1454 ms
picWed01.jpg
1819 ms
picFacilities01.jpg
1449 ms
Y-SDGs1.jpg
1445 ms
sns_ico_facebook.png
1339 ms
sns_ico_x.png
1464 ms
sns_ico_instagram.png
1478 ms
sprite.svg
1455 ms
bottom_bg.jpg
1440 ms
bg-gray.jpg
1503 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
89 ms
share.png
1445 ms
bnr_propose.jpg
1476 ms
bnr_secondhouse.jpg
1463 ms
bnr_rei.jpg
1452 ms
bnr_secondhouse.jpg
1500 ms
bnr_rei.jpg
1574 ms
settings
69 ms
button.856debeac157d9669cf51e73a08fbc93.js
27 ms
embeds
25 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html
40 ms
5590c49fa0749eb59d002e98.json
163 ms
ybht.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
ybht.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ybht.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 Ybht.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 Ybht.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.
ybht.co.jp
Open Graph data is detected on the main page of Ybht. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: