2.9 sec in total
621 ms
2.1 sec
223 ms
Click here to check amazing Saylor content for United States. Otherwise, check out these important facts you probably never knew about saylor.org
Learn new skills, earn credit toward a degree, or advance your career at your own pace with free Saylor Academy courses!
Visit saylor.orgWe analyzed Saylor.org page load time and found that the first response time was 621 ms and then it took 2.3 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.
saylor.org performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value6.5 s
9/100
25%
Value6.5 s
39/100
10%
Value8,040 ms
0/100
30%
Value0.657
8/100
15%
Value16.5 s
5/100
10%
621 ms
12 ms
16 ms
14 ms
16 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 73% of them (66 requests) were addressed to the original Saylor.org, 11% (10 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (621 ms) belongs to the original domain Saylor.org.
Page size can be reduced by 2.2 MB (73%)
3.0 MB
826.1 kB
In fact, the total size of Saylor.org main page is 3.0 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. 75% 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. Javascripts take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 135.3 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 135.3 kB or 77% of the original size.
Potential reduce by 4.7 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. Saylor 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 72% of the original size.
Potential reduce by 403.2 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. Saylor.org needs all CSS files to be minified and compressed as it can save up to 403.2 kB or 86% of the original size.
Number of requests can be reduced by 64 (80%)
80
16
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saylor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
www.saylor.org
621 ms
wp-emoji-release.min.js
12 ms
prettyPhoto.css
16 ms
wp-video-lightbox.css
14 ms
layerslider.css
16 ms
layerslider.custom.css
17 ms
css
33 ms
styles.css
17 ms
nivo-lightbox.css
21 ms
default.css
18 ms
fontello.css
22 ms
animation.css
18 ms
fontello-ie7.css
25 ms
pagenavi-css.css
22 ms
css
48 ms
www.saylor.org
259 ms
bootstrap.css
24 ms
stmenu.css
36 ms
jquery-ui-1.7.3.custom.css
33 ms
style.css
30 ms
sttoolkit.css
36 ms
magnific-popup.css
40 ms
custom.css
37 ms
jquery.js
40 ms
jquery-migrate.min.js
41 ms
jquery.prettyPhoto.js
40 ms
video-lightbox.js
41 ms
layerslider.kreaturamedia.jquery.js
42 ms
greensock.js
40 ms
layerslider.transitions.js
42 ms
css
44 ms
saylor4.js
41 ms
jquery.fancybox-1.3.4.pack.js
44 ms
jquery.fancybox-1.3.4.css
67 ms
jquery.cycle.all.js
45 ms
addthis_widget.js
15 ms
wpaudio.min.js
47 ms
jquery.form.min.js
51 ms
scripts.js
48 ms
js
58 ms
nivo-lightbox.min.js
51 ms
script.js
48 ms
bootstrap.js
48 ms
core.min.js
49 ms
datepicker.min.js
49 ms
toolkit.min.js
72 ms
st-user.js
53 ms
underscore.min.js
57 ms
shortcode.min.js
54 ms
stmenu.js
57 ms
ddsmoothmenu.js
57 ms
custom.js
68 ms
comment-reply.min.js
61 ms
wp-embed.min.js
53 ms
saylor-academy-white.svg
29 ms
banner-OER-150x150.jpg
29 ms
banner-us-capitol-150x150.jpg
30 ms
Coding-vs-Theory-150x150.jpg
28 ms
banner-technical-writing-e1453309076914-150x150.jpg
238 ms
logo_sayloracademy_white_square-03.png
30 ms
courses-number-bg.jpg
214 ms
my-courses-bg.jpg
210 ms
why-saylor-bg.jpg
213 ms
footer-icon-fb.png
213 ms
footer-icon-twitter.png
213 ms
footer-icon-gplus.png
213 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
304 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
352 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
348 ms
BTu4SsVveqk58cdYjlaM9g.ttf
349 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
304 ms
vDvcuXwZxUMLuTfuLrSLpA.ttf
350 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
349 ms
zpv3sOKAbMf4wff105oLjw.ttf
351 ms
4cKlrioa77J2iqTqBgkRWg.ttf
381 ms
5pEc4QKTMA2oB4Hi9NkS4w.ttf
351 ms
websymbols-regular-webfont.woff
282 ms
main.js
583 ms
analytics.js
245 ms
skin.css
104 ms
soundmanager2-nodebug-jsmin.js
113 ms
wpaudio-play.png
101 ms
80x15.png
89 ms
wpaudio-pause.png
51 ms
collect
39 ms
collect
69 ms
nr-686.min.js
187 ms
300lo.json
15 ms
sh.7c7179124ea24ac6ba46caac.html
158 ms
custom-messages.ff94d8c06a032bf68fcb.js
151 ms
layers.3643cb2e25fb91c29386.js
10 ms
saylor.org 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 have valid values
ARIA IDs are not unique
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
saylor.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
saylor.org SEO score
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 Saylor.org 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 Saylor.org 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.
saylor.org
Open Graph description is not detected on the main page of Saylor. 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: