4.5 sec in total
167 ms
2.4 sec
2 sec
Click here to check amazing Disney content. Otherwise, check out these important facts you probably never knew about disney.cl
Descubre todo lo que necesitas saber acerca de las películas de Disney, espectáculos y musicales en directo, viajes y últimas novedades en productos Disney.
Visit disney.clWe analyzed Disney.cl page load time and found that the first response time was 167 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
disney.cl performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value13.7 s
0/100
25%
Value7.8 s
24/100
10%
Value3,180 ms
2/100
30%
Value0
100/100
15%
Value21.7 s
1/100
10%
167 ms
310 ms
543 ms
375 ms
348 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Disney.cl, 87% (39 requests) were made to Static-mh.content.disney.io and 2% (1 request) were made to Disneylatino.com. The less responsive or slowest element that took the longest time to load (688 ms) relates to the external source A.dilcdn.com.
Page size can be reduced by 3.3 MB (83%)
4.0 MB
674.4 kB
In fact, the total size of Disney.cl main page is 4.0 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. 65% of websites need less resources to load. HTML takes 3.0 MB which makes up the majority of the site volume.
Potential reduce by 2.7 MB
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 2.7 MB or 89% of the original size.
Potential reduce by 102 B
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. Disney images are well optimized though.
Potential reduce by 191.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 191.9 kB or 52% of the original size.
Potential reduce by 470.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. Disney.cl needs all CSS files to be minified and compressed as it can save up to 470.4 kB or 73% of the original size.
Number of requests can be reduced by 32 (82%)
39
7
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Disney. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
disney.cl
167 ms
disneylatino.com
310 ms
jquery-dc8b911876ec.js
543 ms
application-82a34c192ca6.css
375 ms
background_styles-1903f7131478.css
348 ms
flex_content_hero-e144966a60f5.css
346 ms
card_grid-ba4fbc42fc89.css
347 ms
slider-138449799a03.css
347 ms
rich_image-7ac318d6c07a.css
375 ms
flex_grid-e3aa5510ca33.css
377 ms
links_footer-497c8e53b53f.css
376 ms
flex_content_hero-b2e324c2f1d2.css
372 ms
card_grid-4e0de3f0929a.css
385 ms
slider-b8208775cd7e.css
389 ms
rich_image-2e839cec85d4.css
386 ms
flex_grid-351547b4e970.css
384 ms
application-fbb3bd8fc764.css
404 ms
disneyuschrome-37ee2f6054c8.css
397 ms
incredibles_search-24807f0c54c2.css
397 ms
head-56277e6a3815.js
400 ms
espn-web-player-bundle.min.js
292 ms
OneID.js
340 ms
application-92d73c342f88.js
416 ms
background_styles-988c5423ca62.js
158 ms
pushdown-e75353a9ca3e.js
197 ms
flex_content_hero-a09207e1b93c.js
166 ms
card_grid-8439406d7604.js
166 ms
slider-20bbcbb161ba.js
172 ms
rich_image-d700628f98ca.js
177 ms
flex_grid-b0c2b068f4d3.js
183 ms
links_footer-81077a392a77.js
188 ms
disneyuschrome-desktop-e34d2438f086.css
11 ms
disneylatino.com.js
688 ms
disneyuschrome-32e8a05c2d65.js
589 ms
636 ms
disney_logo_dark@2x-45d70f7dd57b.png
443 ms
inc-search-input-icon-blue-331475a2cf98.svg
441 ms
disney_logo_dark-baa807690db7.png
55 ms
icon_play_light-a1134bbf894d.svg
58 ms
matterhorn-regular-eed88f0756d6.woff
54 ms
m4-b366701d6945.woff
52 ms
matterhorn-semibold-274588bf380a.woff
56 ms
matterhorn-bold-5c32f7bb9baf.woff
53 ms
social_modal_sprite-a5edf581acbd.png
16 ms
disneyuschrome-mobile-39fc724540e9.css
27 ms
disney.cl accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
disney.cl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
disney.cl SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
ES
ES
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Disney.cl 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 Disney.cl main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
disney.cl
Open Graph data is detected on the main page of Disney. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: