Tools & Wizards About Us
trivago.com.uy screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

trivago.com.uy

trivago.com.uy - Compare hotel prices worldwide

Page Load Speed

3 sec in total

First Response

232 ms

Resources Loaded

2.6 sec

Page Rendered

166 ms

trivago.com.uy screenshot

About Website

Welcome to trivago.com.uy homepage info - get ready to check Trivago Com best content for Uruguay right away, or after learning these important things about trivago.com.uy

Compare hotel prices from hundreds of travel sites and get great deals. Save time and money on finding your ideal accommodation with millions of reviews and photos on trivago.com.uy

Visit trivago.com.uy

Key Findings

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

Performance Metrics

trivago.com.uy performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value3,040 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value1.4

0/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

www.trivago.com.uy

232 ms

en-US

728 ms

tailwind-ltr-7011817950362674.css

43 ms

1a219283a31fdb68.css

163 ms

f8134cc0d86ae2c3.css

83 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 59% of them (33 requests) were addressed to the original Trivago.com.uy, 41% (23 requests) were made to Imgcy.trivago.com. The less responsive or slowest element that took the longest time to load (955 ms) belongs to the original domain Trivago.com.uy.

Page Optimization Overview & Recommendations

Page size can be reduced by 377.1 kB (76%)

Content Size

495.6 kB

After Optimization

118.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Trivago.com.uy main page is 495.6 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. 50% of websites need less resources to load. HTML takes 350.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 284.7 kB

  • Original 350.1 kB
  • After minification 349.8 kB
  • After compression 65.3 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 284.7 kB or 81% of the original size.

JavaScript Optimization

-63%

Potential reduce by 82.4 kB

  • Original 130.3 kB
  • After minification 130.3 kB
  • After compression 47.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 82.4 kB or 63% of the original size.

CSS Optimization

-65%

Potential reduce by 9.9 kB

  • Original 15.3 kB
  • After minification 13.0 kB
  • After compression 5.4 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. Trivago.com.uy needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 65% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

www.trivago.com.uy

www.trivago.com.uy

232 ms

en-US

en-US

728 ms

tailwind-ltr-7011817950362674.css

tailwind-ltr-7011817950362674.css

43 ms

1a219283a31fdb68.css

1a219283a31fdb68.css

163 ms

f8134cc0d86ae2c3.css

f8134cc0d86ae2c3.css

83 ms

d2d587472331b1c6.css

d2d587472331b1c6.css

339 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

197 ms

webpack-6ba644cbfa779d27.js

webpack-6ba644cbfa779d27.js

313 ms

framework-baf8ffbd06d78458.js

framework-baf8ffbd06d78458.js

79 ms

main-5c2bc031227287a3.js

main-5c2bc031227287a3.js

111 ms

_app-30dfe2ed5be2329c.js

_app-30dfe2ed5be2329c.js

702 ms

5591-dd1f6f00a7036e06.js

5591-dd1f6f00a7036e06.js

325 ms

1664-c303f85bbebb1f01.js

1664-c303f85bbebb1f01.js

482 ms

8388-731a136a81abd4f3.js

8388-731a136a81abd4f3.js

481 ms

1471-837b9a1c7f5450eb.js

1471-837b9a1c7f5450eb.js

504 ms

7267-839a6a74e1e7ad45.js

7267-839a6a74e1e7ad45.js

481 ms

416-3f6579e429eeb670.js

416-3f6579e429eeb670.js

480 ms

6111-c2bb1d89e2e94992.js

6111-c2bb1d89e2e94992.js

592 ms

2149-36a38c708d140e44.js

2149-36a38c708d140e44.js

573 ms

7826-188b2c849e31a9b4.js

7826-188b2c849e31a9b4.js

955 ms

8066-ab77ca7daaa991cc.js

8066-ab77ca7daaa991cc.js

611 ms

5561-5c49cd31bc53107f.js

5561-5c49cd31bc53107f.js

635 ms

6935-34d9a7fdd1efecac.js

6935-34d9a7fdd1efecac.js

759 ms

5326-9d93e0a240a17436.js

5326-9d93e0a240a17436.js

683 ms

14-3a47b0fe6f77f089.js

14-3a47b0fe6f77f089.js

705 ms

8859-0a899c1660a34752.js

8859-0a899c1660a34752.js

832 ms

3299-8ac5f129322bbc62.js

3299-8ac5f129322bbc62.js

768 ms

6821-93fca2d760b5176f.js

6821-93fca2d760b5176f.js

742 ms

6067-85d79b4c2cd922e7.js

6067-85d79b4c2cd922e7.js

916 ms

%5BlanguageCode%5D-523dc372d0450d3a.js

%5BlanguageCode%5D-523dc372d0450d3a.js

784 ms

_buildManifest.js

_buildManifest.js

877 ms

_ssgManifest.js

_ssgManifest.js

809 ms

305b7014

305b7014

805 ms

room_1280_2x.webp

room_1280_2x.webp

184 ms

626.png

626.png

117 ms

3340_1.png

3340_1.png

96 ms

406.png

406.png

94 ms

395.png

395.png

129 ms

2420_1.png

2420_1.png

134 ms

14.png

14.png

105 ms

634.png

634.png

106 ms

73256_v37.jpeg

73256_v37.jpeg

131 ms

ae56a36e270eb26db53a39dea66b5b7ce41e0457ce22b86c4373d2a788ad.jpeg

ae56a36e270eb26db53a39dea66b5b7ce41e0457ce22b86c4373d2a788ad.jpeg

117 ms

a141f205e1bf8c1c988e594652ed9662ae7bdb94c2c047d19c011752d19e.jpeg

a141f205e1bf8c1c988e594652ed9662ae7bdb94c2c047d19c011752d19e.jpeg

125 ms

01491c35dee245e90dd26bcc4ed42f05c18dfeedddb1ebef7a8e3b199e44.jpeg

01491c35dee245e90dd26bcc4ed42f05c18dfeedddb1ebef7a8e3b199e44.jpeg

130 ms

0ad0b3c34a5447123e7a647ab8b7ce4024a35984e5a04747ce5ad5613de4.jpeg

0ad0b3c34a5447123e7a647ab8b7ce4024a35984e5a04747ce5ad5613de4.jpeg

131 ms

745e8eb29863b2235c5e03b4cc6711fc33ac188faed193d9382d8f05d0f3.jpeg

745e8eb29863b2235c5e03b4cc6711fc33ac188faed193d9382d8f05d0f3.jpeg

137 ms

73256_v37.jpeg

73256_v37.jpeg

142 ms

67449_v73.jpeg

67449_v73.jpeg

141 ms

67443_v74.jpeg

67443_v74.jpeg

140 ms

141396_v73.jpeg

141396_v73.jpeg

140 ms

14734_v10.jpeg

14734_v10.jpeg

143 ms

59182_v10.jpeg

59182_v10.jpeg

147 ms

Search.svg

Search.svg

149 ms

Compare.svg

Compare.svg

149 ms

Save.svg

Save.svg

151 ms

Accessibility Review

trivago.com.uy accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

trivago.com.uy best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

trivago.com.uy SEO score

98

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Trivago.com.uy 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 Trivago.com.uy 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

trivago.com.uy

Open Graph data is detected on the main page of Trivago Com. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: