4.1 sec in total
89 ms
2.4 sec
1.6 sec
Welcome to ie.dal.ca homepage info - get ready to check Ie Dal best content for Canada right away, or after learning these important things about ie.dal.ca
Visit ie.dal.caWe analyzed Ie.dal.ca page load time and found that the first response time was 89 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ie.dal.ca performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value12.4 s
0/100
25%
Value13.7 s
2/100
10%
Value1,800 ms
9/100
30%
Value0.194
63/100
15%
Value31.4 s
0/100
10%
89 ms
132 ms
130 ms
109 ms
125 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Ie.dal.ca, 48% (41 requests) were made to Cdn.dal.ca and 9% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (771 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 188.2 kB (2%)
8.9 MB
8.7 MB
In fact, the total size of Ie.dal.ca main page is 8.9 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. 85% 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. Images take 8.6 MB which makes up the majority of the site volume.
Potential reduce by 50.6 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 50.6 kB or 83% of the original size.
Potential reduce by 128.0 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. Ie Dal images are well optimized though.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 3.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. Ie.dal.ca has all CSS files already compressed.
Number of requests can be reduced by 62 (78%)
80
18
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ie Dal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
ie.dal.ca
89 ms
ie.dal.ca
132 ms
industrial.html
130 ms
jquery-ui.lt_39f0d37a60fbd501f32c59f84fd34f75.min.css
109 ms
jquery-ui.lt_d15c3c2fe8bb0b57e2fd329b0ba8ab7c.min.css
125 ms
selectNav.lt_5135b360db8e63ccf56b2a5b98325d90.min.css
99 ms
default.lt_d1ffb378fdfb2645b954f3ae6d711df6.min.css
114 ms
default-theme.lt_d2a466252c6d5b7b09cad65e9e909f9f.min.css
101 ms
programs-theme.lt_983eb1cebc5d144bc3cc7455cefba751.min.css
127 ms
jquery.lt_1fc733054ddb2e2fcd4a0f763671047b.min.js
130 ms
jquery-ui.lt_99d8b552b0168e049b4d8a2d5568e57e.min.js
146 ms
jquery.uniform.lt_7dc7bb06854120382202ad7d19325443.min.js
118 ms
selectNav.lt_84c84a606a4e81f8b597406bf7043c5d.min.js
120 ms
purl.lt_53badcd063ce67004f6c8ed95110a740.min.js
118 ms
default.lt_41cfd59d5a7becfcdec68fdaf716a9df.min.js
119 ms
css2
111 ms
all.min.css
120 ms
300 ms
toolsNavigationHeader.lt_eef32f46f7e250ab2d22a8001ce2384e.min.css
128 ms
toolsNavigationHeader.lt_1c0a22b9445571ff7dc9f81e09c8d86f.min.js
121 ms
CoveoFullSearch.css
107 ms
search.lt_27c602bb703d5050d14b73299e90d330.min.css
121 ms
search.lt_b540e34729769208bc6f31e58aea040c.min.js
125 ms
clientlibs.lt_46bd1424ade08286c64f45ae06759fc3.min.css
202 ms
adaptiveImages.lt_255c26b17911c49aa9cebe541dfa21b7.min.js
126 ms
widgets.js
298 ms
clientlibs.lt_cdcbe495a06a0424b79ae52d29684a0a.min.css
206 ms
accessibility.lt_7f64d7918e126c44b6d7cafa10b85ef1.min.css
204 ms
flexslider2.lt_8f455d675b36440c275c11813414d975.min.css
205 ms
featureSlider.lt_576af484e729eee7678364c16d2346a1.min.css
204 ms
flexslider2.lt_d2c415bf29f09ec97f97bcd9c3e994fc.min.js
205 ms
featureSlider.lt_4ce9a9edf2973c3b167f9e47c500d19a.min.js
205 ms
containerTwoColumn.lt_9fd0a600fa39094b6454080eef4e9114.min.css
212 ms
containerThreeColumn.lt_4db8743ae222373b3f2b90833d5dc329.min.css
212 ms
footerClientLib.lt_478d088086840a1bc1d76de662a1ef10.min.css
254 ms
feedback.lt_0da98b229a26e86d440689f37bf4b53d.min.css
212 ms
gtm.js
273 ms
css
38 ms
dalhousie-logo-black.svg
15 ms
1643740356595.jpg
100 ms
1643734696085.jpg
101 ms
1643734736459.jpg
131 ms
003.jpg
140 ms
109.jpg
437 ms
sparx_logo.png
99 ms
MARS_Logo.cq5dam.thumbnail.140.100_3.png
248 ms
HCOR_Logo_new.cq5dam.thumbnail.140.100.png
247 ms
customForm-sprite.png
75 ms
1669219284282.jpg
230 ms
fa-solid-900.woff
40 ms
fa-regular-400.woff
41 ms
embed
334 ms
questions-slate.png
73 ms
tran-black-70.png
74 ms
js
78 ms
js
190 ms
js
284 ms
js
436 ms
analytics.js
402 ms
739 ms
765 ms
767 ms
771 ms
765 ms
763 ms
757 ms
fbevents.js
615 ms
fv8gvexyg9
746 ms
insight.min.js
734 ms
amzn.js
716 ms
js
762 ms
collect
348 ms
collect
340 ms
28 ms
insight.beta.min.js
22 ms
clarity.js
34 ms
38 ms
51 ms
49 ms
50 ms
50 ms
43 ms
insight_tag_errors.gif
197 ms
collect
106 ms
c.gif
8 ms
ie.dal.ca accessibility score
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-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
ie.dal.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ie.dal.ca 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
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ie.dal.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 Ie.dal.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.
ie.dal.ca
Open Graph description is not detected on the main page of Ie Dal. 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: