3.5 sec in total
785 ms
2.3 sec
464 ms
Welcome to community.good.com homepage info - get ready to check Community Good best content for India right away, or after learning these important things about community.good.com
Get answers to your questions about BlackBerry products and services including CylancePROTECT and CylanceOPTICS.
Visit community.good.comWe analyzed Community.good.com page load time and found that the first response time was 785 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
community.good.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value24.9 s
0/100
25%
Value15.9 s
0/100
10%
Value3,600 ms
1/100
30%
Value0.031
100/100
15%
Value33.1 s
0/100
10%
785 ms
312 ms
345 ms
225 ms
174 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 94% of them (59 requests) were addressed to the original Community.good.com, 3% (2 requests) were made to Ssl.google-analytics.com and 2% (1 request) were made to Img.en25.com. The less responsive or slowest element that took the longest time to load (785 ms) belongs to the original domain Community.good.com.
Page size can be reduced by 2.5 MB (71%)
3.5 MB
1.0 MB
In fact, the total size of Community.good.com main page is 3.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. 50% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 302.8 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 302.8 kB or 80% of the original size.
Potential reduce by 30.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. Community Good images are well optimized though.
Potential reduce by 1.7 MB
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 1.7 MB or 79% of the original size.
Potential reduce by 389.4 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. Community.good.com needs all CSS files to be minified and compressed as it can save up to 389.4 kB or 82% of the original size.
Number of requests can be reduced by 33 (58%)
57
24
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Good. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
welcome
785 ms
44fc2fb3d1dfcafdc54a4477b23629d6.js
312 ms
jive.css
345 ms
jive-icons.css
225 ms
groundwork-custom.css
174 ms
global-styles.css
245 ms
community-styles.css
234 ms
jive-widgets.css
365 ms
jive-videomodule.css
296 ms
managedsnippets.css
340 ms
idea.css
372 ms
quicktemplates.css
375 ms
apiDocument.css
373 ms
ExtendedAnalytics.css
375 ms
marketplace.css
378 ms
b08b89e3888f0588b6d2a57ae684acd9.js
345 ms
927c19b54a1809414403d17774b2c5ea.js
273 ms
e8c7c00600dc3cdc3c920d00f84dfb7b.js
430 ms
groundwork.all.js
166 ms
jquery.customSelect.min.js
165 ms
scripts.js
167 ms
good-communities-logo-n.png
167 ms
24.png
198 ms
j-ui-sprite.png
147 ms
searchbg.png
100 ms
jive-icon-sprites-sml.png
303 ms
SmilingGuyJoinAdminPortal.jpg
141 ms
images.png
165 ms
46.png
300 ms
jive-avatar-disabled.png
193 ms
46.png
300 ms
46.png
302 ms
46.png
302 ms
46.png
364 ms
32.png
373 ms
46.png
372 ms
46.png
372 ms
46.png
374 ms
32.png
389 ms
22.png
411 ms
22.png
471 ms
22.png
478 ms
22.png
473 ms
22.png
489 ms
22.png
489 ms
facebook-icon.png
461 ms
twitter-icon.png
516 ms
linkedin-icon.png
529 ms
youtube-icon.png
535 ms
jive-icon-sprites-sml.png
539 ms
j-ideas-sprites.png
495 ms
act-comment-bg.png
488 ms
jive-icon-sprites-med.png
637 ms
OpenSans-Regular.woff
607 ms
OpenSans-Light.woff
554 ms
OpenSans-Bold.woff
503 ms
928ddc86db216446efc8fcddba45a175.js
326 ms
ga.js
91 ms
ebb156989d13e623df9ccfd6f1db58b6.js
396 ms
elqCfg.min.js
77 ms
__utm.gif
12 ms
svrGP
225 ms
ordered
82 ms
community.good.com 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
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
community.good.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
community.good.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.good.com 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 Community.good.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.
community.good.com
Open Graph description is not detected on the main page of Community Good. 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: