Tools & Wizards About Us
blogs.sas.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

blogs.sas.com

SAS Blogs - SAS Blogs

Page Load Speed

2.7 sec in total

First Response

96 ms

Resources Loaded

2.2 sec

Page Rendered

372 ms

blogs.sas.com screenshot

About Website

Click here to check amazing Blogs SAS content for United States. Otherwise, check out these important facts you probably never knew about blogs.sas.com

Connecting you to people, products & ideas from SAS

Visit blogs.sas.com

Key Findings

We analyzed Blogs.sas.com page load time and found that the first response time was 96 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

blogs.sas.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.266

46/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

blogs.sas.com

96 ms

1419 ms

style.css

75 ms

styles.css

43 ms

wp-syntax.css

42 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 62% of them (57 requests) were addressed to the original Blogs.sas.com, 5% (5 requests) were made to Assets.adobedtm.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Blogs.sas.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 703.8 kB (49%)

Content Size

1.4 MB

After Optimization

734.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blogs.sas.com main page is 1.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 883.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 73.9 kB

  • Original 102.3 kB
  • After minification 101.3 kB
  • After compression 28.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 73.9 kB or 72% of the original size.

Image Optimization

-7%

Potential reduce by 26.1 kB

  • Original 396.4 kB
  • After minification 370.3 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. Blogs SAS images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 558.1 kB

  • Original 883.5 kB
  • After minification 878.6 kB
  • After compression 325.4 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 558.1 kB or 63% of the original size.

CSS Optimization

-81%

Potential reduce by 45.6 kB

  • Original 56.1 kB
  • After minification 38.2 kB
  • After compression 10.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. Blogs.sas.com needs all CSS files to be minified and compressed as it can save up to 45.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (55%)

Requests Now

87

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blogs 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 27 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

blogs.sas.com

blogs.sas.com

96 ms

1419 ms

style.css

style.css

75 ms

styles.css

styles.css

43 ms

wp-syntax.css

wp-syntax.css

42 ms

style.css

style.css

41 ms

jquery.js

jquery.js

233 ms

jquery-migrate.min.js

jquery-migrate.min.js

66 ms

sastheme.js

sastheme.js

88 ms

widgets.js

widgets.js

121 ms

in.js

in.js

6 ms

satelliteLib-392eedeb8633e1cc249f4de8df2bb2cfb4073228.js

satelliteLib-392eedeb8633e1cc249f4de8df2bb2cfb4073228.js

12 ms

style.css

style.css

52 ms

sastheme.css

sastheme.css

37 ms

reset.css

reset.css

54 ms

typography.css

typography.css

17 ms

2c-r-fixed.css

2c-r-fixed.css

20 ms

images.css

images.css

61 ms

default.css

default.css

33 ms

plugins.css

plugins.css

35 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

168 ms

plusone.js

plusone.js

97 ms

secureAnonymousFramework

secureAnonymousFramework

36 ms

dc.js

dc.js

48 ms

bodybg.jpg

bodybg.jpg

55 ms

header-main.jpg

header-main.jpg

90 ms

saslogo.png

saslogo.png

91 ms

mainbg.png

mainbg.png

31 ms

28.thumbnail.jpg

28.thumbnail.jpg

58 ms

open-data.jpg

open-data.jpg

273 ms

MgOpenModernaRegular.ttf

MgOpenModernaRegular.ttf

132 ms

__utm.gif

__utm.gif

19 ms

views_icon.png

views_icon.png

15 ms

comments_icon.png

comments_icon.png

38 ms

linkarrows.png

linkarrows.png

38 ms

dot.gif

dot.gif

52 ms

1040.thumbnail.jpg

1040.thumbnail.jpg

52 ms

1197.thumbnail.jpg

1197.thumbnail.jpg

71 ms

928.thumbnail.jpg

928.thumbnail.jpg

70 ms

134.thumbnail.png

134.thumbnail.png

78 ms

666.thumbnail.jpg

666.thumbnail.jpg

95 ms

369.thumbnail.jpg

369.thumbnail.jpg

95 ms

136.thumbnail.jpg

136.thumbnail.jpg

108 ms

53.thumbnail.png

53.thumbnail.png

110 ms

ga-audiences

ga-audiences

41 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

22 ms

941.thumbnail.jpeg

941.thumbnail.jpeg

17 ms

4.thumbnail.jpg

4.thumbnail.jpg

26 ms

274.thumbnail.jpg

274.thumbnail.jpg

20 ms

135.thumbnail.jpg

135.thumbnail.jpg

18 ms

466.thumbnail.jpg

466.thumbnail.jpg

37 ms

769.thumbnail.jpg

769.thumbnail.jpg

39 ms

1144.thumbnail.jpg

1144.thumbnail.jpg

39 ms

58.thumbnail.jpg

58.thumbnail.jpg

35 ms

531.thumbnail.jpg

531.thumbnail.jpg

22 ms

widget-bg.png

widget-bg.png

22 ms

268x88-va-ad.png

268x88-va-ad.png

24 ms

250.thumbnail.jpg

250.thumbnail.jpg

21 ms

483.thumbnail.jpg

483.thumbnail.jpg

18 ms

1124.thumbnail.jpg

1124.thumbnail.jpg

18 ms

footerbg.png

footerbg.png

59 ms

feed-icon-14x14.png

feed-icon-14x14.png

56 ms

footer-directorybg.gif

footer-directorybg.gif

57 ms

feed-icon-10x10.png

feed-icon-10x10.png

56 ms

addthis_widget.js

addthis_widget.js

11 ms

output.css

output.css

20 ms

os-99-0.js

os-99-0.js

37 ms

SASCXA.js

SASCXA.js

113 ms

wp-embed.min.js

wp-embed.min.js

18 ms

2813.js

2813.js

35 ms

os-ue-lib-1.1.0.js

os-ue-lib-1.1.0.js

31 ms

analytics.js

analytics.js

23 ms

26 ms

collect

collect

252 ms

collect

collect

253 ms

251 ms

session.js

session.js

250 ms

JavascriptInsert.js

JavascriptInsert.js

249 ms

satellite-566842cf64746d54aa002f76.html

satellite-566842cf64746d54aa002f76.html

243 ms

satellite-555e19946336300014130500.js

satellite-555e19946336300014130500.js

238 ms

satellite-555e1fdc33313200147a0600.js

satellite-555e1fdc33313200147a0600.js

238 ms

satellite-555e1fdc3331320014790600.html

satellite-555e1fdc3331320014790600.html

238 ms

300lo.json

300lo.json

30 ms

s

s

63 ms

u

u

82 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

38 ms

oct.js

oct.js

63 ms

insight.min.js

insight.min.js

31 ms

2813.js

2813.js

33 ms

adsct

adsct

88 ms

adsct

adsct

50 ms

15 ms

Accessibility Review

blogs.sas.com accessibility score

86

Accessibility Issues

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

blogs.sas.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

blogs.sas.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blogs.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 Blogs.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.

Social Sharing Optimization

blogs.sas.com

Open Graph data is detected on the main page of Blogs SAS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: