Tools & Wizards About Us
hyatt.kr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hyatt.kr

호텔 예약 | 호텔 객실 온라인 예약 - 하얏트 호텔 & 리조트

Page Load Speed

1.2 sec in total

First Response

129 ms

Resources Loaded

954 ms

Page Rendered

90 ms

hyatt.kr screenshot

About Website

Welcome to hyatt.kr homepage info - get ready to check Hyatt best content for South Korea right away, or after learning these important things about hyatt.kr

Hyatt.com에서만 최대 15% 할인 혜택을 제공합니다. 지금 전 세계 850+여 개의 하얏트 호텔 및 리조트 중 한 곳을 예약하고 최적가 보장을 받으십시오.

Visit hyatt.kr

Key Findings

We analyzed Hyatt.kr page load time and found that the first response time was 129 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

hyatt.kr performance score

0

Network Requests Diagram

hyatt.kr

129 ms

index.jsp

381 ms

A.global.css.pagespeed.cf.FjU5w_nPf9.css

87 ms

A.jquery.ui.all.css.pagespeed.cf.Ak67dZOX8I.css

16 ms

core-libs-combined.js.pagespeed.jm.F7u1sQpLsJ.js

12 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Hyatt.kr, 50% (19 requests) were made to Hyatt.com and 37% (14 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (381 ms) relates to the external source Hyatt.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 799.7 kB (65%)

Content Size

1.2 MB

After Optimization

427.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hyatt.kr main page is 1.2 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. 50% of websites need less resources to load. Javascripts take 663.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 61.0 kB

  • Original 79.9 kB
  • After minification 75.6 kB
  • After compression 18.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. 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 61.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 83 B

  • Original 147.2 kB
  • After minification 147.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. Hyatt images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 456.3 kB

  • Original 663.2 kB
  • After minification 659.7 kB
  • After compression 206.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 456.3 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 282.3 kB

  • Original 336.6 kB
  • After minification 297.7 kB
  • After compression 54.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. Hyatt.kr needs all CSS files to be minified and compressed as it can save up to 282.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (69%)

Requests Now

36

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hyatt.kr

hyatt.kr

129 ms

index.jsp

index.jsp

381 ms

A.global.css.pagespeed.cf.FjU5w_nPf9.css

A.global.css.pagespeed.cf.FjU5w_nPf9.css

87 ms

A.jquery.ui.all.css.pagespeed.cf.Ak67dZOX8I.css

A.jquery.ui.all.css.pagespeed.cf.Ak67dZOX8I.css

16 ms

core-libs-combined.js.pagespeed.jm.F7u1sQpLsJ.js

core-libs-combined.js.pagespeed.jm.F7u1sQpLsJ.js

12 ms

jquery.ui.datepicker.parseDate.js.pagespeed.jm.VaKcrobn1O.js

jquery.ui.datepicker.parseDate.js.pagespeed.jm.VaKcrobn1O.js

18 ms

utag.sync.js

utag.sync.js

33 ms

global.js+main.js.pagespeed.jc.ycG3TKJWhY.js

global.js+main.js.pagespeed.jc.ycG3TKJWhY.js

13 ms

nav.js+common.js+homepage.js.pagespeed.jc.cSe9WrzChE.js

nav.js+common.js+homepage.js.pagespeed.jc.cSe9WrzChE.js

15 ms

A.hyattBuilt.css.pagespeed.cf.KOkj8QtlNg.css

A.hyattBuilt.css.pagespeed.cf.KOkj8QtlNg.css

33 ms

A.quickbook.css+quickbook_calendar.css,Mcc.5YqVu0RMMb.css.pagespeed.cf.jie7h42fxv.css

A.quickbook.css+quickbook_calendar.css,Mcc.5YqVu0RMMb.css.pagespeed.cf.jie7h42fxv.css

32 ms

quickbook.js+quickbook_layout.js+autocomplete.js+quickbook_calendar.js+disambig.js.pagespeed.jc.kH-xX8H81u.js

quickbook.js+quickbook_layout.js+autocomplete.js+quickbook_calendar.js+disambig.js.pagespeed.jc.kH-xX8H81u.js

31 ms

css

css

63 ms

id

id

17 ms

target.js

target.js

26 ms

gp_ko_signin_0.gif.pagespeed.ce.39wzDdFnqq.gif

gp_ko_signin_0.gif.pagespeed.ce.39wzDdFnqq.gif

59 ms

utag.js

utag.js

42 ms

xgp_signup_not_a-Member_ko.gif.pagespeed.ic.Vtk2-eI1af.png

xgp_signup_not_a-Member_ko.gif.pagespeed.ic.Vtk2-eI1af.png

33 ms

x160203_Buy2get3-Banner,281280x427,29px_KOR.jpg.pagespeed.ic.FqpgXvclS4.jpg

x160203_Buy2get3-Banner,281280x427,29px_KOR.jpg.pagespeed.ic.FqpgXvclS4.jpg

32 ms

xada-icon.png.pagespeed.ic.NKo11wpuK0.png

xada-icon.png.pagespeed.ic.NKo11wpuK0.png

31 ms

xclose_button.png.pagespeed.ic.JXy40-HGAq.png

xclose_button.png.pagespeed.ic.JXy40-HGAq.png

30 ms

xKW0091_36424_med_344x144_GPJoinExclusives.jpg.pagespeed.ic.TkAEVKxbBh.jpg

xKW0091_36424_med_344x144_GPJoinExclusives.jpg.pagespeed.ic.TkAEVKxbBh.jpg

30 ms

xBed-and-Breakfast-344x144.jpg.pagespeed.ic.s9B4JQGaAK.jpg

xBed-and-Breakfast-344x144.jpg.pagespeed.ic.s9B4JQGaAK.jpg

27 ms

xBCC-Slot-3.png.pagespeed.ic.nzKfnlpSLr.png

xBCC-Slot-3.png.pagespeed.ic.nzKfnlpSLr.png

32 ms

xfooter_KO.png.pagespeed.ic.y8Z57jDU7s.png

xfooter_KO.png.pagespeed.ic.y8Z57jDU7s.png

32 ms

utag.currency.js

utag.currency.js

12 ms

utag.88220.js

utag.88220.js

6 ms

utag.88241.js

utag.88241.js

13 ms

utag.88227.js

utag.88227.js

9 ms

utag.86172.js

utag.86172.js

5 ms

utag.86005.js

utag.86005.js

5 ms

utag.88167.js

utag.88167.js

9 ms

utag.86179.js

utag.86179.js

10 ms

utag.86180.js

utag.86180.js

21 ms

utag.86118.js

utag.86118.js

22 ms

utag.88120.js

utag.88120.js

7 ms

utag.88187.js

utag.88187.js

7 ms

id

id

6 ms

SEO Factors

hyatt.kr SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hyatt.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed English language. Our system also found out that Hyatt.kr 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

hyatt.kr

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