Tools & Wizards About Us
purdue.instructure.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

purdue.instructure.com

Log In to Canvas

Page Load Speed

1.1 sec in total

First Response

33 ms

Resources Loaded

831 ms

Page Rendered

195 ms

purdue.instructure.com screenshot

About Website

Visit purdue.instructure.com now to see the best up-to-date Purdue Instructure content for United States and also check out these interesting facts you probably never knew about purdue.instructure.com

Visit purdue.instructure.com

Key Findings

We analyzed Purdue.instructure.com page load time and found that the first response time was 33 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

purdue.instructure.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

purdue.instructure.com

33 ms

purdue.instructure.com

74 ms

login

61 ms

saml

68 ms

delegated_auth_pass_through

85 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 29% of them (4 requests) were addressed to the original Purdue.instructure.com, 50% (7 requests) were made to Purdue.edu and 14% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (85 ms) relates to the external source Sso.canvaslms.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 kB (61%)

Content Size

3.7 kB

After Optimization

1.4 kB

  • HTML

In fact, the total size of Purdue.instructure.com main page is 3.7 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. 15% of websites need less resources to load. HTML takes 3.7 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 2.3 kB

  • Original 3.7 kB
  • After minification 3.1 kB
  • After compression 1.4 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 558 B, which is 15% 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.3 kB or 61% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

purdue.instructure.com

purdue.instructure.com

33 ms

purdue.instructure.com

purdue.instructure.com

74 ms

login

login

61 ms

saml

saml

68 ms

delegated_auth_pass_through

delegated_auth_pass_through

85 ms

login

login

71 ms

login.css

login.css

28 ms

jquery.min.js

jquery.min.js

63 ms

jquery-ui.min.js

jquery-ui.min.js

85 ms

casLoginView.js

casLoginView.js

53 ms

bg.gif

bg.gif

29 ms

login-tile.jpg

login-tile.jpg

74 ms

login-bottom.gif

login-bottom.gif

33 ms

input_bg.gif

input_bg.gif

57 ms

Accessibility Review

purdue.instructure.com accessibility score

86

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

purdue.instructure.com 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

purdue.instructure.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

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

    EN

  • Encoding

    UTF-8

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

purdue.instructure.com

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