Tools & Wizards About Us
hotelunizo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hotelunizo.com

ユニゾグループのホテル【公式サイト】｜ホテルの宿泊予約サイト

Page Load Speed

4.8 sec in total

First Response

359 ms

Resources Loaded

4.1 sec

Page Rendered

324 ms

hotelunizo.com screenshot

About Website

Click here to check amazing Hotelunizo content for Japan. Otherwise, check out these important facts you probably never knew about hotelunizo.com

ユニゾグループのホテル 公式サイト。アクセスの利便性を追求した立地と、快適な空間を備えた宿泊特化型のホテルを日本全国に展開しています。

Visit hotelunizo.com

Key Findings

We analyzed Hotelunizo.com page load time and found that the first response time was 359 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

hotelunizo.com performance score

0

Network Requests Diagram

hotelunizo.com

359 ms

index.php

712 ms

init.css

359 ms

top.css

538 ms

datepicker.css

369 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 83% of them (78 requests) were addressed to the original Hotelunizo.com, 13% (12 requests) were made to Advance.reservation.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Advance.reservation.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 416.1 kB (23%)

Content Size

1.8 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hotelunizo.com main page is 1.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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 38.2 kB

  • Original 46.0 kB
  • After minification 37.6 kB
  • After compression 7.8 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. This page needs HTML code to be minified as it can gain 8.4 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 38.2 kB or 83% of the original size.

Image Optimization

-11%

Potential reduce by 161.5 kB

  • Original 1.4 MB
  • After minification 1.3 MB

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. Obviously, Hotelunizo needs image optimization as it can save up to 161.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 202.1 kB

  • Original 285.1 kB
  • After minification 228.1 kB
  • After compression 82.9 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 202.1 kB or 71% of the original size.

CSS Optimization

-79%

Potential reduce by 14.4 kB

  • Original 18.2 kB
  • After minification 11.3 kB
  • After compression 3.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. Hotelunizo.com needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (32%)

Requests Now

91

After Optimization

62

  • Images
  • JavaScript
  • CSS

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hotelunizo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hotelunizo.com

hotelunizo.com

359 ms

index.php

index.php

712 ms

init.css

init.css

359 ms

top.css

top.css

538 ms

datepicker.css

datepicker.css

369 ms

jquery.nivo.slider.css

jquery.nivo.slider.css

361 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

380 ms

jquery.js

jquery.js

1220 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

716 ms

connected-select.js

connected-select.js

551 ms

ui.core.js

ui.core.js

756 ms

ui.tabs.js

ui.tabs.js

683 ms

jp-holidays.js

jp-holidays.js

712 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

901 ms

util.js

util.js

857 ms

getseal

getseal

265 ms

jquery.carouFredSel-6.2.0.js

jquery.carouFredSel-6.2.0.js

1071 ms

20110518112935187.jpg

20110518112935187.jpg

996 ms

20101015192818015.jpg

20101015192818015.jpg

922 ms

20150512192121078.jpg

20150512192121078.jpg

1105 ms

20140920211144564.jpg

20140920211144564.jpg

926 ms

2010012211210689.jpg

2010012211210689.jpg

758 ms

20120828154842953.JPG

20120828154842953.JPG

946 ms

20130819114103871.jpg

20130819114103871.jpg

1109 ms

20131230165841487.png

20131230165841487.png

1264 ms

20140921075958485.PNG

20140921075958485.PNG

1458 ms

20140708154621471.PNG

20140708154621471.PNG

1493 ms

20150412074445116.jpg

20150412074445116.jpg

1156 ms

20151023152220786.JPG

20151023152220786.JPG

1450 ms

headder_bg.jpg

headder_bg.jpg

234 ms

unizo-logo.jpg

unizo-logo.jpg

234 ms

headder_japanese.jpg

headder_japanese.jpg

235 ms

headder_unizoin.png

headder_unizoin.png

233 ms

headder_jowa.png

headder_jowa.png

353 ms

headder_toiawase.jpg

headder_toiawase.jpg

330 ms

headder_touroku.jpg

headder_touroku.jpg

399 ms

headder_annai.jpg

headder_annai.jpg

398 ms

menu_bg.jpg

menu_bg.jpg

403 ms

btn_menu_home_off.jpg

btn_menu_home_off.jpg

418 ms

btn_menu_yoyaku_off.jpg

btn_menu_yoyaku_off.jpg

507 ms

btn_menu_kakunin_off.jpg

btn_menu_kakunin_off.jpg

530 ms

img_arrow_on_blue.png

img_arrow_on_blue.png

573 ms

bg_kvtab_on_blue.png

bg_kvtab_on_blue.png

574 ms

bg_border_kv.png

bg_border_kv.png

581 ms

bg_kvtab_off.png

bg_kvtab_off.png

605 ms

img-ginza7_open.jpg

img-ginza7_open.jpg

893 ms

img_sapporo_open.jpg

img_sapporo_open.jpg

882 ms

img-tenjin_open.jpg

img-tenjin_open.jpg

1090 ms

img_ginza_open.jpg

img_ginza_open.jpg

1260 ms

r_menu_midashi_yoyaku.jpg

r_menu_midashi_yoyaku.jpg

758 ms

btn_r_menu_search_off.jpg

btn_r_menu_search_off.jpg

793 ms

r_menu_midashi_hotel.jpg

r_menu_midashi_hotel.jpg

936 ms

btn_r_menu_shinbashi_off.png

btn_r_menu_shinbashi_off.png

979 ms

btn_r_menu_ginza1_off.png

btn_r_menu_ginza1_off.png

1059 ms

btn_r_menu_ginza7_off.png

btn_r_menu_ginza7_off.png

1068 ms

btn_r_menu_shibuya_off.png

btn_r_menu_shibuya_off.png

1114 ms

btn_r_menu_kyoto.s_off.png

btn_r_menu_kyoto.s_off.png

1168 ms

btn_r_menu_osaka_off.png

btn_r_menu_osaka_off.png

1237 ms

btn_r_menu_tenjin_off.png

btn_r_menu_tenjin_off.png

1243 ms

btn_r_menu_sapporo_off.png

btn_r_menu_sapporo_off.png

1263 ms

btn_r_menu_sendai_off.png

btn_r_menu_sendai_off.png

1291 ms

btn_r_menu_asakusa2_off.png

btn_r_menu_asakusa2_off.png

1354 ms

btn_r_menu_nagoya_s_off.png

btn_r_menu_nagoya_s_off.png

1414 ms

btn_r_menu_nagoya_off.png

btn_r_menu_nagoya_off.png

1399 ms

analytics.js

analytics.js

75 ms

btn_r_menu_hiroshima2_off.png

btn_r_menu_hiroshima2_off.png

1207 ms

menu_midashi_picup.png

menu_midashi_picup.png

1211 ms

bnr_recruit_sapporo.jpg

bnr_recruit_sapporo.jpg

1243 ms

picup_bnr01.jpg

picup_bnr01.jpg

1315 ms

r_menu_banner_qr.png

r_menu_banner_qr.png

1364 ms

collect

collect

12 ms

collect

collect

55 ms

footer_banner_yachiyo2.jpg

footer_banner_yachiyo2.jpg

1273 ms

bnr_unizo_sp.jpg

bnr_unizo_sp.jpg

1262 ms

contents_midashi_map.png

contents_midashi_map.png

1221 ms

contents_map3.png

contents_map3.png

1427 ms

contents_midashi_info.png

contents_midashi_info.png

1335 ms

bnr01.jpg

bnr01.jpg

1360 ms

bnr02.jpg

bnr02.jpg

1272 ms

bnr03.jpg

bnr03.jpg

1258 ms

ad_scroll_back.png

ad_scroll_back.png

1225 ms

ad_scroll_forward.png

ad_scroll_forward.png

1350 ms

contents_midashi_plan.png

contents_midashi_plan.png

1373 ms

contents_midashi_news.png

contents_midashi_news.png

1350 ms

footer_link_release.jpg

footer_link_release.jpg

1203 ms

footer_link_saiyo.jpg

footer_link_saiyo.jpg

1178 ms

footer_link_kaisha.jpg

footer_link_kaisha.jpg

1123 ms

footer_link_kiyaku.jpg

footer_link_kiyaku.jpg

1219 ms

footer_link_policy.jpg

footer_link_policy.jpg

1193 ms

footer_link_map.jpg

footer_link_map.jpg

1148 ms

footer_copy.jpg

footer_copy.jpg

1078 ms

r_menu_yoyaku_icon.jpg

r_menu_yoyaku_icon.jpg

1077 ms

contents_news_icon.jpg

contents_news_icon.jpg

1092 ms

footer_bg.jpg

footer_bg.jpg

1184 ms

SEO Factors

hotelunizo.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotelunizo.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 Hotelunizo.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.

Social Sharing Optimization

hotelunizo.com

Open Graph description is not detected on the main page of Hotelunizo. 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: