Tools & Wizards About Us
osakadaiichi.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

osakadaiichi.co.jp

＜公式＞大阪第一ホテル｜大阪駅より徒歩3分の大阪マルビル

Page Load Speed

9.3 sec in total

First Response

609 ms

Resources Loaded

8.5 sec

Page Rendered

262 ms

osakadaiichi.co.jp screenshot

About Website

Click here to check amazing Osakadaiichi content for Japan. Otherwise, check out these important facts you probably never knew about osakadaiichi.co.jp

大阪駅より徒歩3分の大阪第一ホテルのページです。大阪梅田のランドマークビル「大阪マルビル」の中にあり、関西観光・ビジネスの宿泊に便利なアクセスです。宴会、会議、各種パーティご利用にも。レストラン・ショップは充実の20店以上

Visit osakadaiichi.co.jp

Key Findings

We analyzed Osakadaiichi.co.jp page load time and found that the first response time was 609 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

osakadaiichi.co.jp performance score

0

Network Requests Diagram

osakadaiichi.co.jp

609 ms

index2.html

638 ms

reset.css

352 ms

common.css

354 ms

index.css

892 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 82% of them (83 requests) were addressed to the original Osakadaiichi.co.jp, 7% (7 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Osakadaiichi.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 286.0 kB (32%)

Content Size

898.0 kB

After Optimization

612.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Osakadaiichi.co.jp main page is 898.0 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. 65% of websites need less resources to load. Images take 573.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 25.4 kB

  • Original 34.3 kB
  • After minification 32.2 kB
  • After compression 8.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 25.4 kB or 74% of the original size.

Image Optimization

-8%

Potential reduce by 46.9 kB

  • Original 573.7 kB
  • After minification 526.8 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. Osakadaiichi images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 114.3 kB

  • Original 174.5 kB
  • After minification 133.5 kB
  • After compression 60.2 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 114.3 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 99.5 kB

  • Original 115.5 kB
  • After minification 89.4 kB
  • After compression 16.1 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. Osakadaiichi.co.jp needs all CSS files to be minified and compressed as it can save up to 99.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (43%)

Requests Now

90

After Optimization

51

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

osakadaiichi.co.jp

osakadaiichi.co.jp

609 ms

index2.html

index2.html

638 ms

reset.css

reset.css

352 ms

common.css

common.css

354 ms

index.css

index.css

892 ms

jquery.tabs.css

jquery.tabs.css

600 ms

jquery.bxslider.css

jquery.bxslider.css

413 ms

notosansjapanese.css

notosansjapanese.css

24 ms

jquery.min.js

jquery.min.js

8 ms

common.js

common.js

554 ms

dropdown.js

dropdown.js

749 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

751 ms

swfobject.js

swfobject.js

824 ms

jquery.history_remote.pack.js

jquery.history_remote.pack.js

932 ms

smoothScroll.js

smoothScroll.js

953 ms

yahho-calendar.js

yahho-calendar.js

1082 ms

gcalendar-holidays.js

gcalendar-holidays.js

1106 ms

bxslider.js

bxslider.js

1624 ms

ssl.js

ssl.js

1045 ms

conversion.js

conversion.js

13 ms

yuiloader-dom-event.js

yuiloader-dom-event.js

5 ms

calendar.css

calendar.css

6 ms

calendar-min.js

calendar-min.js

8 ms

header_logo.gif

header_logo.gif

198 ms

nav-online_head.gif

nav-online_head.gif

189 ms

nav-title_online-reserv_2.gif

nav-title_online-reserv_2.gif

400 ms

btn_reservation_cal.jpg

btn_reservation_cal.jpg

398 ms

btn_reservation_plan.jpg

btn_reservation_plan.jpg

400 ms

btn_reservation_day.jpg

btn_reservation_day.jpg

425 ms

btn_calender_2.gif

btn_calender_2.gif

549 ms

btn_search-room_2.jpg

btn_search-room_2.jpg

550 ms

btn_search-room_3.jpg

btn_search-room_3.jpg

732 ms

btn_houjin_login.jpg

btn_houjin_login.jpg

741 ms

bnr_usj.jpg

bnr_usj.jpg

739 ms

btn_faq.jpg

btn_faq.jpg

775 ms

nav-title_recommend-menu.gif

nav-title_recommend-menu.gif

902 ms

btn_flash_acsess.jpg

btn_flash_acsess.jpg

946 ms

btn_flash_stay.jpg

btn_flash_stay.jpg

1115 ms

btn_flash_internet.jpg

btn_flash_internet.jpg

1132 ms

title_whatsnew.gif

title_whatsnew.gif

1122 ms

whatsnew_stay1.gif

whatsnew_stay1.gif

1123 ms

img_usj.jpg

img_usj.jpg

1472 ms

whatsnew_party1.gif

whatsnew_party1.gif

1323 ms

whatsnew_carat1.gif

whatsnew_carat1.gif

1472 ms

whatsnew_others1.gif

whatsnew_others1.gif

1501 ms

h3_top_restaurant.png

h3_top_restaurant.png

1508 ms

bnr_top_marubiru-rest.png

bnr_top_marubiru-rest.png

1521 ms

bnr_top_carat_2016spring.png

bnr_top_carat_2016spring.png

1823 ms

bnr_top_onlineshop.jpg

bnr_top_onlineshop.jpg

1850 ms

bnr_top_pointcard.jpg

bnr_top_pointcard.jpg

1861 ms

bnr_top_memberscard.jpg

bnr_top_memberscard.jpg

1906 ms

bnr_top_greenproject.jpg

bnr_top_greenproject.jpg

1901 ms

h3_top_csr.png

h3_top_csr.png

1899 ms

img_top_csr.png

img_top_csr.png

2390 ms

h3_top_jusyo.png

h3_top_jusyo.png

2207 ms

top_banner_hi-service.jpg

top_banner_hi-service.jpg

2394 ms

title_r_2.png

title_r_2.png

2228 ms

present_2.jpg

present_2.jpg

2474 ms

analytics.js

analytics.js

25 ms

footer_info.png

footer_info.png

2274 ms

collect

collect

31 ms

NotoSansJP-DemiLight.woff

NotoSansJP-DemiLight.woff

47 ms

NotoSansJP-Light.woff

NotoSansJP-Light.woff

106 ms

NotoSansJP-Thin.woff

NotoSansJP-Thin.woff

160 ms

NotoSansJP-Regular.woff

NotoSansJP-Regular.woff

159 ms

NotoSansJP-Medium.woff

NotoSansJP-Medium.woff

162 ms

NotoSansJP-Bold.woff

NotoSansJP-Bold.woff

160 ms

NotoSansJP-Black.woff

NotoSansJP-Black.woff

158 ms

38 ms

113 ms

footer_logo.png

footer_logo.png

2381 ms

footer_menu.png

footer_menu.png

2356 ms

159 ms

footer_link.png

footer_link.png

2263 ms

bnr_f_associate2.png

bnr_f_associate2.png

2495 ms

bnr_f_usj2.png

bnr_f_usj2.png

2615 ms

bnr_challenge25.png

bnr_challenge25.png

2439 ms

bnr_stop.png

bnr_stop.png

2399 ms

bg_header.jpg

bg_header.jpg

2639 ms

bg_header-inner.jpg

bg_header-inner.jpg

2494 ms

arrow01.gif

arrow01.gif

2504 ms

bg_wrapper.jpg

bg_wrapper.jpg

2748 ms

bg_columnA.jpg

bg_columnA.jpg

2530 ms

bg_listbdr.gif

bg_listbdr.gif

2467 ms

outlink.gif

outlink.gif

2614 ms

bg_lineC0BFBD.gif

bg_lineC0BFBD.gif

2482 ms

bg_A-list.gif

bg_A-list.gif

2477 ms

bg_tab4_4.gif

bg_tab4_4.gif

2537 ms

arrow04.gif

arrow04.gif

2565 ms

a3.gif

a3.gif

2577 ms

a1.gif

a1.gif

2444 ms

a2.gif

a2.gif

2496 ms

bg_lineB2A499.gif

bg_lineB2A499.gif

2510 ms

arrow03.gif

arrow03.gif

2522 ms

icon_outlink01.gif

icon_outlink01.gif

2524 ms

main_noflash.jpg

main_noflash.jpg

2951 ms

stickersr_s.gif

stickersr_s.gif

2437 ms

bnr_top_onlineshop.jpg

bnr_top_onlineshop.jpg

2477 ms

bnr_top_pointcard.jpg

bnr_top_pointcard.jpg

2486 ms

bnr_top_memberscard.jpg

bnr_top_memberscard.jpg

2509 ms

bnr_top_greenproject.jpg

bnr_top_greenproject.jpg

2516 ms

SEO Factors

osakadaiichi.co.jp 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 Osakadaiichi.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 Osakadaiichi.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.

Social Sharing Optimization

osakadaiichi.co.jp

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