2.9 sec in total
180 ms
2.1 sec
562 ms
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.caWe 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.
policies.royalroads.ca performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value8.9 s
1/100
25%
Value10.1 s
9/100
10%
Value13,230 ms
0/100
30%
Value0.047
99/100
15%
Value21.5 s
1/100
10%
180 ms
214 ms
75 ms
46 ms
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 size can be reduced by 203.0 kB (47%)
428.3 kB
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.
Potential reduce by 196.1 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.
Potential reduce by 2.3 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.
Potential reduce by 4.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. Policies.royalroads.ca has all CSS files already compressed.
Number of requests can be reduced by 66 (79%)
84
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.
policies.royalroads.ca
180 ms
policies
214 ms
js
75 ms
google_tag.script.js
46 ms
miniorange_saml.admin.css
51 ms
ajax-progress.module.css
65 ms
align.module.css
87 ms
autocomplete-loading.module.css
89 ms
fieldgroup.module.css
86 ms
container-inline.module.css
87 ms
clearfix.module.css
85 ms
details.module.css
90 ms
hidden.module.css
105 ms
item-list.module.css
110 ms
js.module.css
106 ms
nowrap.module.css
107 ms
position-container.module.css
108 ms
progress.module.css
110 ms
reset-appearance.module.css
110 ms
resize.module.css
112 ms
sticky-header.module.css
111 ms
system-status-counter.css
115 ms
system-status-report-counters.css
112 ms
system-status-report-general-info.css
113 ms
tabledrag.module.css
120 ms
tablesort.module.css
119 ms
tree-child.module.css
118 ms
views.module.css
119 ms
search.min.css
117 ms
better_exposed_filters.css
119 ms
normalize.css
144 ms
normalize-fixes.css
142 ms
main.css
153 ms
jquery.min.js
137 ms
drupalSettingsLoader.js
129 ms
drupal.js
131 ms
drupal.init.js
131 ms
onpoint-predictor.min.js
135 ms
onpoint-search.min.js
130 ms
element.matches.js
130 ms
object.assign.js
116 ms
once.min.js
301 ms
jquery.once.min.js
296 ms
google_analytics.js
294 ms
jquery.once.bc.js
296 ms
main.js
297 ms
better_exposed_filters.js
295 ms
analytics.js
29 ms
collect
232 ms
logo.svg
128 ms
logo-light.svg
130 ms
collect
93 ms
Auto1Regular.ttf
79 ms
Auto1Light.ttf
79 ms
Auto1Bold.ttf
78 ms
Auto1Black.otf
79 ms
Auto1BoldSmCp.ttf
57 ms
Auto1RegularSmCp.ttf
151 ms
Auto1LightSmCp.ttf
150 ms
gtm.js
67 ms
collect
95 ms
collect
159 ms
conversion_async.js
70 ms
insight.min.js
217 ms
uwt.js
261 ms
1020.js
500 ms
fbevents.js
199 ms
js
102 ms
collect
100 ms
print.css
27 ms
activityi;src=5179265;type=invmedia;cat=gpyptoxt;ord=2266251431592;gtm=2wga30;auiddc=198207165.1664911242;~oref=https%3A%2F%2Fwww.royalroads.ca%2Fpolicies
383 ms
activityi;src=5179265;type=invmedia;cat=rdnct1nt;ord=2968667226820;gtm=2wga30;auiddc=198207165.1664911242;~oref=https%3A%2F%2Fwww.royalroads.ca%2Fpolicies
381 ms
activityi;src=9488552;type=royal0;cat=royal0;ord=2327623905148;gtm=2wga30;auiddc=198207165.1664911242;u1=https%3A%2F%2Fwww.royalroads.ca%2Fpolicies;~oref=https%3A%2F%2Fwww.royalroads.ca%2Fpolicies
378 ms
collect
139 ms
373 ms
js
98 ms
1221428491303646
173 ms
src=9488552;type=royal0;cat=royal0;ord=2327623905148;gtm=2wga30;auiddc=198207165.1664911242;u1=https%3A%2F%2Fwww.royalroads.ca%2Fpolicies;~oref=https%3A%2F%2Fwww.royalroads.ca%2Fpolicies
104 ms
src=5179265;type=invmedia;cat=rdnct1nt;ord=2968667226820;gtm=2wga30;auiddc=198207165.1664911242;~oref=https%3A%2F%2Fwww.royalroads.ca%2Fpolicies
130 ms
146 ms
71 ms
adsct
110 ms
adsct
109 ms
www.royalroads.ca.json
85 ms
src=5179265;type=invmedia;cat=gpyptoxt;ord=2266251431592;gtm=2wga30;auiddc=198207165.1664911242;~oref=https%3A%2F%2Fwww.royalroads.ca%2Fpolicies
45 ms
conversion.js
57 ms
32 ms
a18bb0e21d11a839b7adb013c92ee611.js
55 ms
35 ms
www.royalroads.ca.json
64 ms
34 ms
32 ms
44 ms
nr-1216.min.js
32 ms
policies.royalroads.ca accessibility score
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
Buttons do not have an accessible name
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
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
policies.royalroads.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
policies.royalroads.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
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.
policies.royalroads.ca
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: