7.3 sec in total
297 ms
6.5 sec
469 ms
Click here to check amazing Content Captain content for Germany. Otherwise, check out these important facts you probably never knew about contentcaptain.de
Werde mit dem Content Captain zum Leuchtturm und biete deiner Branche Orientierung: Bleibe immer auf dem Laufenden und informiere Kunden und Mitarbeiter.
Visit contentcaptain.deWe analyzed Contentcaptain.de page load time and found that the first response time was 297 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
contentcaptain.de performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value9.3 s
1/100
25%
Value11.3 s
5/100
10%
Value120 ms
97/100
30%
Value0.002
100/100
15%
Value12.5 s
14/100
10%
297 ms
1171 ms
24 ms
96 ms
190 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 61% of them (49 requests) were addressed to the original Contentcaptain.de, 19% (15 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source I2.wp.com.
Page size can be reduced by 1.4 MB (63%)
2.3 MB
840.8 kB
In fact, the total size of Contentcaptain.de main page is 2.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 34.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 34.9 kB or 79% of the original size.
Potential reduce by 0 B
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. Content Captain images are well optimized though.
Potential reduce by 777.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 777.6 kB or 72% of the original size.
Potential reduce by 600.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. Contentcaptain.de needs all CSS files to be minified and compressed as it can save up to 600.5 kB or 86% of the original size.
Number of requests can be reduced by 46 (75%)
61
15
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Content Captain. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
contentcaptain.de
297 ms
1171 ms
css
24 ms
styles.css
96 ms
style.css
190 ms
easy-author-image.css
197 ms
style.css
190 ms
font-awesome.min.css
191 ms
style.min.css
198 ms
stylesheet.min.css
391 ms
style_dynamic.php
709 ms
responsive.min.css
282 ms
style_dynamic_responsive.php
650 ms
js_composer.css
286 ms
custom_css.php
644 ms
style.css
375 ms
jetpack.css
380 ms
jquery.js
565 ms
jquery-migrate.min.js
474 ms
script.js
480 ms
photon.js
565 ms
jquery.form.min.js
572 ms
scripts.js
660 ms
qppr_frontend_script.min.js
661 ms
ssba.min.js
667 ms
zerospam.js
732 ms
devicepx-jetpack.js
7 ms
gprofiles.js
54 ms
wpgroho.js
736 ms
qode-like.min.js
751 ms
plugins.js
1203 ms
jquery.carouFredSel-6.2.1.min.js
761 ms
lemmon-slider.min.js
794 ms
jquery.fullPage.min.js
824 ms
jquery.mousewheel.min.js
829 ms
jquery.touchSwipe.min.js
844 ms
isotope.pkgd.min.js
855 ms
default_dynamic.php
1377 ms
default.min.js
1014 ms
custom_js.php
1389 ms
e-201611.js
3 ms
comment-reply.min.js
934 ms
js_composer_front.js
867 ms
wp-embed.min.js
854 ms
wp-emoji-release.min.js
868 ms
style.css
744 ms
fbevents.js
247 ms
ga.js
62 ms
Bildschirmfoto-2016-03-04-um-13.20.14.png
3896 ms
Sandra-Staub-casual-nah-c-Elisabeth-und-Rainer-Zola120.jpg
2360 ms
Eggert-Portrait-150x150-140x140.jpg
513 ms
contentcaptain-logo.png
232 ms
contentcaptain-logo-white.png
231 ms
Fotos.jpg
508 ms
Strand_Wellenbraecher.jpg
507 ms
portr%C3%A4t-140x140.jpg
2257 ms
do7-0avPC2vxor6SN2THGA.ttf
170 ms
Li18TEFObx_yGdzKDoI_ci3USBnSvpkopQaUR-2r7iU.ttf
170 ms
ZKwULyCG95tk6mOqHQfRBC3USBnSvpkopQaUR-2r7iU.ttf
167 ms
cbAbzEjxTdN5KKmS-gA0tS3USBnSvpkopQaUR-2r7iU.ttf
171 ms
rr0ijB5_2nAJsAoZ6vECXaCWcynf_cDxXwCLxiixG1c.ttf
167 ms
STBOO2waD2LpX45SXYjQBS3USBnSvpkopQaUR-2r7iU.ttf
169 ms
WmVKXVcOuffP_qmCpFuyzS3USBnSvpkopQaUR-2r7iU.ttf
169 ms
QoPu455RxV2raYSIFXAMBS3USBnSvpkopQaUR-2r7iU.ttf
169 ms
Ji5epXNcpHu3r63lhS0cTi3USBnSvpkopQaUR-2r7iU.ttf
173 ms
5M21SdFLkD52QavfmHs6cA.ttf
165 ms
oOeFwZNlrTefzLYmlVV1UKCWcynf_cDxXwCLxiixG1c.ttf
165 ms
Pru33qjShpZSmG3z6VYwnaCWcynf_cDxXwCLxiixG1c.ttf
166 ms
BhNUF0UvSiDyKi5GMZK0cPesZW2xOQ-xsNqO47m55DA.ttf
166 ms
97uahxiqZRoncBaCEI3aW6CWcynf_cDxXwCLxiixG1c.ttf
168 ms
9_7S_tWeGDh5Pq3u05RVkqCWcynf_cDxXwCLxiixG1c.ttf
165 ms
fontawesome-webfont.woff
445 ms
__utm.gif
204 ms
210 ms
454 ms
hovercard.css
64 ms
services.css
94 ms
collect
58 ms
ajax-loader.gif
96 ms
g.gif
6 ms
contentcaptain.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
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.
contentcaptain.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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
contentcaptain.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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contentcaptain.de 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 Contentcaptain.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.
contentcaptain.de
Open Graph data is detected on the main page of Content Captain. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: