5.9 sec in total
1.6 sec
4 sec
344 ms
Visit vocer.org now to see the best up-to-date VOCER content for Germany and also check out these interesting facts you probably never knew about vocer.org
Visit vocer.orgWe analyzed Vocer.org page load time and found that the first response time was 1.6 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
vocer.org performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value3.2 s
72/100
25%
Value4.2 s
78/100
10%
Value0 ms
100/100
30%
Value0.13
82/100
15%
Value3.1 s
95/100
10%
1593 ms
109 ms
213 ms
210 ms
215 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 93% of them (71 requests) were addressed to the original Vocer.org, 4% (3 requests) were made to Etracker.de and 1% (1 request) were made to Static.etracker.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Vocer.org.
Page size can be reduced by 381.8 kB (28%)
1.4 MB
981.7 kB
In fact, the total size of Vocer.org main page is 1.4 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. 35% of websites need less resources to load. Images take 875.6 kB which makes up the majority of the site volume.
Potential reduce by 40.1 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 40.1 kB or 80% of the original size.
Potential reduce by 55.3 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. VOCER images are well optimized though.
Potential reduce by 205.6 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 205.6 kB or 60% of the original size.
Potential reduce by 80.7 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. Vocer.org needs all CSS files to be minified and compressed as it can save up to 80.7 kB or 84% of the original size.
Number of requests can be reduced by 54 (72%)
75
21
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VOCER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
www.vocer.org
1593 ms
wp-emoji-release.min.js
109 ms
accordion.css
213 ms
normalize.css
210 ms
zenponsive.css
215 ms
style.css
216 ms
colorbox.css
212 ms
jquery.js
330 ms
jquery-migrate.min.js
315 ms
jquery.cookies.js
314 ms
socialshareprivacy.js
317 ms
facebook.js
318 ms
twitter.js
320 ms
gplus.js
420 ms
flattr.js
420 ms
socialshareprivacy.js
421 ms
facebook.js
422 ms
twitter.js
422 ms
gplus.js
431 ms
flattr.js
522 ms
jquery.cycle2.min.js
523 ms
jquery.cycle2.center.min.js
527 ms
jquery.cycle2.swipe.min.js
527 ms
ios6fix.js
528 ms
jquery.colorbox-min.js
535 ms
jquery.lazy.min.js
625 ms
jquery.iframeResizer.min.js
626 ms
jquery.localScroll.min.js
627 ms
jquery.scrollTo.min.js
628 ms
vocer.js
629 ms
e.js
328 ms
fonts.css
431 ms
vocer_2014.png
128 ms
searchicon.png
124 ms
dossier_der-neue-journalismus_illu-rita-kohel.jpg
519 ms
wahl-quiz.jpg
212 ms
dossier_der-dritte-weg_illu-fragment03-150x100.jpg
129 ms
kolumne_aus-den-laboren_ill-141x100.jpg
129 ms
crowdspondent-thumbnail-150x100.jpg
211 ms
autor_mark-heywinkel.jpg
429 ms
autorin_carla-baum.jpg
428 ms
autor_julian-gutberlet.jpg
537 ms
autor_thilo-kasper.jpg
727 ms
autor_stephan-weichert1.jpg
628 ms
autor_hendrik-holdmann.jpg
843 ms
12767363_1117271734971661_978944580_n.jpg
538 ms
boxheading_bordeaux.png
613 ms
PTS55F-webfont.woff
737 ms
vocericons.woff
636 ms
jquery-1.8.3.min.js
280 ms
201 ms
t.js
267 ms
socialshareprivacy.css
624 ms
dummy_twitter.png
618 ms
dummy_facebook.png
629 ms
dummy_gplus.png
711 ms
dummy_flattr.png
711 ms
PTS75F-webfont.woff
815 ms
PTS56F-webfont.woff
847 ms
cnt.php
194 ms
common.css
130 ms
buffer.css
207 ms
delicious.css
207 ms
disqus.css
242 ms
facebook.css
243 ms
flattr.css
310 ms
gplus.css
311 ms
hackernews.css
315 ms
linkedin.css
321 ms
mail.css
328 ms
pinterest.css
332 ms
reddit.css
415 ms
stumbleupon.css
416 ms
tumblr.css
416 ms
twitter.css
422 ms
xing.css
429 ms
vocer.org 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
Links do not have a discernible 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.
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.
vocer.org 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
Page has valid source maps
vocer.org 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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vocer.org can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Vocer.org 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.
vocer.org
Open Graph description is not detected on the main page of VOCER. 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: