Report Summary

  • 68

    Performance

    Renders faster than
    80% 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

  • 89

    SEO

    Google-friendlier than
    67% of websites

facultyaccess.uchicago.edu

UChicago - Sign In

Page Load Speed

1.3 sec in total

First Response

84 ms

Resources Loaded

1 sec

Page Rendered

220 ms

facultyaccess.uchicago.edu screenshot

About Website

Welcome to facultyaccess.uchicago.edu homepage info - get ready to check Facultyaccess UChicago best content for United States right away, or after learning these important things about facultyaccess.uchicago.edu

Visit facultyaccess.uchicago.edu

Key Findings

We analyzed Facultyaccess.uchicago.edu page load time and found that the first response time was 84 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

facultyaccess.uchicago.edu performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

facultyaccess.uchicago.edu

84 ms

facultyaccess.uchicago.edu

128 ms

noaccess.php

24 ms

SSO;jsessionid=13frxqyd911qm1w8cokr0l8mqf

29 ms

proximanova.css

21 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Facultyaccess.uchicago.edu, 53% (21 requests) were made to Identitymanagement.uchicago.edu and 33% (13 requests) were made to Shibboleth2.uchicago.edu. The less responsive or slowest element that took the longest time to load (240 ms) relates to the external source Identitymanagement.uchicago.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.3 kB (9%)

Content Size

104.8 kB

After Optimization

95.5 kB

In fact, the total size of Facultyaccess.uchicago.edu main page is 104.8 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. Javascripts take 82.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 6.4 kB

  • Original 8.7 kB
  • After minification 8.1 kB
  • After compression 2.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 6.4 kB or 74% of the original size.

JavaScript Optimization

-2%

Potential reduce by 1.8 kB

  • Original 82.7 kB
  • After minification 82.5 kB
  • After compression 80.9 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

-9%

Potential reduce by 1.2 kB

  • Original 13.4 kB
  • After minification 13.4 kB
  • After compression 12.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. Facultyaccess.uchicago.edu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (67%)

Requests Now

36

After Optimization

12

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facultyaccess UChicago. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

facultyaccess.uchicago.edu accessibility score

100

Accessibility Issues

Best Practices

facultyaccess.uchicago.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

High

Page has valid source maps

SEO Factors

facultyaccess.uchicago.edu SEO score

89

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

    UTF-8

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

Social Sharing Optimization

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