2.7 sec in total
304 ms
2.1 sec
249 ms
Visit comstats.de now to see the best up-to-date Comstats content for Germany and also check out these interesting facts you probably never knew about comstats.de
Comstats bietet umfangreiche Statistiken und Zusatzfunktionen zum beliebten Fußballmanager Comunio
Visit comstats.deWe analyzed Comstats.de page load time and found that the first response time was 304 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
comstats.de performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value4.2 s
45/100
25%
Value5.7 s
52/100
10%
Value3,500 ms
1/100
30%
Value0.007
100/100
15%
Value12.5 s
14/100
10%
304 ms
321 ms
105 ms
315 ms
10 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 17% of them (13 requests) were addressed to the original Comstats.de, 9% (7 requests) were made to Googleads.g.doubleclick.net and 9% (7 requests) were made to Comstats.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Comstats.net.
Page size can be reduced by 457.4 kB (41%)
1.1 MB
657.0 kB
In fact, the total size of Comstats.de main page is 1.1 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 504.0 kB which makes up the majority of the site volume.
Potential reduce by 66.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 66.6 kB or 86% of the original size.
Potential reduce by 13.0 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. Comstats images are well optimized though.
Potential reduce by 324.9 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 324.9 kB or 64% of the original size.
Potential reduce by 52.9 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. Comstats.de needs all CSS files to be minified and compressed as it can save up to 52.9 kB or 76% of the original size.
Number of requests can be reduced by 51 (71%)
72
21
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Comstats. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and as a result speed up the page load time.
comstats.de
304 ms
www.comstats.de
321 ms
stylec.css
105 ms
jquery-ui-1.10.3.custom.min.css
315 ms
urchin.js
10 ms
jquery.min.js
34 ms
general.min.js
193 ms
jquery-ui-1.10.3.custom.min.js
299 ms
jquery.i18n.min.js
206 ms
click-tracker.min.js
204 ms
dict_de_DE.js
206 ms
sb.min.js
206 ms
jquery.flot.min.js
381 ms
jquery.flot.time.min.js
301 ms
charts.min.js
303 ms
overallvalues_100d.js
304 ms
adsbygoogle.js
8 ms
ga.js
16 ms
gpt.js
16 ms
rasen_cropped.jpg
1093 ms
comunio.de_top.png
339 ms
tp.gif
342 ms
all_icons5.png
638 ms
gradient_sprite.png
199 ms
__utm.gif
36 ms
pubads_impl_81.js
34 ms
clubs2016.png
413 ms
ca-pub-7337424045569701.js
168 ms
zrt_lookup.html
171 ms
show_ads_impl.js
133 ms
piwik.js
421 ms
container.html
40 ms
ads
365 ms
ads
83 ms
osd.js
13 ms
ads
325 ms
ads
179 ms
osd.js
8 ms
adj
122 ms
beacon
119 ms
m_js_controller.js
33 ms
abg.js
52 ms
favicon
72 ms
googlelogo_color_112x36dp.png
55 ms
nessie_icon_thin_arrow_big_white.png
30 ms
s
22 ms
x_button_blue2.png
18 ms
MINI-2907_DigitalBanner_300x600_TIER-2_FIND-A-DEALER.jpg
75 ms
lidar.js
27 ms
img;p.a=127481692;a=11147200808928;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=3737255178
66 ms
5273113
262 ms
dvtp_src.js
65 ms
sbhK2lTE.js
50 ms
adj
55 ms
beacon
48 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
10 ms
cTrvNaRi.html
8 ms
dvtp_src.js
34 ms
MINI-0456_Dealer_728X90_copy.gif
43 ms
5273113
244 ms
img;p.a=127485180;a=11147200808928;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=310660759
41 ms
dvtp_src_internal25.js
39 ms
pixel
121 ms
pixel
162 ms
t2tv7.html
185 ms
visit.js
170 ms
pixel
140 ms
pixel
139 ms
visit.js
108 ms
pixel
68 ms
avs5634.js
36 ms
event.gif
100 ms
event.gif
81 ms
event.gif
82 ms
Pix-1x1.gif
55 ms
event.jpg
72 ms
event.jpg
66 ms
sd
38 ms
comstats.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
<frame> or <iframe> elements do not have a title
comstats.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
comstats.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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Comstats.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Comstats.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.
comstats.de
Open Graph description is not detected on the main page of Comstats. 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: