Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

policies.royalroads.ca

Policies, procedures, guidelines, directives & bylaws | Royal Roads University

Page Load Speed

2.9 sec in total

First Response

180 ms

Resources Loaded

2.1 sec

Page Rendered

562 ms

policies.royalroads.ca screenshot

About Website

Welcome to policies.royalroads.ca homepage info - get ready to check Policies Royal Roads best content for Canada right away, or after learning these important things about policies.royalroads.ca

Search Royal Roads University's policies, procedures, guidelines, directives and bylaws. Contact the Policy Office for questions.

Visit policies.royalroads.ca

Key Findings

We analyzed Policies.royalroads.ca page load time and found that the first response time was 180 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

policies.royalroads.ca performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value13,230 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

policies.royalroads.ca

180 ms

policies

214 ms

js

75 ms

google_tag.script.js

46 ms

miniorange_saml.admin.css

51 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Policies.royalroads.ca, 59% (55 requests) were made to Royalroads.ca and 5% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (500 ms) relates to the external source Script.crazyegg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.0 kB (47%)

Content Size

428.3 kB

After Optimization

225.3 kB

In fact, the total size of Policies.royalroads.ca main page is 428.3 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. 70% of websites need less resources to load. HTML takes 218.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 196.1 kB

  • Original 218.5 kB
  • After minification 177.9 kB
  • After compression 22.5 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 40.6 kB, which is 19% 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 196.1 kB or 90% of the original size.

JavaScript Optimization

-2%

Potential reduce by 2.3 kB

  • Original 118.5 kB
  • After minification 118.4 kB
  • After compression 116.1 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

-5%

Potential reduce by 4.6 kB

  • Original 91.3 kB
  • After minification 89.4 kB
  • After compression 86.7 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. Policies.royalroads.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 66 (79%)

Requests Now

84

After Optimization

18

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

Accessibility Review

policies.royalroads.ca accessibility score

77

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

Buttons do not have an accessible name

High

Links do not have a discernible name

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

policies.royalroads.ca 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

policies.royalroads.ca SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Policies.royalroads.ca 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 Policies.royalroads.ca 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 Policies Royal Roads. 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: