671 ms in total
83 ms
365 ms
223 ms
Welcome to zimbra.org homepage info - get ready to check Zimbra best content for United States right away, or after learning these important things about zimbra.org
Visit zimbra.orgWe analyzed Zimbra.org page load time and found that the first response time was 83 ms and then it took 588 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
zimbra.org performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value5.8 s
15/100
25%
Value3.2 s
92/100
10%
Value40 ms
100/100
30%
Value0.115
86/100
15%
Value4.0 s
88/100
10%
83 ms
6 ms
12 ms
23 ms
19 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that all of those requests were addressed to Zimbra.org and no external sources were called. The less responsive or slowest element that took the longest time to load (83 ms) relates to the external source Forums.zimbra.org.
Page size can be reduced by 313.2 kB (37%)
856.7 kB
543.6 kB
In fact, the total size of Zimbra.org main page is 856.7 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. 45% of websites need less resources to load. Images take 471.3 kB which makes up the majority of the site volume.
Potential reduce by 65.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. This page needs HTML code to be minified as it can gain 20.8 kB, which is 28% 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 65.6 kB or 88% of the original size.
Potential reduce by 8.9 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. Zimbra images are well optimized though.
Potential reduce by 129.5 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 129.5 kB or 74% of the original size.
Potential reduce by 109.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. Zimbra.org needs all CSS files to be minified and compressed as it can save up to 109.1 kB or 80% of the original size.
Number of requests can be reduced by 20 (71%)
28
8
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zimbra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
forums.zimbra.org
83 ms
font-awesome.min.css
6 ms
stylesheet.css
12 ms
stylesheet.css
23 ms
jquery-3.6.0.min.js
19 ms
core.js
19 ms
forum_fn.js
27 ms
ajax.js
25 ms
normalize.css
15 ms
base.css
14 ms
utilities.css
13 ms
common.css
21 ms
links.css
15 ms
content.css
18 ms
buttons.css
16 ms
cp.css
18 ms
forms.css
19 ms
icons.css
20 ms
colours.css
23 ms
responsive.css
22 ms
flat.css
20 ms
colour-override.css
23 ms
stylesheet.css
15 ms
ZimbraForumBanner_background_3000px_225px.png
79 ms
laptopwithrocket.png
77 ms
site_logo.png
75 ms
forum_read.png
76 ms
forum_read_locked.png
76 ms
forum_read_subforum.png
76 ms
poppins-v3-latin-ext_latin-regular.woff
76 ms
poppins-v3-latin-ext_latin-600.woff
77 ms
bebaskai-regular-webfont.woff
8 ms
fontawesome-webfont.woff
13 ms
zimbra.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Links do not have a discernible name
zimbra.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
zimbra.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zimbra.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Zimbra.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.
zimbra.org
Open Graph description is not detected on the main page of Zimbra. 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: