Tools & Wizards About Us
staying.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

staying.com

Compare and book hotels all over the world

Page Load Speed

2.4 sec in total

First Response

176 ms

Resources Loaded

2 sec

Page Rendered

302 ms

staying.com screenshot

About Website

Welcome to staying.com homepage info - get ready to check Staying best content for United States right away, or after learning these important things about staying.com

Compare and book over 150000 properties all over the world. Check customer reviews, amenities and nearby suggestions and reserve the best deals.

Visit staying.com

Key Findings

We analyzed Staying.com page load time and found that the first response time was 176 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

staying.com performance score

0

Network Requests Diagram

staying.com

176 ms

css

24 ms

bootstrap.min.css

6 ms

custom.css

51 ms

jquery.min.js

16 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 19% of them (11 requests) were addressed to the original Staying.com, 18% (10 requests) were made to Google-analytics.com and 12% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (715 ms) relates to the external source Secure.rezserver.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 358.7 kB (37%)

Content Size

967.3 kB

After Optimization

608.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Staying.com main page is 967.3 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. 45% of websites need less resources to load. Images take 534.5 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 16.0 kB

  • Original 21.7 kB
  • After minification 20.5 kB
  • After compression 5.7 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 16.0 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 9.8 kB

  • Original 534.5 kB
  • After minification 524.7 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. Staying images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 205.5 kB

  • Original 257.8 kB
  • After minification 171.8 kB
  • After compression 52.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 205.5 kB or 80% of the original size.

CSS Optimization

-83%

Potential reduce by 127.4 kB

  • Original 153.3 kB
  • After minification 146.1 kB
  • After compression 25.9 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. Staying.com needs all CSS files to be minified and compressed as it can save up to 127.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (55%)

Requests Now

47

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Staying. 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

staying.com

staying.com

176 ms

css

css

24 ms

bootstrap.min.css

bootstrap.min.css

6 ms

custom.css

custom.css

51 ms

jquery.min.js

jquery.min.js

16 ms

bootstrap.min.js

bootstrap.min.js

4 ms

custom.js

custom.js

93 ms

searchbox.js

searchbox.js

159 ms

deals.min.js

deals.min.js

326 ms

gtm.js

gtm.js

45 ms

logo.svg

logo.svg

53 ms

hotels.jpg

hotels.jpg

273 ms

newsletter.svg

newsletter.svg

131 ms

facebook.png

facebook.png

133 ms

payment_methods.png

payment_methods.png

133 ms

conversion_async.js

conversion_async.js

27 ms

analytics.js

analytics.js

24 ms

logo_plane.svg

logo_plane.svg

54 ms

ODelI1aHBYDBqgeIAH2zlBBHWFfxJXS04xYOz0jw624.woff

ODelI1aHBYDBqgeIAH2zlBBHWFfxJXS04xYOz0jw624.woff

48 ms

toadOcfmlt9b38dHJxOBGIPZSf8Ud0kNoe3bGnF7K24.woff

toadOcfmlt9b38dHJxOBGIPZSf8Ud0kNoe3bGnF7K24.woff

49 ms

toadOcfmlt9b38dHJxOBGLhZfOo4eSOlrve6pGrXHAo.woff

toadOcfmlt9b38dHJxOBGLhZfOo4eSOlrve6pGrXHAo.woff

51 ms

toadOcfmlt9b38dHJxOBGAAD_zxmsR6vL1X3tnvCZYo.woff

toadOcfmlt9b38dHJxOBGAAD_zxmsR6vL1X3tnvCZYo.woff

49 ms

toadOcfmlt9b38dHJxOBGAE-U1AYRUXXE0Dth8uKIE0.woff

toadOcfmlt9b38dHJxOBGAE-U1AYRUXXE0Dth8uKIE0.woff

77 ms

toadOcfmlt9b38dHJxOBGLhvvL6PHcOvkHgRlzWiaCU.woff

toadOcfmlt9b38dHJxOBGLhvvL6PHcOvkHgRlzWiaCU.woff

50 ms

linkid.js

linkid.js

41 ms

54 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

26 ms

collect

collect

15 ms

collect

collect

110 ms

collect

collect

10 ms

collect

collect

100 ms

43 ms

662 ms

collect

collect

70 ms

715 ms

collect

collect

70 ms

702 ms

collect

collect

33 ms

collect

collect

18 ms

collect

collect

19 ms

collect

collect

19 ms

jquery-2.0.3.min.js

jquery-2.0.3.min.js

110 ms

internal.min.js

internal.min.js

107 ms

offers.css

offers.css

47 ms

css

css

33 ms

52726484.jpg

52726484.jpg

644 ms

starRating.png

starRating.png

29 ms

409796_14030618320018585384.jpg

409796_14030618320018585384.jpg

169 ms

41215113.jpg

41215113.jpg

623 ms

12850698.jpg

12850698.jpg

542 ms

20559166.jpg

20559166.jpg

582 ms

8253726.jpg

8253726.jpg

632 ms

33953955.jpg

33953955.jpg

548 ms

20836178.jpg

20836178.jpg

626 ms

promoIcons.png

promoIcons.png

12 ms

10594_120430143846705.jpg

10594_120430143846705.jpg

125 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

4 ms

SEO Factors

staying.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

staying.com

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