Tools & Wizards About Us
osp.stanford.edu screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

osp.stanford.edu

Stanford University Proxy Server

Page Load Speed

5.3 sec in total

First Response

1.3 sec

Resources Loaded

4 sec

Page Rendered

127 ms

osp.stanford.edu screenshot

About Website

Click here to check amazing Osp Stanford content for United States. Otherwise, check out these important facts you probably never knew about osp.stanford.edu

Visit osp.stanford.edu

Key Findings

We analyzed Osp.stanford.edu page load time and found that the first response time was 1.3 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

osp.stanford.edu performance score

0

Network Requests Diagram

osp.stanford.edu

1252 ms

1363 ms

stanfordmodern.css

86 ms

ceebox-min.css

168 ms

jquery.min.js

333 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Osp.stanford.edu, 74% (14 requests) were made to Tools.stanford.edu and 11% (2 requests) were made to Stanford.edu. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Tools.stanford.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 15.6 kB (25%)

Content Size

63.4 kB

After Optimization

47.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Osp.stanford.edu main page is 63.4 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. Javascripts take 27.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 5.4 kB

  • Original 7.0 kB
  • After minification 5.5 kB
  • After compression 1.6 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 1.5 kB, which is 21% 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 5.4 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 53 B

  • Original 11.1 kB
  • After minification 11.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. Osp Stanford images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 320 B

  • Original 27.1 kB
  • After minification 27.1 kB
  • After compression 26.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-54%

Potential reduce by 9.8 kB

  • Original 18.1 kB
  • After minification 15.7 kB
  • After compression 8.3 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. Osp.stanford.edu needs all CSS files to be minified and compressed as it can save up to 9.8 kB or 54% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (20%)

Requests Now

15

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Osp 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 as a result speed up the page load time.

Network Requests Diagram

osp.stanford.edu

osp.stanford.edu

1252 ms

1363 ms

stanfordmodern.css

stanfordmodern.css

86 ms

ceebox-min.css

ceebox-min.css

168 ms

jquery.min.js

jquery.min.js

333 ms

stanfordmodern.js

stanfordmodern.js

416 ms

jquery.swfobject.js

jquery.swfobject.js

498 ms

jquery.ceebox-min.js

jquery.ceebox-min.js

500 ms

body_bg2.jpg

body_bg2.jpg

85 ms

icon_expanded.jpg

icon_expanded.jpg

85 ms

bg-sidebar-right.gif

bg-sidebar-right.gif

87 ms

raquo.gif

raquo.gif

89 ms

seal.jpg

seal.jpg

155 ms

search_box_bg.png

search_box_bg.png

159 ms

search_button.gif

search_button.gif

164 ms

banner.gif

banner.gif

306 ms

banner.gif

banner.gif

356 ms

handheld.css

handheld.css

76 ms

handheld.css

handheld.css

86 ms

SEO Factors

osp.stanford.edu SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Osp.stanford.edu can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Osp.stanford.edu main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

osp.stanford.edu

Open Graph description is not detected on the main page of Osp 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: