2 sec in total
165 ms
1.5 sec
412 ms
Click here to check amazing Plone content for Democratic Republic of Congo. Otherwise, check out these important facts you probably never knew about plone.com
Plone is an open-source content management system (CMS) with over 20 years of stability and security wrapped in a modern, powerful user-centric package with Plone 6.
Visit plone.comWe analyzed Plone.com page load time and found that the first response time was 165 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
plone.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.2 s
5/100
25%
Value5.0 s
63/100
10%
Value460 ms
62/100
30%
Value0.164
72/100
15%
Value8.9 s
34/100
10%
165 ms
10 ms
61 ms
36 ms
247 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 87% of them (39 requests) were addressed to the original Plone.com, 4% (2 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (758 ms) belongs to the original domain Plone.com.
Page size can be reduced by 62.4 kB (13%)
468.8 kB
406.3 kB
In fact, the total size of Plone.com main page is 468.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 414.6 kB which makes up the majority of the site volume.
Potential reduce by 25.5 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. This page needs HTML code to be minified as it can gain 4.4 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.5 kB or 77% of the original size.
Potential reduce by 36.8 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. Plone images are well optimized though.
Potential reduce by 123 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 13 (31%)
42
29
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
plone.com
165 ms
resourcejquery-cachekey-5aafa6c87db86adc44268b391ad9dc80.css
10 ms
base-cachekey-19abca18333ca63653e79f1a45ecc3e4.css
61 ms
faceted_view-cachekey-00e6231918841d72fbac6b73e7577cd3.css
36 ms
resourceplone.app.jquery-cachekey-35f52531085409d521dcbe8153593cd0.js
247 ms
jquery.tinymce-cachekey-6fd1446fcd72f69a6a20f7ac6fed65a2.js
301 ms
faceted_view-cachekey-8941f4fcda61be7402683cf09a82c0fe.js
138 ms
resourcecarousel-cachekey-2bda3b2ef1501f5c23e71a0f78d1154e.js
48 ms
resourceplone.css
409 ms
themediazotheme.css
374 ms
style.css
296 ms
responsive.css
297 ms
css
392 ms
main.js
365 ms
logo-home.png
167 ms
image
758 ms
1.png
167 ms
2.png
162 ms
befdf4ea-bab4-4abe-8241-ede3295bffac.jpeg
76 ms
71297f1f-e354-4008-bfd0-9d910fc3b663.png
75 ms
logo3.png
167 ms
wildcard-corp
166 ms
syslab.com
195 ms
six-feet-up
193 ms
rackspace
223 ms
psw-group
169 ms
pretaweb
222 ms
jazkarta
241 ms
enfold-systems
332 ms
contextual-corp
311 ms
abstract
337 ms
plone_footer.png
337 ms
twitter.png
332 ms
facebook.png
415 ms
gtm.js
184 ms
nav_toggle.png
406 ms
search.png
406 ms
bg-content.png
352 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
228 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
265 ms
news_icon.png
265 ms
feature_icons.png
369 ms
spinner.gif
334 ms
analytics.js
173 ms
collect
80 ms
plone.com 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
plone.com 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
plone.com 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plone.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Plone.com 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.
plone.com
Open Graph description is not detected on the main page of Plone. 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: