5.8 sec in total
127 ms
5.3 sec
397 ms
Click here to check amazing Runnymede Collegiate content. Otherwise, check out these important facts you probably never knew about runnymedecollegiate.com
Runnymede Collegiate Institute
Visit runnymedecollegiate.comWe analyzed Runnymedecollegiate.com page load time and found that the first response time was 127 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
runnymedecollegiate.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value6.4 s
9/100
25%
Value6.8 s
35/100
10%
Value760 ms
39/100
30%
Value0.03
100/100
15%
Value20.6 s
2/100
10%
127 ms
264 ms
107 ms
3715 ms
78 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Runnymedecollegiate.com, 69% (80 requests) were made to Schoolweb.tdsb.on.ca and 14% (16 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Schoolweb.tdsb.on.ca.
Page size can be reduced by 1.3 MB (50%)
2.7 MB
1.3 MB
In fact, the total size of Runnymedecollegiate.com main page is 2.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 64.7 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 64.7 kB or 65% of the original size.
Potential reduce by 106.1 kB
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. Obviously, Runnymede Collegiate needs image optimization as it can save up to 106.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 MB
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 1.1 MB or 73% of the original size.
Potential reduce by 104.9 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. Runnymedecollegiate.com needs all CSS files to be minified and compressed as it can save up to 104.9 kB or 85% of the original size.
Number of requests can be reduced by 48 (44%)
108
60
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runnymede Collegiate. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
runnymedecollegiate.com
127 ms
runnymedeci
264 ms
107 ms
Home.aspx
3715 ms
default.css
78 ms
module.css
49 ms
skin.css
83 ms
container.css
47 ms
schoolDefault.css
48 ms
portal.css
81 ms
prettyPhoto.css
115 ms
module.css
74 ms
ComboBox.Default.css
90 ms
jquery.min.js
138 ms
jquery-ui.min.js
204 ms
PanelBar.skindDefault.css
108 ms
jquery-1.6.1.min.js
129 ms
Telerik.Web.UI.WebResource.axd
121 ms
jquery.prettyPhoto.js
139 ms
jquery.qtip-1.0.0.js
208 ms
maps
53 ms
ScriptResource.axd
136 ms
Telerik.Web.UI.WebResource.axd
267 ms
dnn.js
137 ms
jquery.hoverIntent.min.js
138 ms
dnn.jquery.js
203 ms
ControlPanel.debug.js
205 ms
dnncore.js
205 ms
dnn.modalpopup.js
251 ms
nivo-slider.css
251 ms
jquery.nivo.slider.js
254 ms
initWidgets.js
249 ms
TDSB_Print_Logo.gif
90 ms
TDSB_Banner_Logo.gif
92 ms
Icon_Twitter.png
94 ms
Icon_Facebook.png
92 ms
Icon_YouTube.png
94 ms
Icon_Rss.png
132 ms
logo.gif
199 ms
m2sct1.jpg
142 ms
Runnymede%20is.jpg
93 ms
Runnymede%20is_YouTube.jpg
128 ms
913282046134.jpg
130 ms
homepg05.jpg
129 ms
IMG_022724678.JPG
147 ms
10528010_n56203.jpg
130 ms
homepg08.jpg
130 ms
homepg09.jpg
145 ms
homepg14.jpg
144 ms
homepg15.jpg
172 ms
903283446374.jpg
173 ms
927280110748.jpg
173 ms
432529632_n18525.jpg
190 ms
931275643833.jpg
189 ms
IMG_006926379.JPG
336 ms
IMG_008225513.JPG
327 ms
IMG_009222681.JPG
328 ms
IMG_014827327.JPG
336 ms
484508641_n43165.jpg
356 ms
2015%20St%20Louis.jpg
351 ms
Promo_AW.jpg
352 ms
mccarthy.jpg
307 ms
YouTubeChannel.jpg
319 ms
facebook-button.jpg
320 ms
Twitter.jpg
320 ms
Instagram.jpg
319 ms
runnymedeis.jpg
318 ms
Icon_Footer_Twitter.gif
318 ms
Icon_Footer_Facebook.gif
317 ms
transparent.gif
314 ms
analytics.js
12 ms
TDSB_Print_Logo.gif
246 ms
banner_bg_newton.jpg
246 ms
navArrow.gif
473 ms
Runnymede%20is.jpg
247 ms
collect
22 ms
shadow.png
427 ms
loading.gif
428 ms
Footer_DIV_DividerLine_Dark.jpg
200 ms
Icon_Footer_Contact_Phone_White.png
425 ms
Icon_Footer_Contact_Email_White.png
428 ms
Icon_Footer_Contact_Mail_White.png
428 ms
DotNetNukeAjaxShared.js
419 ms
common.js
133 ms
util.js
157 ms
geocoder.js
132 ms
map.js
148 ms
overlay.js
147 ms
marker.js
138 ms
StaticMapService.GetMapImage
194 ms
infowindow.js
185 ms
onion.js
70 ms
widgets.js
34 ms
ViewportInfoService.GetViewportInfo
77 ms
stats.js
23 ms
controls.js
18 ms
transparent.png
29 ms
css
61 ms
google4.png
49 ms
mapcnt6.png
43 ms
sv5.png
49 ms
marker.png
47 ms
tmapctrl.png
25 ms
cb_scout5.png
27 ms
tmapctrl4.png
25 ms
imgs8.png
84 ms
vt
22 ms
vt
16 ms
vt
16 ms
vt
18 ms
vt
24 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
11 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
12 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
12 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
22 ms
AuthenticationService.Authenticate
66 ms
runnymedecollegiate.com 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
Image elements do not have [alt] attributes
runnymedecollegiate.com 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
runnymedecollegiate.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Runnymedecollegiate.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 Runnymedecollegiate.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.
runnymedecollegiate.com
Open Graph description is not detected on the main page of Runnymede Collegiate. 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: