8.9 sec in total
218 ms
8.3 sec
371 ms
Welcome to explainr.de homepage info - get ready to check Explainr best content for Germany right away, or after learning these important things about explainr.de
Erklärfilme. mit Profi-Skripten. Mit einer tollen Geschichte fängt es an. Unsere Skriptschreiber sind ausgewählte Drehbuchautoren, die für Film und Fernsehen arbeiten
Visit explainr.deWe analyzed Explainr.de page load time and found that the first response time was 218 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
explainr.de performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value6.8 s
7/100
25%
Value4.5 s
73/100
10%
Value1,920 ms
8/100
30%
Value0.146
77/100
15%
Value20.5 s
2/100
10%
218 ms
1286 ms
1645 ms
458 ms
438 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 57% of them (43 requests) were addressed to the original Explainr.de, 7% (5 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Pages.explainr.de.
Page size can be reduced by 735.8 kB (50%)
1.5 MB
732.2 kB
In fact, the total size of Explainr.de main page is 1.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 673.1 kB which makes up the majority of the site volume.
Potential reduce by 95.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 95.8 kB or 76% of the original size.
Potential reduce by 87 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. Explainr images are well optimized though.
Potential reduce by 437.4 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 437.4 kB or 65% of the original size.
Potential reduce by 202.5 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. Explainr.de needs all CSS files to be minified and compressed as it can save up to 202.5 kB or 87% of the original size.
Number of requests can be reduced by 43 (64%)
67
24
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Explainr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
explainr.de
218 ms
explainr.de
1286 ms
VY9ZDsIwDEQvVGMqPjhPcN3UkI3YQertiRRWyT8zT_Mkz0g5mSODNdcIZ5REoS2sSKqotgfWaUY_g4-ujPYdRq-ZxAWQ7hk4OkkdVX5okIUrlnYJQuhU2V5eNpPkdTriiTq7fcRKlTn99Nd-98Z1P0Tnk6xCUHJpBf_jdwG0SVjANo48HngC.css
1645 ms
M9TPy8xNyknVLcgvKknLz8nM18_MS84pTUkt1i8oSi0pqSzIyC_JR2YDAA.css
458 ms
M9TPy8xNyknVLcgvKknLz8nM18_MS84pTUktxpDRMcRUXJydmVesn5KalliaUwLmYVGlC5UvyCkt1gWpIV5hfllqUVEm0DUA.css
438 ms
font-awesome.min.css
348 ms
g1-dynamic-style.css
298 ms
galleria.classic.css
278 ms
css
66 ms
css
81 ms
nY1BDsIwDAQ_1MagvCgNFnWJ7TR2kOD1RFWl3rntYWYnwrZ3bJ8pnmNmerbkGJhkukPDtxV6YIPal0IZkhm6wWYnH3xFxtolr8FVi_0jDlhLd1I57BvEPJTXQbOOE6Fvu1bI3Vx5VLQ6ycwq5qN0JVKlHw.js
2649 ms
M9A3Ts7JTM4u1s8q1i9KLS7Iz0uB0XrFRckA.js
1582 ms
css
92 ms
0ccd5852dba56892ca0ea628fe8ebed94cd21c860f78024222399c8d5edfb49a.js
384 ms
M9RPzs8rSUwu0U3LL8rVNdfPzEvOKU1JLdbPAqLC0tSiSj2QjF5uZh4A.js
1495 ms
M9RPzs8rSUwu0U3LL8rVNdfPzEvOKU1JLdbPKtYvTi7KLCgpBgA.js
1629 ms
sort.js
456 ms
fY9RDoJADEQvxHZB_PEcnqAuDRRbwO0Sw-39WCEIiX-dl5lppvR1EA5P8715RR6Kck_610xxgTTOobu_eaIzAT2GWhShyLgdroIL3P4YU0dK5oOgGYeNwxfsUsIP31bOWCchZ8INxdx1hMXVh1GVhuQiTbKc3-cpTilhgwnXaav-NRMaD-3qyQoqqD8.js
1912 ms
M9A3Ts7JTM4u1s8q1k8qSk3MLsjPzCtBYQMA.js
1775 ms
dY1ZDsIwDEQv1MRlEUfgApwgOIa6TeKQRVVvjyq2IsqXR6N5fi3s0DEOGfoMaJLUYyJ7Igf9rVKa9LJTB73VGxUNDmSbdok-1mo0UxQOJcM7ac_he5uHJM6l1_0dPNXeXANfGFWUWON6-xfOXqR0GWfFWveBFHbsrCodeQIvdn5uCkvIzR7GqMifyc6eOw.js
2351 ms
M9TPy8xNyknVLcgvKknLz8nM18_MS84pTUkt1i8oSi0pqSzIyC_JR2YDAA.js
2023 ms
09dPzEqs0EvPz0_PSU0syCzWS87PBYvp52QmFeuXpyal5eeV6BvqmeiZw3h6WcUA.js
1941 ms
wp-emoji-release.min.js
282 ms
analytics.js
28 ms
collect
3 ms
collect
51 ms
Explainr-Logo-232%C3%9782.png
562 ms
hintergrund3.jpg
558 ms
laptop2.png
560 ms
ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf
146 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
146 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
147 ms
mtracking.gif
4147 ms
hintergrund2.png
740 ms
kapthon2-480x480.jpg
526 ms
C48-Dr.-Walter_Deutsch-480x480.jpg
679 ms
C52-German-Personnel-HD-480x480.jpg
677 ms
SiraMunich-300x300.jpg
678 ms
Meplan-300x300.jpg
677 ms
Mapping-Master-300x300.jpg
676 ms
Kunden2-bw.png
738 ms
facebook-48.png
723 ms
googleplus-48.png
721 ms
linkedin-48.png
722 ms
rss-48.png
718 ms
twitter-48.png
867 ms
vimeo-48.png
869 ms
xing-48.png
868 ms
userlike.min.js
466 ms
fontawesome-webfont.woff
361 ms
jquery.min.js
490 ms
revolution.extension.video.min.js
426 ms
revolution.extension.slideanims.min.js
428 ms
revolution.extension.layeranimation.min.js
429 ms
revolution.extension.navigation.min.js
439 ms
explainr.de
659 ms
ajax-loader.gif
369 ms
webfont.js
111 ms
userlikelib.min.js
83 ms
css
27 ms
578 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
12 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
11 ms
froogaloop2.min.js
53 ms
loader.gif
106 ms
85231645
84 ms
player.js
55 ms
player.css
58 ms
ga.js
29 ms
vuid.min.js
56 ms
__utm.gif
93 ms
proxy.html
60 ms
462446626.jpg
143 ms
spinner.gif
10 ms
tracker.js
40 ms
explainr.de 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
explainr.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
explainr.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Tap targets are not sized appropriately
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Explainr.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Explainr.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.
explainr.de
Open Graph data is detected on the main page of Explainr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: