5.3 sec in total
80 ms
4.9 sec
364 ms
Visit community.sitecore.net now to see the best up-to-date Community Sitecore content for United States and also check out these interesting facts you probably never knew about community.sitecore.net
Visit community.sitecore.netWe analyzed Community.sitecore.net page load time and found that the first response time was 80 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
community.sitecore.net performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value11.7 s
0/100
25%
Value11.7 s
4/100
10%
Value2,740 ms
3/100
30%
Value0.561
12/100
15%
Value15.1 s
7/100
10%
80 ms
3697 ms
217 ms
257 ms
322 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 56% of them (35 requests) were addressed to the original Community.sitecore.net, 44% (28 requests) were made to Doc.sitecore.net. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Community.sitecore.net.
Page size can be reduced by 1.1 MB (53%)
2.1 MB
985.6 kB
In fact, the total size of Community.sitecore.net main page is 2.1 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. Images take 835.1 kB which makes up the majority of the site volume.
Potential reduce by 105.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. This page needs HTML code to be minified as it can gain 27.4 kB, which is 23% 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 105.2 kB or 87% of the original size.
Potential reduce by 90.6 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. Obviously, Community Sitecore needs image optimization as it can save up to 90.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 526.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 526.5 kB or 75% of the original size.
Potential reduce by 396.9 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.sitecore.net needs all CSS files to be minified and compressed as it can save up to 396.9 kB or 89% of the original size.
Number of requests can be reduced by 19 (44%)
43
24
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Sitecore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
community.sitecore.net
80 ms
community.sitecore.net
3697 ms
layout.css
217 ms
jquery.min.js
257 ms
telligent.glow.min.js
322 ms
jquery.validate.min.js
181 ms
telligent.evolution.min.js
341 ms
plupload.silverlight.js
136 ms
screen.css
243 ms
webfonts.css
220 ms
sitecore_2D00_custom.css
283 ms
theme.js
285 ms
sitecore_2D00_custom.js
278 ms
dynamic-style
290 ms
WebResource.axd
313 ms
WebResource.axd
334 ms
WebResource.axd
334 ms
ui.js
267 ms
ui.js
267 ms
ui.js
267 ms
tablet.less
39 ms
FE5E7E8C106841CDA7354E834090C412.ashx
150 ms
logo.png_2D00_250x88.png
144 ms
new_2D00_banner_2D00_crop_5F00_1040x314px.jpg_2D00_1040x314x2.jpg
145 ms
anonymous.gif_2D00_44x44x2.png
144 ms
DEA401C517744EA688A924C6E0FB0F4F.ashx
149 ms
E8CD3027C9BB4B8D8C1FFCECD77E3746.ashx
149 ms
302A6F205A384D0C995FCE55C30D57F5.ashx
146 ms
4B4484C6C5D147939F27CE7091F3C471.ashx
147 ms
E55431692EF14F5CB294E80CC30BBEDE.ashx
147 ms
BF0037BFECF344B093307586D3D3F2CA.ashx
150 ms
3B5600BAA2094840B73AEFABDEF7232D.ashx
150 ms
99C7838AB50A4FC882A898F575C7757D.ashx
150 ms
B713797D3A944DE190419B3242C57D59.ashx
152 ms
872F40CD7C414430898BF9CE52F93B54.ashx
152 ms
98C86BC7C841401DBD53378DCD812EE6.ashx
152 ms
576197E25E5B41F39466ED6D83BCF6A2.ashx
166 ms
BD59C9E8163F46778A7D4E5546208270.ashx
166 ms
icons.png
117 ms
beta_2D00_ribbon.png
76 ms
302A6F205A384D0C995FCE55C30D57F5.ashx
408 ms
4B4484C6C5D147939F27CE7091F3C471.ashx
461 ms
E55431692EF14F5CB294E80CC30BBEDE.ashx
372 ms
E8CD3027C9BB4B8D8C1FFCECD77E3746.ashx
390 ms
FE5E7E8C106841CDA7354E834090C412.ashx
415 ms
DEA401C517744EA688A924C6E0FB0F4F.ashx
449 ms
BF0037BFECF344B093307586D3D3F2CA.ashx
544 ms
3B5600BAA2094840B73AEFABDEF7232D.ashx
489 ms
99C7838AB50A4FC882A898F575C7757D.ashx
545 ms
B713797D3A944DE190419B3242C57D59.ashx
517 ms
872F40CD7C414430898BF9CE52F93B54.ashx
520 ms
98C86BC7C841401DBD53378DCD812EE6.ashx
557 ms
kievit.svg
100 ms
entypo.svg
99 ms
entypo.woff
66 ms
kievit_2D00_light.svg
136 ms
576197E25E5B41F39466ED6D83BCF6A2.ashx
580 ms
BD59C9E8163F46778A7D4E5546208270.ashx
606 ms
kievit.woff
64 ms
entypo.woff
64 ms
kievit_2D00_light.woff
69 ms
print.css
41 ms
handheld.less
43 ms
community.sitecore.net 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
[aria-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
[role] values are not valid
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
community.sitecore.net 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
community.sitecore.net 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
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 Community.sitecore.net 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.sitecore.net 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.sitecore.net
Open Graph description is not detected on the main page of Community Sitecore. 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: