10.2 sec in total
350 ms
9.7 sec
189 ms
Visit community.single.de now to see the best up-to-date Community Single content for Germany and also check out these interesting facts you probably never knew about community.single.de
Online Dating mit Deutschlands beliebtester Singlebörse seit 2001 mit über 2 Millionen Mitgliedern. Hier verliebst Du Dich!
Visit community.single.deWe analyzed Community.single.de page load time and found that the first response time was 350 ms and then it took 9.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.
community.single.de performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value2.9 s
81/100
25%
Value5.7 s
52/100
10%
Value900 ms
31/100
30%
Value0
100/100
15%
Value9.5 s
30/100
10%
350 ms
457 ms
357 ms
562 ms
872 ms
Our browser made a total of 246 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Community.single.de, 17% (41 requests) were made to Static.single.de and 16% (39 requests) were made to Dmp.theadex.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Ad2.cdns.turn.com.
Page size can be reduced by 637.6 kB (61%)
1.0 MB
405.3 kB
In fact, the total size of Community.single.de main page is 1.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. 60% of websites need less resources to load. Javascripts take 725.0 kB which makes up the majority of the site volume.
Potential reduce by 57.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 57.6 kB or 81% of the original size.
Potential reduce by 11.1 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. Community Single images are well optimized though.
Potential reduce by 487.8 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 487.8 kB or 67% of the original size.
Potential reduce by 81.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. Community.single.de needs all CSS files to be minified and compressed as it can save up to 81.1 kB or 86% of the original size.
Number of requests can be reduced by 152 (77%)
198
46
The browser has sent 198 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Single. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
community.single.de
350 ms
single.013.css
457 ms
slimbox2.css
357 ms
jquery-1.3.2.min.js
562 ms
jquery-ui-1.7.2.custom.min.js
872 ms
slimbox2.js
359 ms
stace.php
330 ms
jquery-ui.css
461 ms
index13_jq.js
557 ms
praeludium_fn.js
222 ms
single_de.js
328 ms
iam.js
522 ms
GA_Singles_Community.js
326 ms
uma.php
113 ms
rea.js
207 ms
adex.js
258 ms
rc
227 ms
single.de_poweredby.jpg
210 ms
layout.2b.foot.png
104 ms
single_de_auf_den_ersten_klick.png
209 ms
layout.2b.boxfoot.png
105 ms
648e5b0fd5bc6c8b0741081072aa345e.jpg
106 ms
0b9b1881cb4b90e77026b800a9b07b26.jpg
108 ms
25ffead7e0e96cd556848e0e6d5a12ea.jpg
205 ms
1b08551af8a8b17e7b7f81f772da2703.jpg
206 ms
ec5d59a7674d6247f6151ef0a2142862.jpg
207 ms
31e8779bd76414443fab6611fa4e6f07.jpg
209 ms
e9c8f7cc7f135b905cd7a6c8840b61e3.jpg
305 ms
c7f390eaa84980aa9084f79a6000d8ad.jpg
306 ms
e92658d36c2dc32b49102bc0a4369973.jpg
307 ms
73603768e59f3eea7498cfe5400759d8.jpg
309 ms
5ed60bb2b58ff3d07761d7991da6b1fd.jpg
309 ms
ce4fa3aaeae764fb2417b6009c71eba7.jpg
310 ms
453bd02083dde28407b61d1f651ac11b.jpg
405 ms
7aad339c7e4025cbcb9e2a83baf6409e.jpg
404 ms
35d1634b0b3f7feac13109747dce2f3c.jpg
407 ms
dbc20c64e70a2153dd5a3a6bb4617351.jpg
409 ms
be12cf9790d66bf3d8a14db995dcd590.jpg
409 ms
4a0ae04370623115111f378fcbf04b48.jpg
410 ms
ee4ab9d8c5a7d86aa4f975f607a9bd40.jpg
506 ms
19f796d67ecdf87fbf1fd2ca075bd985.jpg
508 ms
dc59377232117d0223e7586ef7f7a153.jpg
508 ms
c18fd8db0a130fba89563c0a25158297.jpg
511 ms
16c1aa1d4b3014215dee7f3f541fbf27.jpg
512 ms
index.html
313 ms
tx.io
191 ms
tx.io
96 ms
Cookie
106 ms
t.js
89 ms
call.sjs
134 ms
1.gif
89 ms
analytic.js
169 ms
176 ms
Community_Singles;sz=728x90,728x180;adset=brs;;tile=1;prae=y;cnw=max;flash=no;ord=213665301790
330 ms
pixel
19 ms
redirect
271 ms
pixel
19 ms
cm.gif
88 ms
2.gif
90 ms
getads.js
9 ms
t.js
85 ms
redirect
376 ms
impr
95 ms
rtb
92 ms
match
91 ms
adex.js
91 ms
adition.js
256 ms
js
178 ms
loadImages.js
12 ms
1.gif
89 ms
analytic.js
86 ms
87 ms
2.gif
158 ms
0
91 ms
2.gif
91 ms
nuggad
90 ms
banner
176 ms
uid.html
90 ms
callback.js
4 ms
impr
92 ms
show_ads.js
4 ms
zrt_lookup.html
25 ms
show_ads_impl.js
38 ms
ads
202 ms
adex.js
88 ms
2.gif
85 ms
osd.js
21 ms
mtrcs_284704.js
285 ms
layout.2b.body.png
110 ms
fusse02.jpg
209 ms
button.bg.png
108 ms
167
88 ms
layout.2b.boxhead.png
107 ms
layout.2b.boxbody.png
105 ms
Community_Singles;sz=300x250;adset=brs;;tile=2;prae=y;cnw=max;flash=no;ord=213665301790
310 ms
1.gif
89 ms
analytic.js
86 ms
99 ms
usersync.gif
165 ms
27 ms
redirect
186 ms
UCookieSetPug
17 ms
generic
6 ms
100149051646250110
38 ms
2.gif
91 ms
2.gif
88 ms
generic
5 ms
2.gif
90 ms
UCookieSetPug
21 ms
2.gif
87 ms
12 ms
2.gif
144 ms
2.gif
144 ms
2.gif
137 ms
mtrcs_284704.js
12 ms
impr
110 ms
2.gif
90 ms
2.gif
90 ms
2.gif
88 ms
627
90 ms
rtb
96 ms
2.gif
87 ms
submit
280 ms
js
172 ms
1007
93 ms
banner
178 ms
impr
130 ms
ads
186 ms
mtrcs_284704.js
97 ms
Rest;sz=300x150;;tile=3;prae=y;cnw=max;flash=no;ord=213665301790
213 ms
1287
88 ms
pixel
52 ms
11204545574924786011
43 ms
abg.js
46 ms
m_js_controller.js
63 ms
googlelogo_color_112x36dp.png
87 ms
gum
207 ms
impr
97 ms
s
22 ms
x_button_blue2.png
23 ms
push
38 ms
rtb
97 ms
pixel
17 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
14 ms
pixel
24 ms
ads
242 ms
mtrcs_284704.js
97 ms
layout.2b.boxhead2.png
105 ms
Rest;sz=301x250;;tile=4;prae=y;cnw=max;flash=no;ord=213665301790
260 ms
1970
98 ms
0
112 ms
revoke
298 ms
push
33 ms
usersync.aspx
28 ms
dpixel
31 ms
ads.js
89 ms
Rest;sz=301x150;;tile=5;prae=y;cnw=max;flash=no;ord=213665301790
49 ms
0
120 ms
impr
95 ms
294 ms
rtb
92 ms
mtrcs_284704.js
98 ms
Rest;sz=302x150;;tile=6;prae=y;cnw=max;flash=no;ord=213665301790
47 ms
impr
96 ms
rtb
94 ms
show22.asp
281 ms
mtrcs_284704.js
97 ms
Community_Singles;sz=120x600,160x600,200x600,300x600;adset=brs;;tile=7;prae=y;cnw=max;flash=no;ord=213665301790
250 ms
submit
94 ms
revoke
309 ms
submit
95 ms
360 ms
2692
160 ms
activeview
41 ms
viewsterComscorePixels.js
43 ms
viewsterGoogleAnalytics.js
48 ms
hiro_dynamic_player.js
58 ms
jsinfo.asp
138 ms
beacon.js
10 ms
ga.js
85 ms
video-js.css
11 ms
PlayerWrapper.js
39 ms
viewster
167 ms
ddcssl.htm
3703 ms
fashionwzlogo.png
35 ms
fashionwz-static300x250.jpg
35 ms
push
50 ms
__utm.gif
28 ms
vjs.woff
4 ms
pixel
19 ms
activeview
12 ms
116358
742 ms
impr
97 ms
3190
93 ms
rtb
92 ms
adscaleRedirect
191 ms
impr
139 ms
3490
88 ms
rtb
93 ms
js
173 ms
3769
91 ms
banner
175 ms
113831
729 ms
1by1.png
5 ms
impr
91 ms
;bid=1250565055;sz=160x600;ord=1456847190624
189 ms
2.gif
169 ms
user-registering
96 ms
4158
95 ms
1397906714207402941
6 ms
adscale
13 ms
137 ms
submit
98 ms
1.gif
177 ms
4448
93 ms
lr.gif
18 ms
mtrcs_284704.js
97 ms
sf.shadow.png
108 ms
__utm.gif
11 ms
usermatchredir
16 ms
0
86 ms
revoke
109 ms
submit
95 ms
usersync.gif
83 ms
11 ms
redirect
188 ms
UCookieSetPug
14 ms
generic
6 ms
100149051646250110
23 ms
2.gif
91 ms
2.gif
97 ms
2.gif
123 ms
2.gif
169 ms
2.gif
168 ms
2.gif
93 ms
2.gif
93 ms
100250
881 ms
23388
32 ms
vagfp-npr-449.xml
7 ms
116358
1188 ms
submit
95 ms
pixel
17 ms
pql
19 ms
gw.js
177 ms
ui
14 ms
Cookie
111 ms
community.single.de accessibility score
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
Buttons do not have an accessible name
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
community.single.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
community.single.de 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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.single.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 Community.single.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.
community.single.de
Open Graph description is not detected on the main page of Community Single. 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: