Tools & Wizards About Us
weblogin.stanford.edu screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

weblogin.stanford.edu

Web Authentication and Authorization (was WebAuth) | University IT

Page Load Speed

3.6 sec in total

First Response

493 ms

Resources Loaded

3.1 sec

Page Rendered

1 ms

weblogin.stanford.edu screenshot

About Website

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

Visit weblogin.stanford.edu

Key Findings

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

Performance Metrics

weblogin.stanford.edu performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

weblogin.stanford.edu

493 ms

webauth

451 ms

webauth

331 ms

webauth

390 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

254 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Weblogin.stanford.edu, 72% (26 requests) were made to Uit.stanford.edu and 11% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Uit.stanford.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 442.4 kB (78%)

Content Size

567.1 kB

After Optimization

124.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Weblogin.stanford.edu main page is 567.1 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. 20% of websites need less resources to load. CSS take 359.4 kB which makes up the majority of the site volume.

HTML Optimization

-9%

Potential reduce by 10 B

  • Original 108 B
  • After minification 108 B
  • After compression 98 B

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. This web page is already compressed.

JavaScript Optimization

-70%

Potential reduce by 145.5 kB

  • Original 207.6 kB
  • After minification 178.4 kB
  • After compression 62.0 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 145.5 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 296.8 kB

  • Original 359.4 kB
  • After minification 347.1 kB
  • After compression 62.6 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. Weblogin.stanford.edu needs all CSS files to be minified and compressed as it can save up to 296.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (94%)

Requests Now

31

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

weblogin.stanford.edu

weblogin.stanford.edu

493 ms

webauth

webauth

451 ms

webauth

webauth

331 ms

webauth

webauth

390 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

254 ms

css_8WsBE51ZLaFfp0zwBAlE3X3LwLPjbG0g87gpHZu-DlA.css

css_8WsBE51ZLaFfp0zwBAlE3X3LwLPjbG0g87gpHZu-DlA.css

251 ms

css_b_V5rf2qKXfXoVMOGEx89EWxe3ycPAaCUJ73t5anm1o.css

css_b_V5rf2qKXfXoVMOGEx89EWxe3ycPAaCUJ73t5anm1o.css

338 ms

css_ZkUqnHCHG4qW55MrylMtK30A9SRgVPWYXgIOQgJDQ4M.css

css_ZkUqnHCHG4qW55MrylMtK30A9SRgVPWYXgIOQgJDQ4M.css

430 ms

stanford_itservices_custom.css

stanford_itservices_custom.css

264 ms

css_wHxt7EdVrNFym4sV7rLm_Tw1_dzZkWtJD6MxORJmc5k.css

css_wHxt7EdVrNFym4sV7rLm_Tw1_dzZkWtJD6MxORJmc5k.css

262 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

668 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

511 ms

jquery.once.js

jquery.once.js

510 ms

drupal.js

drupal.js

536 ms

google_cse.js

google_cse.js

596 ms

googleanalytics.js

googleanalytics.js

963 ms

bootstrap.min.js

bootstrap.min.js

786 ms

open_framework.js

open_framework.js

1074 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

793 ms

stanford-framework.js

stanford-framework.js

923 ms

stanford_itservices.js

stanford_itservices.js

1033 ms

footable.js

footable.js

1040 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

1213 ms

js_injector_10.js

js_injector_10.js

1179 ms

js_injector_11.js

js_injector_11.js

1210 ms

js_injector_12.js

js_injector_12.js

1286 ms

js_injector_15.js

js_injector_15.js

1297 ms

css

css

73 ms

css

css

85 ms

cse.js

cse.js

58 ms

jsapi

jsapi

50 ms

default+en.css

default+en.css

4 ms

default.css

default.css

18 ms

default+en.I.js

default+en.I.js

18 ms

default.css

default.css

21 ms

css_nTr55mbZYlMSsBXnLjRgu7jXCLkPIwg_iGLiIvrYokQ.css

css_nTr55mbZYlMSsBXnLjRgu7jXCLkPIwg_iGLiIvrYokQ.css

139 ms

Accessibility Review

weblogin.stanford.edu accessibility score

100

Accessibility Issues

Best Practices

weblogin.stanford.edu best practices score

83

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

SEO Factors

weblogin.stanford.edu SEO score

96

Search Engine Optimization Advices

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weblogin.stanford.edu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Weblogin.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

weblogin.stanford.edu

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