13.2 sec in total
297 ms
12.3 sec
587 ms
Click here to check amazing Besuch Disneyland Paris content for Germany. Otherwise, check out these important facts you probably never knew about besuch.disneylandparis.de
Alle Gästeservice-Angebote von Disneyland Paris ansehen
Visit besuch.disneylandparis.deWe analyzed Besuch.disneylandparis.de page load time and found that the first response time was 297 ms and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
besuch.disneylandparis.de performance score
297 ms
1255 ms
375 ms
645 ms
1017 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Besuch.disneylandparis.de, 30% (28 requests) were made to Cdn5.dlp-media.com and 11% (10 requests) were made to Opm-dnx.disneylandparis.com. The less responsive or slowest element that took the longest time to load (6.9 sec) relates to the external source Cdn1.dlp-media.com.
Page size can be reduced by 2.7 MB (59%)
4.5 MB
1.8 MB
In fact, the total size of Besuch.disneylandparis.de main page is 4.5 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. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 175.8 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 175.8 kB or 84% of the original size.
Potential reduce by 47.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. Besuch Disneyland Paris images are well optimized though.
Potential reduce by 1.5 MB
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 1.5 MB or 71% of the original size.
Potential reduce by 937.1 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. Besuch.disneylandparis.de needs all CSS files to be minified and compressed as it can save up to 937.1 kB or 72% of the original size.
Number of requests can be reduced by 38 (47%)
81
43
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Besuch 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 19 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
besuch.disneylandparis.de
297 ms
1255 ms
601c5506a6c6fad2b81488b938e08c50-boomerang-compiled.min.js
375 ms
c181158537ef4136e739c07401216419-screen.core2.min.css
645 ms
4038da832d3a27250115643d5fadfe49-screen.globalNavigation.min.css
1017 ms
35303852d77383d818c2edb6ec0b75f0-screen.core1.min.css
541 ms
c49329e6a1b1f46d7a78ee8cb41645a7-screen.finder.responsive.dlp.min.css
436 ms
727e1dae3fa7eb7b864ec6278e61e589-dlpmdx-icons.css
404 ms
efabc68f64c117c3fcb0d221ada5479b-languageMessage.desktop.css
1625 ms
4c866b6c89fc92532268e25b6fafc200-headScripts.min.js
338 ms
framework-top.min.js
43 ms
tc_Disneylandparisfr_1.js
129 ms
14c5829165198d9df144d52101756e52-wdpro.device.profiling.js
223 ms
6d9d8065995b11fe121ef36070619835-finder.responsive.core.min.js
2426 ms
9a3449a1f2e8ebe9093868e794f6aae6-finder.responsive.min.js
702 ms
8acb62b3c196942aabf60c3a4ef1e4b6-finder.responsive.desktop.min.js
1763 ms
framework-bottom.min.js
41 ms
tc_Disneylandparisfr_1.js
118 ms
fd05b123ac864a0911b2a41f24cbfb8c-pep.fontFaceObserver.js
1516 ms
prum.min.js
8 ms
style.css
59 ms
OPS_1-1.jpg
722 ms
e72856ac2d1337f5c992b4df37a9e8c9-sprite-xs-icons-profile.png
40 ms
d948b2f11891c1336923dd0cc17f12d9-peploading-sprite.png
41 ms
Facebook-25x25.png
42 ms
Twitter-25x25.png
41 ms
Instagram-25x25.png
41 ms
Youtube-25x25.png
41 ms
icon_googleplus_25x25.png
42 ms
Logo-forum-Go-DisneylandParis-25x25.png
42 ms
push_hp_data-collect_110x110.png
357 ms
push_hp_go-dlp_110x110_v1.png
372 ms
n018001_2018jan01_disney-castle_1-1.jpg
637 ms
N022358_28-03-2017.jpg
573 ms
push_megamenu-product_data-collect_110x110_v2.jpg
439 ms
n016624_2021apr04_spring2014_parade-donald-daisy_1-1_500x500.jpg
658 ms
449113086-0320bz-1675gv_2065dec31_mobile-app-visual-usa_1-1.jpg
651 ms
push_megamenu-offer_tgu_110x110.png
580 ms
push_menu-offer_early-booker_110x110.png
650 ms
3bc6498b548bc2f3ca2d03dcf799e0ce-avenir55roman.woff
16 ms
1a6f112b4fc114dd745b05ddd253e440-avenir35light.woff
7 ms
1b137251e4ff39c8d7fcc8bc5011f048-avenir85heavy.woff
7 ms
edf17b4d1d69c62f4afb58ba90150b3a-avenir95black.woff
15 ms
819ef74265062fab243936b78904f767-pep_icon_font15-webfont.woff
15 ms
fa39ec41fead9a135ad54de3c74053ae-avenir55romanoblique.woff
14 ms
343a09007227fb5676de6f4f90ba96ee-avenir35oblique.woff
15 ms
0e7ab3c60b70f005a2d536ac1ab96b59-dlp_pep_icon8-webfont.woff
35 ms
translate
408 ms
170 ms
getcookie.php
175 ms
reach
181 ms
8692e6efddf882acbff144c38ea7dfdf-ui-bg_flat_75_ffffff_40x100.png
61 ms
232 ms
beacon.js
35 ms
8e265d3c049d814d78b19f77862f3839-sprite-xs-icons-interactive.png
33 ms
ac.php
162 ms
ajax
31 ms
ce28976da9883a56d9a2eb6a73048dba-dcl_pep_icon5-webfont.woff
10 ms
getcookie.php
150 ms
s17470655539073
85 ms
74ce98d8ba6e29c3523c808992786b0b-services.png
160 ms
b8d347827ed9d704a584d3702b950656-screen.finder.responsive.no-mq.min.css
374 ms
2c692376d389908f783ffa2f7a4d10c1-screen.finder.responsive.desktop.no-mq.min.css
161 ms
91b86e2543761264a03ab8cee8a9a8b2-finder.responsive.lazyLoad.desktop.min.js
88 ms
getcookie.php
160 ms
DLP_Automated-External-Defibrillators_16-9.jpg
101 ms
tc_Disneylandparisfr_3.js
60 ms
setcookie.php
247 ms
getcookie.php
240 ms
privacy_39.js
32 ms
setcookie.php
219 ms
privacyHit.php
184 ms
cross.png
31 ms
translate
260 ms
peploading.gif
82 ms
DLP_Air-Travel-to-DLP_16-9.jpg
1034 ms
DLP_Guests-with-Disabilities-or-Special-Needs_16-9.jpg
102 ms
DLP_Guests-with-Hearing-Disabilities_16-9.jpg
1015 ms
DLP_Guests-with-Visual-Disabilities_16-9.jpg
105 ms
DLP_Storage-of-Special-Products_16-9.jpg
98 ms
DLP_Visiting-DLP-with-Children_16-9.jpg
729 ms
DLP_Guests-with-Disabilities-or-Special-Needs_16-9.jpg
694 ms
DLP_Visitor-Relations-at-City-Hall_16-9.jpg
6880 ms
DLP_Guests-with-Special-Dietary-Needs_16-9.jpg
1046 ms
DLP_Guests-with-Mental-or-Cognitive-Disabilities_16-9.jpg
98 ms
DLP_Guests-with-Photosensitive-Epilepsy_16-9.jpg
96 ms
5a41157f6983c0285ec87035ae892dd6-pep-places-webfont.woff
4 ms
s17656660231295
85 ms
chartbeat.js
25 ms
f8ef2cce7a12ce84d1ec303343351872-languageSelection.min.js
88 ms
boomerang.cloud.go.com
259 ms
ping
8 ms
beacon.gif
72 ms
besuch.disneylandparis.de SEO score
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Besuch.disneylandparis.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Besuch.disneylandparis.de 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.
besuch.disneylandparis.de
Open Graph description is not detected on the main page of Besuch 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: