2.9 sec in total
406 ms
2.3 sec
150 ms
Click here to check amazing Wayback Stanford content for United States. Otherwise, check out these important facts you probably never knew about wayback.stanford.edu
Visit wayback.stanford.eduWe analyzed Wayback.stanford.edu page load time and found that the first response time was 406 ms and then it took 2.5 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.
wayback.stanford.edu performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value6.0 s
13/100
25%
Value4.0 s
81/100
10%
Value130 ms
96/100
30%
Value0.658
8/100
15%
Value4.9 s
77/100
10%
406 ms
635 ms
580 ms
387 ms
62 ms
Our browser made a total of 18 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Wayback.stanford.edu, 61% (11 requests) were made to Swap.stanford.edu and 11% (2 requests) were made to Stanford.edu. The less responsive or slowest element that took the longest time to load (684 ms) relates to the external source Swap.stanford.edu.
Page size can be reduced by 176.9 kB (24%)
742.5 kB
565.6 kB
In fact, the total size of Wayback.stanford.edu main page is 742.5 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. Only 10% of websites need less resources to load. Images take 510.9 kB which makes up the majority of the site volume.
Potential reduce by 11.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 4.9 kB, which is 35% 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 11.2 kB or 81% of the original size.
Potential reduce by 34.0 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. Wayback Stanford images are well optimized though.
Potential reduce by 23.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 23.5 kB or 27% of the original size.
Potential reduce by 108.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. Wayback.stanford.edu needs all CSS files to be minified and compressed as it can save up to 108.2 kB or 83% of the original size.
Number of requests can be reduced by 7 (44%)
16
9
The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wayback Stanford. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
wayback.stanford.edu
406 ms
swap.stanford.edu
635 ms
bootstrap.min.css
580 ms
su-identity.css
387 ms
css
62 ms
styles.css
256 ms
su-wayback.css
258 ms
jquery.min.js
79 ms
bootstrap.min.js
348 ms
su-wayback.js
264 ms
analytics.js
39 ms
footer-stanford-logo@2x.png
94 ms
SUL-Logo-white-text-h25.png
255 ms
slac_1991.jpg
434 ms
slac_1994.jpg
684 ms
slac_1996.jpg
681 ms
slac_1999.jpg
610 ms
collect
12 ms
wayback.stanford.edu accessibility score
wayback.stanford.edu 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
wayback.stanford.edu 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
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 Wayback.stanford.edu 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 Wayback.stanford.edu 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.
wayback.stanford.edu
Open Graph description is not detected on the main page of Wayback Stanford. 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: