5.2 sec in total
299 ms
4.7 sec
273 ms
Visit contenido.org now to see the best up-to-date CONTENIDO content for Germany and also check out these interesting facts you probably never knew about contenido.org
Das deutschsprachige Open Source Web Content Management System für (mehrsprachige) Plattformen und Portale
Visit contenido.orgWe analyzed Contenido.org page load time and found that the first response time was 299 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
contenido.org performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value7.7 s
3/100
25%
Value14.9 s
1/100
10%
Value1,380 ms
16/100
30%
Value0.572
12/100
15%
Value12.4 s
15/100
10%
299 ms
1379 ms
26 ms
311 ms
842 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 50% of them (18 requests) were addressed to the original Contenido.org, 42% (15 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Contenido.org.
Page size can be reduced by 633.6 kB (43%)
1.5 MB
833.4 kB
In fact, the total size of Contenido.org main page is 1.5 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. 40% of websites need less resources to load. Images take 620.3 kB which makes up the majority of the site volume.
Potential reduce by 19.2 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 19.2 kB or 67% of the original size.
Potential reduce by 4.2 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. CONTENIDO images are well optimized though.
Potential reduce by 353.1 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 353.1 kB or 69% of the original size.
Potential reduce by 257.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. Contenido.org needs all CSS files to be minified and compressed as it can save up to 257.1 kB or 84% of the original size.
We found no issues to fix!
17
17
The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CONTENIDO. According to our analytics all requests are already optimized.
contenido.org
299 ms
www.contenido.org
1379 ms
css
26 ms
dist.min.css
311 ms
startpage.min.js
842 ms
start_page.js
971 ms
contenido_rgb.png
99 ms
icon_search.png
1098 ms
xCONTENIDO_Startseite_headerbilder_A.jpeg.pagespeed.ic.jtcCgnoiVD.jpg
2426 ms
xCONTENIDO_Startseite_headerbilder_B.jpeg.pagespeed.ic.2WA3EfOOpx.jpg
2487 ms
xCONTENIDO_Startseite_headerbilder_C.jpeg.pagespeed.ic.JviVJjneJE.jpg
391 ms
icon_reduction_fix.png.pagespeed.ce.esOLRa5qlX.png
491 ms
icon_flag_fix.png.pagespeed.ce.xncYqS2deZ.png
592 ms
xCONTENIDO_Startseite_Parallax.jpeg.pagespeed.ic.kJHrE5KHvL.jpg
690 ms
xcontenido_aufbau.png.pagespeed.ic.hdL7i0timX.png
796 ms
4fb_white.png
721 ms
analytics.js
5 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
14 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
20 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
19 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
19 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
19 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
19 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
18 ms
PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff
19 ms
PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff
19 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
35 ms
PRmiXeptR36kaC0GEAetxkCDe67GEgBv_HnyvHTfdew.woff
36 ms
custom-icons.woff
846 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
35 ms
vzIUHo9z-oJ4WgkpPOtg1_esZW2xOQ-xsNqO47m55DA.woff
35 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
35 ms
collect
26 ms
loader.gif
169 ms
revicons.woff
104 ms
contenido.org 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
Links do not have a discernible name
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.
contenido.org 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
contenido.org 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contenido.org can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Contenido.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.
contenido.org
Open Graph description is not detected on the main page of CONTENIDO. 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: