Tools & Wizards About Us
tudiscovery.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tudiscovery.com

WBD LATAM - Todos tus canales favoritos

Page Load Speed

764 ms in total

First Response

188 ms

Resources Loaded

576 ms

Page Rendered

0 ms

tudiscovery.com screenshot

About Website

Click here to check amazing Tudiscovery content for Argentina. Otherwise, check out these important facts you probably never knew about tudiscovery.com

Conoce todos los contenidos de cada una de nuestras marcas, descúbrelas según su tendencia y recorre en detalle sus guías de programación.

Visit tudiscovery.com

Key Findings

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

Performance Metrics

tudiscovery.com performance score

0

Network Requests Diagram

www.tudiscovery.com

188 ms

www.latam.discovery.com

40 ms

gncs.js

185 ms

style.min.1449849307.css

28 ms

addthis_widget.js

40 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 9% of them (1 request) were addressed to the original Tudiscovery.com, 36% (4 requests) were made to Latam.discovery.com and 9% (1 request) were made to Global.utils.discovery.com. The less responsive or slowest element that took the longest time to load (188 ms) belongs to the original domain Tudiscovery.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (83%)

Content Size

1.3 MB

After Optimization

213.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tudiscovery.com main page is 1.3 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. 70% of websites need less resources to load. CSS take 818.9 kB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 646 B

  • Original 1.3 kB
  • After minification 1.2 kB
  • After compression 628 B

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 646 B or 51% of the original size.

Image Optimization

-26%

Potential reduce by 2.6 kB

  • Original 10.1 kB
  • After minification 7.5 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. Obviously, Tudiscovery needs image optimization as it can save up to 2.6 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 294.4 kB

  • Original 439.7 kB
  • After minification 426.4 kB
  • After compression 145.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 294.4 kB or 67% of the original size.

CSS Optimization

-93%

Potential reduce by 759.1 kB

  • Original 818.9 kB
  • After minification 817.4 kB
  • After compression 59.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. Tudiscovery.com needs all CSS files to be minified and compressed as it can save up to 759.1 kB or 93% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (78%)

Requests Now

9

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

www.tudiscovery.com

www.tudiscovery.com

188 ms

www.latam.discovery.com

www.latam.discovery.com

40 ms

gncs.js

gncs.js

185 ms

style.min.1449849307.css

style.min.1449849307.css

28 ms

addthis_widget.js

addthis_widget.js

40 ms

head.min.1449849322.js

head.min.1449849322.js

29 ms

BrightcoveExperiences.js

BrightcoveExperiences.js

55 ms

BrightcovePlugin.js

BrightcovePlugin.js

40 ms

fw-config-lazy.min.js

fw-config-lazy.min.js

88 ms

cc.js

cc.js

22 ms

main.min.1449849332.js

main.min.1449849332.js

33 ms

SEO Factors

tudiscovery.com SEO score

0

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

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

tudiscovery.com

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