5.2 sec in total
137 ms
4.7 sec
340 ms
Click here to check amazing Communities SAS content for United States. Otherwise, check out these important facts you probably never knew about communities.sas.com
Get SAS tips, share your knowledge, and find out about upcoming SAS-related events.
Visit communities.sas.comWe analyzed Communities.sas.com page load time and found that the first response time was 137 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
communities.sas.com performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value25.6 s
0/100
25%
Value15.7 s
0/100
10%
Value4,120 ms
1/100
30%
Value0.266
46/100
15%
Value26.4 s
0/100
10%
137 ms
2147 ms
148 ms
176 ms
266 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 12% of them (14 requests) were addressed to the original Communities.sas.com, 45% (52 requests) were made to Kntur85557.i.lithium.com and 23% (27 requests) were made to Sas.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Communities.sas.com.
Page size can be reduced by 1.5 MB (65%)
2.4 MB
843.7 kB
In fact, the total size of Communities.sas.com main page is 2.4 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. 45% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 494.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 200.4 kB, which is 36% 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 494.5 kB or 89% of the original size.
Potential reduce by 69.1 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, Communities SAS needs image optimization as it can save up to 69.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 884.6 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 884.6 kB or 71% of the original size.
Potential reduce by 93.7 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. Communities.sas.com needs all CSS files to be minified and compressed as it can save up to 93.7 kB or 87% of the original size.
Number of requests can be reduced by 33 (30%)
111
78
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Communities SAS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
check
137 ms
communities.sas.com
2147 ms
modernizr.js
148 ms
header-footer.css
176 ms
sas_skin-510462019.css
266 ms
prism.css
201 ms
prism.js
198 ms
satelliteLib-392eedeb8633e1cc249f4de8df2bb2cfb4073228.js
23 ms
lia-scripts-head-min.js
203 ms
en_us.pheader.html
640 ms
en_us.pfooter.html
107 ms
addthis_widget.js
49 ms
lia-scripts-common-min.js
263 ms
lia-scripts-body-min.js
272 ms
sas.js
114 ms
satellite-5698000a64746d79e6000412.js
31 ms
icon_thread_new.svg
245 ms
icon_tkb_thread_new.svg
246 ms
message_type_solved.svg
252 ms
icon_ideas.svg
250 ms
icon_thread.svg
253 ms
a71076_XiaKeshan_Photo.png
424 ms
1844i15FE2E9BD34FEC80
1251 ms
a64407_merrybell.png
613 ms
a72835_tempImage5947268897083534673.png
700 ms
a73123_Rausch_Nancy_04.png
827 ms
a71071_tempImage2246401904918172985.png
506 ms
icon_help.svg
41 ms
sas-employee-rank.png
40 ms
contributor-rank.png
40 ms
new-contributor-rank.png
39 ms
message
39 ms
message
189 ms
message
65 ms
message
230 ms
message
65 ms
message
213 ms
50x50
210 ms
0%2C0%2C1531%2C1531
243 ms
message
91 ms
50x50
119 ms
message
285 ms
50x50
409 ms
message
447 ms
message
408 ms
message
416 ms
message
266 ms
message
405 ms
message
458 ms
message
494 ms
message
541 ms
message
591 ms
message
684 ms
message
691 ms
message_has_url.svg
484 ms
message_has_image.svg
537 ms
occassional-contributor-rank.png
538 ms
frequent-contributor-rank.png
574 ms
message_has_attachment.svg
574 ms
regular-contributor-rank.png
589 ms
1429209335438.png
48 ms
sgf2016-users-logo.png
40 ms
super-contributor-rank.png
587 ms
new-user-rank.png
599 ms
community-super-user-ranking-icon.png
590 ms
j.php
26 ms
valued-guide-rank.png
573 ms
8%2C3%2C139%2C111
787 ms
48%2C11%2C167%2C132
788 ms
super-freq-rank.png
650 ms
respected-advisor-rank.png
648 ms
v.gif
6 ms
0%2C0%2C214%2C142
761 ms
trusted-advisor-rank.png
630 ms
message
605 ms
communities-menu-icon.png
392 ms
ideation-icon.png
348 ms
sas-TPTK-sprite.png
69 ms
1455303445002.png
69 ms
1455303445009.png
69 ms
1454959702194.png
69 ms
1454959702228.png
98 ms
1443210198315.png
140 ms
1456343264303.png
103 ms
1456343264386.png
103 ms
1456343264462.png
100 ms
1456343264550.png
99 ms
1456343265639.png
131 ms
1455025201562.png
129 ms
1454962288603.png
129 ms
1454962288640.png
137 ms
bb495831-ebf7-4423-9a14-ee11bf6b292f.woff
98 ms
b4199f62-4009-46e6-9359-5c262251c962.woff
131 ms
sasicons-41615.woff
130 ms
user-profiles-min.2.0.js
94 ms
jquery.js
168 ms
trackingCode.js
229 ms
social-sprite.png
91 ms
satellite-566842cf64746d54aa002f76.html
8 ms
satellite-55c4c97c393933001700036c.js
81 ms
satellite-55df4a6c66333400170000b8.js
82 ms
SASCXA.js
83 ms
oct.js
216 ms
session.js
485 ms
JavascriptInsert.js
497 ms
dc.js
182 ms
2813.js
99 ms
comm-hero-8.jpg
167 ms
300lo.json
88 ms
adsct
377 ms
adsct
378 ms
sh.7c7179124ea24ac6ba46caac.html
40 ms
s
339 ms
u
418 ms
layers.648fb6c882fbeb98be27.js
57 ms
ga-audiences
37 ms
communities.sas.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
communities.sas.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
communities.sas.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Communities.sas.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 Communities.sas.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.
communities.sas.com
Open Graph data is detected on the main page of Communities SAS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: