4.9 sec in total
350 ms
4.3 sec
209 ms
Click here to check amazing EXPLI content for Germany. Otherwise, check out these important facts you probably never knew about expli.de
Die große DIY Community zum Dokumentieren eigener Projekte und Bestaunen cooler Ideen in Form von Schritt für Schritt Anleitungen zum Selbermachen - How To, Anleitung, Ratgeber & Bauanleitungen.
Visit expli.deWe analyzed Expli.de page load time and found that the first response time was 350 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
expli.de performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value4.6 s
35/100
25%
Value4.9 s
65/100
10%
Value40 ms
100/100
30%
Value0.203
61/100
15%
Value4.4 s
83/100
10%
350 ms
1862 ms
460 ms
225 ms
222 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 66% of them (83 requests) were addressed to the original Expli.de, 6% (7 requests) were made to Apis.google.com and 3% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Expli.de.
Page size can be reduced by 349.1 kB (44%)
794.8 kB
445.7 kB
In fact, the total size of Expli.de main page is 794.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 401.0 kB which makes up the majority of the site volume.
Potential reduce by 89.9 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 89.9 kB or 86% of the original size.
Potential reduce by 40.7 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. EXPLI images are well optimized though.
Potential reduce by 174.0 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 174.0 kB or 74% of the original size.
Potential reduce by 44.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. Expli.de needs all CSS files to be minified and compressed as it can save up to 44.5 kB or 86% of the original size.
Number of requests can be reduced by 62 (51%)
121
59
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EXPLI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
expli.de
350 ms
www.expli.de
1862 ms
box.css
460 ms
columns.css
225 ms
fonts.css
222 ms
general.css
408 ms
image.css
315 ms
structure.css
277 ms
jquery.js
824 ms
general.js
529 ms
JSON.js
372 ms
all.js
151 ms
plusone.js
96 ms
widgets.js
6 ms
show_ads.js
36 ms
expli_logo.jpg
278 ms
register_dog_ear.jpg
299 ms
bubble_corner_top.gif
105 ms
expli_news.jpg
277 ms
2.jpg
274 ms
3.jpg
103 ms
halloween_lady.jpg
274 ms
pilzverkaeufer-132566954993_31237.jpg
274 ms
Amaretta.jpg
379 ms
BAT-127048022383_16643.jpg
379 ms
kakorei-135230179357_2344.jpg
394 ms
Fledervieh.jpg
378 ms
Lerchenweg.bmp
377 ms
segeltyp77.jpg
398 ms
hikmet.jpg
487 ms
barnyks.jpg
486 ms
marcert.jpg
482 ms
bunga-129364169087_18467.jpg
548 ms
newsletter_box_2_columns.jpg
608 ms
bauanleitung-vogelhaus-selber-bauen-124204489837_26756.jpg
519 ms
star_blue.gif
575 ms
star_grey.gif
604 ms
notebook-macbook-schreibtisch-pc-staender-selbr-machen-basteln-karton-billig-mod-arbeitsplatz-123670521065_28718.jpg
607 ms
windows-programme-deinstallieren-startmenue-12199331529_8328.jpg
609 ms
feed-icon.png
644 ms
145665244083_4408.jpg
671 ms
large_square_dummy_thumbnail.gif
677 ms
145569947939_2936.jpg
702 ms
145569799454_30989.jpg
719 ms
139749055593_26367.jpg
705 ms
145521305142_11655.jpg
739 ms
145521338856_13831.jpg
766 ms
14466626944_16172.jpg
769 ms
145225303137_22843.jpg
797 ms
145397534272_10047.png
802 ms
analytics.js
36 ms
145374133096_21120.jpg
806 ms
281 ms
cb=gapi.loaded_0
11 ms
collect
31 ms
xd_arbiter.php
210 ms
xd_arbiter.php
386 ms
zrt_lookup.html
41 ms
show_ads_impl.js
47 ms
144666385081_21587.jpg
740 ms
144611288027_20835.jpg
768 ms
ads
249 ms
osd.js
93 ms
ads
275 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
46 ms
cb=gapi.loaded_1
26 ms
fastbutton
115 ms
145080144156_1646.jpg
597 ms
14464566712_8105.jpg
628 ms
145209728354_7992.jpg
633 ms
144714646734_18367.jpg
657 ms
144499059486_9390.jpg
665 ms
postmessageRelay
47 ms
background.gif
668 ms
tweet_button.6a78875565a912489e9aef879c881358.de.html
14 ms
api.js
66 ms
core:rpc:shindig.random:shindig.sha1.js
93 ms
2536007149-postmessagerelay.js
70 ms
cb=gapi.loaded_0
42 ms
cb=gapi.loaded_1
44 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
48 ms
like.php
111 ms
background_header.jpg
591 ms
input_l.gif
621 ms
search.gif
625 ms
input_c.gif
655 ms
background_navigation_highlighted.gif
640 ms
background_navigation.gif
658 ms
css
62 ms
m_js_controller.js
28 ms
abg.js
29 ms
jot
145 ms
qbEHJxuVK5u.js
341 ms
LVx-xkvaJ0b.png
374 ms
background_blue_header_left.gif
581 ms
css
37 ms
background_blue_header_center.gif
606 ms
background_blue_header_right.gif
612 ms
favicon
88 ms
nessie_icon_tiamat_white.png
19 ms
s
41 ms
googlelogo_color_112x36dp.png
56 ms
x_button_blue2.png
42 ms
dark_upper_left_border.gif
618 ms
favicon
94 ms
dark_upper_right_border.gif
581 ms
dark_lower_left_border.gif
572 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
5 ms
PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf
8 ms
dark_lower_right_border.gif
552 ms
hr.gif
579 ms
background_grey_footer_left.gif
585 ms
background_grey_footer_right.gif
614 ms
background_grey_footer_center.gif
592 ms
input_r.gif
570 ms
button_left.gif
577 ms
button_right.gif
578 ms
button_center.gif
571 ms
background_grey_header_left.gif
601 ms
background_grey_header_right.gif
603 ms
background_grey_header_center.gif
566 ms
dog_ear_yellow_on_grey_large.png
581 ms
background_white_footer_left.gif
579 ms
background_white_footer_right.gif
581 ms
dog_ear_yellow_on_grey_small.png
602 ms
expli.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
expli.de 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
expli.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Expli.de can be misinterpreted by Google and other search engines. Our service has detected that German 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 Expli.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.
expli.de
Open Graph description is not detected on the main page of EXPLI. 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: