3.6 sec in total
61 ms
3.3 sec
246 ms
Visit ino.ca now to see the best up-to-date INO content for Canada and also check out these interesting facts you probably never knew about ino.ca
Creating and developing innovative and valuable optical-based solutions for businesses. Bring to life innovations that enable you to be more productive and competitive.
Visit ino.caWe analyzed Ino.ca page load time and found that the first response time was 61 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ino.ca performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value11.7 s
0/100
25%
Value11.0 s
6/100
10%
Value980 ms
28/100
30%
Value0.069
96/100
15%
Value16.7 s
5/100
10%
61 ms
909 ms
27 ms
1639 ms
176 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 57% of them (24 requests) were addressed to the original Ino.ca, 14% (6 requests) were made to Fonts.gstatic.com and 12% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Ino.ca.
Page size can be reduced by 466.8 kB (46%)
1.0 MB
547.5 kB
In fact, the total size of Ino.ca main page is 1.0 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. 40% of websites need less resources to load. Images take 400.3 kB which makes up the majority of the site volume.
Potential reduce by 26.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 11.4 kB, which is 34% 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 26.5 kB or 80% of the original size.
Potential reduce by 31.5 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. INO images are well optimized though.
Potential reduce by 129.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 129.3 kB or 64% of the original size.
Potential reduce by 279.5 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. Ino.ca needs all CSS files to be minified and compressed as it can save up to 279.5 kB or 74% of the original size.
Number of requests can be reduced by 15 (45%)
33
18
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ino.ca
61 ms
909 ms
css
27 ms
style.css
1639 ms
flexslider.css
176 ms
jquery-1.10.2.min.js
679 ms
home.js
386 ms
jsapi
22 ms
jquery.validate.min.js
401 ms
jquery.jpanelmenu.min.js
388 ms
jquery.flexslider-min.js
455 ms
scripts.js
540 ms
ga.js
19 ms
logo.png
286 ms
motif.png
353 ms
silicon-photonics-packaging-ino-350px.jpg
256 ms
yb-doped-LMA-fiber-INO.jpg
133 ms
ion-selective-fiber-water-treatment-home.JPG
224 ms
black_circle.png
296 ms
prix-du-quebec-ino.jpg
449 ms
youtube.png
367 ms
linkedin.png
327 ms
twitter.png
409 ms
accueil4.jpg
537 ms
motif_blue.png
397 ms
metal_footer.png
415 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
27 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
28 ms
wkfQbvfT_02e2IWO3yYueQ.woff
28 ms
BVtM30trf7q_jfqYeHfjtA.woff
28 ms
33 ms
inpage_linkid.js
5 ms
2HG_tEPiQ4Z6795cGfdivD8E0i7KZn-EPnyo3HZu7kw.woff
25 ms
HkF_qI1x_noxlxhrhMQYED8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
__utm.gif
13 ms
default+en.css
3 ms
default.css
39 ms
default+en.I.js
9 ms
default.css
33 ms
fleche-top.png
202 ms
2434.js
20 ms
__utm.gif
5 ms
ino.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ino.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
Page has valid source maps
ino.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ino.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ino.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.
ino.ca
Open Graph description is not detected on the main page of INO. 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: