56.3 sec in total
615 ms
51 sec
4.7 sec
Welcome to yayaya21.com homepage info - get ready to check YAYAYA 21 best content for Japan right away, or after learning these important things about yayaya21.com
ホテル YAYAYA 貳番館 オフィシャルサイト。鶯谷駅より徒歩3分。
Visit yayaya21.comWe analyzed Yayaya21.com page load time and found that the first response time was 615 ms and then it took 55.7 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 were 40 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
yayaya21.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value11.0 s
0/100
25%
Value9.5 s
12/100
10%
Value670 ms
45/100
30%
Value0.303
39/100
15%
Value11.6 s
18/100
10%
615 ms
1135 ms
743 ms
495 ms
13239 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 71% of them (120 requests) were addressed to the original Yayaya21.com, 14% (23 requests) were made to Maps.googleapis.com and 5% (9 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Yayaya21.com.
Page size can be reduced by 676.9 kB (9%)
7.8 MB
7.1 MB
In fact, the total size of Yayaya21.com main page is 7.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. 45% of websites need less resources to load. Images take 7.1 MB which makes up the majority of the site volume.
Potential reduce by 21.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 21.9 kB or 81% of the original size.
Potential reduce by 195.1 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. YAYAYA 21 images are well optimized though.
Potential reduce by 445.6 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 445.6 kB or 65% of the original size.
Potential reduce by 14.3 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. Yayaya21.com needs all CSS files to be minified and compressed as it can save up to 14.3 kB or 79% of the original size.
Number of requests can be reduced by 45 (37%)
122
77
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of YAYAYA 21. 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 4 to 1 for CSS and as a result speed up the page load time.
yayaya21.com
615 ms
www.yayaya21.com
1135 ms
style.css
743 ms
jquery.slick.css
495 ms
main01.png
13239 ms
main02.png
19971 ms
main03.png
4050 ms
txt_whatsnew.gif
981 ms
icon_rate.png
990 ms
timetable_yayaya.gif
6298 ms
timetable_next.gif
2247 ms
timetable_niban.gif
3066 ms
btn_coupon_off.png
4773 ms
btn_pagetop_off.png
3591 ms
icon_room.png
4038 ms
txt_room_yayaya.gif
4343 ms
111.png
19090 ms
112.png
6574 ms
113.png
7085 ms
115.png
14723 ms
211.png
18137 ms
212.png
11286 ms
213.png
18234 ms
215.png
15765 ms
216.png
19742 ms
217.png
17765 ms
311.png
19742 ms
312.png
19743 ms
313.png
19742 ms
315.png
19743 ms
316.png
19743 ms
txt_room_niban.gif
19743 ms
101.png
19758 ms
201.png
19761 ms
202.png
19761 ms
203.png
19767 ms
205.png
19772 ms
301.png
20488 ms
embed
298 ms
print.js
19995 ms
jquery-1.11.0.min.js
20185 ms
embed
1198 ms
jquery.slick.min.js
19998 ms
jquery.ticker.js
19990 ms
rs=ABjfnFX2tihhEHtv5jrClYlHcE3jABjaCA
285 ms
css
279 ms
js
357 ms
rs=ABjfnFW_8EqvjfdWjZFcB9KzU4n_ruUV4A
564 ms
jquery.cookie.js
19245 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
472 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
523 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
599 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
676 ms
rs=ABjfnFW_8EqvjfdWjZFcB9KzU4n_ruUV4A
156 ms
common.js
180 ms
map.js
223 ms
overlay.js
298 ms
1493-wht-blank_maps-4x.png&filter=ffA61B4A&scale=1.0
291 ms
util.js
719 ms
marker.js
289 ms
geocoder.js
278 ms
controls.js
340 ms
places_impl.js
277 ms
selection_2x-000.png
145 ms
gen204
174 ms
onion.js
102 ms
ViewportInfoService.GetViewportInfo
572 ms
stats.js
67 ms
StaticMapService.GetMapImage
482 ms
302.png
19696 ms
transparent.png
392 ms
mapcnt6.png
375 ms
tmapctrl4.png
418 ms
vt
276 ms
vt
351 ms
vt
672 ms
vt
252 ms
vt
250 ms
vt
382 ms
vt
403 ms
viewer-icons001.png
131 ms
star4.png
251 ms
MyMaps_Icons003.png
38 ms
mymaps_32.png
38 ms
v1_4593b7d7.png
60 ms
google-my-maps-logo-small-001.png
60 ms
303.png
20163 ms
305.png
19918 ms
gen204
219 ms
AuthenticationService.Authenticate
64 ms
kh
587 ms
401.png
19704 ms
402.png
20404 ms
403.png
19983 ms
405.png
19678 ms
501.png
20171 ms
502.png
19660 ms
QuotaService.RecordEvent
20 ms
QuotaService.RecordEvent
45 ms
txt_room_next.gif
12958 ms
231.png
19734 ms
232.png
18345 ms
233.png
16687 ms
235.png
11009 ms
236.png
11715 ms
331.png
16257 ms
332.png
15967 ms
333.png
19291 ms
335.png
19998 ms
336.png
19997 ms
441.png
19997 ms
442.png
19997 ms
443.png
19996 ms
445.png
19997 ms
446.png
19980 ms
icon_service.png
19980 ms
txt_service.gif
19980 ms
img_service01.jpg
19969 ms
img_service02.jpg
19970 ms
img_service03.jpg
19969 ms
img_service04.jpg
20124 ms
img_service05.jpg
19990 ms
img_service06.jpg
19881 ms
img_service07.jpg
19888 ms
img_service08.jpg
19887 ms
ga.js
448 ms
txt_facility.gif
18913 ms
__utm.gif
66 ms
img_facility01.jpg
18083 ms
img_facility02.jpg
17765 ms
img_facility03.jpg
18026 ms
img_facility04.jpg
17524 ms
img_facility05.jpg
17053 ms
img_facility06.jpg
16754 ms
img_facility07.jpg
16770 ms
img_facility08.jpg
16247 ms
img_facility09.jpg
15208 ms
img_facility10.jpg
15555 ms
img_facility11.jpg
13366 ms
img_facility12.jpg
12275 ms
img_facility13.jpg
10162 ms
img_facility14.jpg
9837 ms
icon_access.png
9428 ms
txt_access_yayaya.gif
8102 ms
txt_access_niban.gif
7532 ms
txt_access_next.gif
3735 ms
icon_coupon.png
3214 ms
img_coupon.png
9829 ms
btn_print.png
3294 ms
icon_faq.png
3300 ms
txt_copyright.gif
3326 ms
menu01.png
3470 ms
menu02.png
3672 ms
menu03.png
3815 ms
menu04.png
3913 ms
menu05.png
4079 ms
menu06.png
4217 ms
menu07.png
4288 ms
tab_ya_on.gif
4038 ms
tab_ni_off.gif
4025 ms
tab_ne_off.gif
4446 ms
txt_service_bg.gif
3898 ms
txt_facility_bg.gif
4510 ms
icon_map.gif
3983 ms
line_faq.gif
3998 ms
icon_q.png
3654 ms
icon_a.png
3835 ms
icon_footer_sp.gif
3765 ms
icon_footer_pc.gif
3911 ms
yayaya21.com 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
Image elements do not have [alt] attributes
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.
yayaya21.com 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
yayaya21.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Yayaya21.com 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 Yayaya21.com 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.
yayaya21.com
Open Graph description is not detected on the main page of YAYAYA 21. 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: