3.2 sec in total
515 ms
2.5 sec
139 ms
Visit datebutler.de now to see the best up-to-date Datebutler content and also check out these interesting facts you probably never knew about datebutler.de
Visit datebutler.deWe analyzed Datebutler.de page load time and found that the first response time was 515 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
datebutler.de performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
515 ms
199 ms
207 ms
205 ms
309 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 55% of them (23 requests) were addressed to the original Datebutler.de, 38% (16 requests) were made to Social-bookmark-script.de and 2% (1 request) were made to Datebutler.jimdo.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Datebutler.jimdo.com.
Page size can be reduced by 244.4 kB (65%)
374.5 kB
130.0 kB
In fact, the total size of Datebutler.de main page is 374.5 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. 20% of websites need less resources to load. Javascripts take 246.7 kB which makes up the majority of the site volume.
Potential reduce by 14.6 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 14.6 kB or 79% of the original size.
Potential reduce by 10.4 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, Datebutler needs image optimization as it can save up to 10.4 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 182.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 182.5 kB or 74% of the original size.
Potential reduce by 37.0 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. Datebutler.de needs all CSS files to be minified and compressed as it can save up to 37.0 kB or 79% of the original size.
Number of requests can be reduced by 8 (20%)
40
32
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Datebutler. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
datebutler.de
515 ms
main.css
199 ms
layout.css
207 ms
font.css
205 ms
web.css
309 ms
logstate2-css.css
208 ms
web.js
1029 ms
shoppingcart.js
299 ms
textWithImage.js
307 ms
gallery.js
315 ms
bg.jpg
1034 ms
view.asp
348 ms
wong_trans.gif
307 ms
webnews_trans.gif
316 ms
kledy_trans.gif
316 ms
favoriten_trans.gif
317 ms
softigg_trans.gif
317 ms
linkarena_trans.gif
323 ms
readster_trans.gif
418 ms
icio_trans.gif
430 ms
favit_trans.gif
431 ms
bookmarksat_trans.gif
887 ms
linksilo_trans.gif
885 ms
folkd_trans.gif
439 ms
yigg_trans.gif
879 ms
facebook_trans.gif
544 ms
yahoo_trans.gif
545 ms
google_trans.gif
856 ms
top.jpg
122 ms
header.jpg
113 ms
emotionheader.jpg
118 ms
content.jpg
116 ms
balken.jpg
120 ms
herz.jpg
113 ms
cache_2694393462.jpg
230 ms
thumb_2694854162.png
218 ms
thumb_2694855262.jpg
220 ms
thumb_2694862762.jpg
220 ms
footer.jpg
225 ms
printer.gif
226 ms
onepixel.gif
215 ms
print.css
104 ms
datebutler.de accessibility score
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
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.
datebutler.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
datebutler.de SEO score
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
N/A
N/A
LATIN1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Datebutler.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Datebutler.de main page’s claimed encoding is latin1. 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.
datebutler.de
Open Graph description is not detected on the main page of Datebutler. 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: