Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ots.loyola.edu

Web Login Service - Stale Request

Page Load Speed

461 ms in total

First Response

49 ms

Resources Loaded

297 ms

Page Rendered

115 ms

ots.loyola.edu screenshot

About Website

Visit ots.loyola.edu now to see the best up-to-date Ots Loyola content for United States and also check out these interesting facts you probably never knew about ots.loyola.edu

Visit ots.loyola.edu

Key Findings

We analyzed Ots.loyola.edu page load time and found that the first response time was 49 ms and then it took 412 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

ots.loyola.edu performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value400 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

ots.loyola.edu

49 ms

Login

23 ms

cireson.min.css

161 ms

login.min.css

65 ms

custom.css

49 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that all of those requests were addressed to Ots.loyola.edu and no external sources were called. The less responsive or slowest element that took the longest time to load (161 ms) belongs to the original domain Ots.loyola.edu.

Page Optimization Overview & Recommendations

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

Content Size

387.2 kB

After Optimization

86.8 kB

In fact, the total size of Ots.loyola.edu main page is 387.2 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 5% of websites need less resources to load. CSS take 266.0 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 2.6 kB

  • Original 3.8 kB
  • After minification 3.3 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 495 B, which is 13% 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 2.6 kB or 67% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 68 B
  • After minification 68 B

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. Ots Loyola images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 80.5 kB

  • Original 117.4 kB
  • After minification 104.8 kB
  • After compression 36.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 80.5 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 217.4 kB

  • Original 266.0 kB
  • After minification 262.6 kB
  • After compression 48.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. Ots.loyola.edu needs all CSS files to be minified and compressed as it can save up to 217.4 kB or 82% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ots Loyola. According to our analytics all requests are already optimized.

Accessibility Review

ots.loyola.edu accessibility score

100

Accessibility Issues

Best Practices

ots.loyola.edu best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ots.loyola.edu SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

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 Ots.loyola.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 Ots.loyola.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 Ots Loyola. 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: