8.8 sec in total
147 ms
8.5 sec
157 ms
Click here to check amazing My Disneyland Paris content for United Kingdom. Otherwise, check out these important facts you probably never knew about my-disneyland.disneylandparis.co.uk
Visit my-disneyland.disneylandparis.co.ukWe analyzed My-disneyland.disneylandparis.co.uk page load time and found that the first response time was 147 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
my-disneyland.disneylandparis.co.uk performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value20.4 s
0/100
25%
Value9.1 s
14/100
10%
Value2,510 ms
4/100
30%
Value1.118
1/100
15%
Value21.0 s
1/100
10%
147 ms
271 ms
297 ms
409 ms
730 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 58% of them (36 requests) were addressed to the original My-disneyland.disneylandparis.co.uk, 13% (8 requests) were made to Sales.disneylandparis.com and 10% (6 requests) were made to Cdn.tagcommander.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain My-disneyland.disneylandparis.co.uk.
Page size can be reduced by 1.3 MB (68%)
2.0 MB
647.1 kB
In fact, the total size of My-disneyland.disneylandparis.co.uk main page is 2.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. 25% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 26.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 26.3 kB or 76% of the original size.
Potential reduce by 1.6 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, My Disneyland Paris needs image optimization as it can save up to 1.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 866.5 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 866.5 kB or 63% of the original size.
Potential reduce by 452.6 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. My-disneyland.disneylandparis.co.uk needs all CSS files to be minified and compressed as it can save up to 452.6 kB or 79% of the original size.
Number of requests can be reduced by 49 (83%)
59
10
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Disneyland Paris. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
login
147 ms
login
271 ms
tc_Disneylandparisfr_1.js
297 ms
modernizr-2.6.2.min.js
409 ms
DMI_init.css
730 ms
require.min.js
2063 ms
s_code.js
790 ms
tc_Disneylandparisfr_1.js
349 ms
style.css
86 ms
framework-jquery-top.min.js
510 ms
index.html
1892 ms
logoMyDLP.png
156 ms
peploading.gif
298 ms
597 ms
framework-bottom.min.js
145 ms
getcookie.php
648 ms
reach
501 ms
ac.php
660 ms
DMI_main.js
99 ms
config.js
292 ms
local.js
223 ms
MYDLP_config.js
196 ms
jquery-version.js
861 ms
fbds.js
330 ms
185 ms
212 ms
212 ms
s74964646638836
116 ms
cookie.min.js
249 ms
getcookie.php
324 ms
getcookie.php
229 ms
jquery-ui-1.10.3.custom.min.js
439 ms
fancyfields-1.2.js
3674 ms
xdate.js
299 ms
validatejs.js
306 ms
plugins.js
542 ms
mydlp-tabs.js
542 ms
clickAndToggle.js
543 ms
detect-orientation.js
451 ms
summaryBarError.js
532 ms
dialog.js
714 ms
tooltip.js
1060 ms
sort.js
799 ms
scroll.js
799 ms
calendar.js
811 ms
tooltip.js
1014 ms
load-modal.js
1055 ms
load-datepicker.js
1053 ms
jquery.mousewheel.js
952 ms
mydlp-populateForms.js
1109 ms
getPopinFromXml.js
2892 ms
css.js
1327 ms
tc_Disneylandparisfr_3.js
161 ms
s71653312470298
162 ms
setcookie.php
691 ms
getcookie.php
729 ms
privacy_20.js
170 ms
setcookie.php
378 ms
cross.png
66 ms
privacyHit.php
558 ms
jquery-ui-1.10.3.custom.css
1164 ms
fancyfields.css
1927 ms
my-disneyland.disneylandparis.co.uk 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
[role]s do not have all required [aria-*] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
my-disneyland.disneylandparis.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
my-disneyland.disneylandparis.co.uk SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My-disneyland.disneylandparis.co.uk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that My-disneyland.disneylandparis.co.uk 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.
my-disneyland.disneylandparis.co.uk
Open Graph description is not detected on the main page of My Disneyland Paris. 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: