1.9 sec in total
73 ms
1.5 sec
300 ms
Click here to check amazing Support SAS content for United States. Otherwise, check out these important facts you probably never knew about support.sas.com
Looking for SAS software support? Visit SAS Support Home to find self-help resources including documentation, training, technical support and to access the community forum.
Visit support.sas.comWe analyzed Support.sas.com page load time and found that the first response time was 73 ms and then it took 1.8 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.
support.sas.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value4.4 s
38/100
25%
Value6.4 s
40/100
10%
Value5,150 ms
0/100
30%
Value0.205
60/100
15%
Value16.5 s
5/100
10%
73 ms
89 ms
451 ms
36 ms
61 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 34% of them (21 requests) were addressed to the original Support.sas.com, 23% (14 requests) were made to Sas.com and 7% (4 requests) were made to Analytics.twitter.com. The less responsive or slowest element that took the longest time to load (633 ms) relates to the external source Sas.com.
Page size can be reduced by 468.8 kB (47%)
988.2 kB
519.4 kB
In fact, the total size of Support.sas.com main page is 988.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 461.0 kB which makes up the majority of the site volume.
Potential reduce by 319.4 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 319.4 kB or 69% of the original size.
Potential reduce by 13 B
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. Support SAS images are well optimized though.
Potential reduce by 149.3 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 149.3 kB or 55% of the original size.
Potential reduce by 0 B
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. Support.sas.com has all CSS files already compressed.
Number of requests can be reduced by 38 (68%)
56
18
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support 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 26 to 1 for JavaScripts and as a result speed up the page load time.
support.sas.com
73 ms
support-home.html
89 ms
gtm.js
451 ms
launch-5d0b718ce8bb.min.js
36 ms
jquery.min.cee8557e8779d371fe722bbcdd3b3eb7.js
61 ms
utils.min.4a192b590a2c2926fb000264370c0588.js
59 ms
granite.min.543d214c88dfa6f4a3233b630c82d875.js
57 ms
jquery.min.dd9b395c741ce2784096e26619e14910.js
56 ms
shared.min.9f3716b2c473fd53ab31b1caa53131a8.js
57 ms
user_profile.min.b08069d5fdc98b158c0b083476ff853a.js
93 ms
static-6c9dcdd279b3f6bc70405d957c419f24.css
117 ms
button.min.60858364fb85b9ffe1bbda48cc43de22.js
59 ms
accordionwrapper.min.953607cf6923e8aaec993414d7c3507d.js
56 ms
contexthub
56 ms
encodings.min.f04cc6dea4b679fcee575fcc22494f86.js
57 ms
foundation_foot.min.818bd9dc519c98749e8ad5dd09bb5989.js
61 ms
jqueryui.min.a148de6b3165acb6ee6cf11ab828de30.css
414 ms
jqueryui.min.ce56079cb674d5bd22664f2c36e680c2.js
57 ms
static-6fab7d452bd36153ed8a79b769dd9c0a.min.js
58 ms
token.json
364 ms
633 ms
play-button.png
181 ms
0.gif
354 ms
wws-globe-icon.svg
355 ms
search-icon.svg
382 ms
contact-icon.svg
384 ms
dot-icon.svg
386 ms
image.1596466668348.png
385 ms
image.1596466668348.png
383 ms
image.1596466668348.png
384 ms
image.1596466668348.png
409 ms
1598365405133.png
409 ms
sasicons-103018.woff
417 ms
breadcrumb-pin.png
308 ms
footer-social-sprite-20.png
308 ms
3-dot-icon-wht.svg
311 ms
notice
286 ms
me
405 ms
js
122 ms
insight.min.js
219 ms
2813.js
219 ms
uwt.js
218 ms
pixel.js
199 ms
destination
209 ms
1006999.js
185 ms
up_loader.1.1.0.js
184 ms
rp.gif
142 ms
t2_2i2v4ir8_telemetry
117 ms
support.sas.com.json
127 ms
insight_tag_errors.gif
414 ms
adsct
191 ms
4f6dac1755531e013a53a30db644f2bf.js
18 ms
adsct
190 ms
profile-not-logged-in.svg
15 ms
adsct
143 ms
adsct
141 ms
adsct
223 ms
adsct
184 ms
adsct
214 ms
adsct
207 ms
li_sync
24 ms
support.sas.com 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-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
support.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
support.sas.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.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 Support.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.
support.sas.com
Open Graph data is detected on the main page of Support SAS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: