1.1 sec in total
43 ms
903 ms
152 ms
Visit am2.ca now to see the best up-to-date AM2 content and also check out these interesting facts you probably never knew about am2.ca
Visit am2.caWe analyzed Am2.ca page load time and found that the first response time was 43 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
am2.ca performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value19.7 s
0/100
25%
Value17.5 s
0/100
10%
Value4,130 ms
1/100
30%
Value0.093
91/100
15%
Value14.8 s
8/100
10%
43 ms
91 ms
75 ms
8 ms
25 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 17% of them (6 requests) were addressed to the original Am2.ca, 23% (8 requests) were made to Apis.google.com and 9% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (355 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 33.1 kB (14%)
239.1 kB
206.1 kB
In fact, the total size of Am2.ca main page is 239.1 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. 40% of websites need less resources to load. Images take 146.1 kB which makes up the majority of the site volume.
Potential reduce by 18.8 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 18.8 kB or 77% of the original size.
Potential reduce by 797 B
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. AM2 images are well optimized though.
Potential reduce by 9.2 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 9.2 kB or 15% of the original size.
Potential reduce by 4.4 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. Am2.ca needs all CSS files to be minified and compressed as it can save up to 4.4 kB or 67% of the original size.
Number of requests can be reduced by 18 (58%)
31
13
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AM2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
am2.ca
43 ms
www.am2.ca
91 ms
reset.css
75 ms
webfont.js
8 ms
css
25 ms
jquery.min.js
11 ms
flyoutmenu.css
17 ms
flyoutmenu.js
64 ms
widgets.js
89 ms
plusone.js
37 ms
quant.js
6 ms
background.jpg
53 ms
cb=gapi.loaded_0
50 ms
cb=gapi.loaded_1
49 ms
fastbutton
114 ms
tracking.js
94 ms
pixel;r=1492317455;a=p-b8x17GqsQ_656;fpan=1;fpa=P0-1110235717-1458463792300;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458463792300;tzo=-180;ref=;url=http%3A%2F%2Fwww.am2.ca%2F;ogl=
28 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
162 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
18 ms
l5lwlGTN3pEY5Bf-rQEuILmKcuvUA98TddnVPjOJl_w.ttf
68 ms
like.php
116 ms
postmessageRelay
63 ms
LoggingAgent
37 ms
sw.js
30 ms
cb=gapi.loaded_0
19 ms
cb=gapi.loaded_1
12 ms
cq_blank.gif
4 ms
3193398744-postmessagerelay.js
26 ms
rpc:shindig_random.js
29 ms
TY3MhkXpWJ-.js
314 ms
LVx-xkvaJ0b.png
355 ms
cb=gapi.loaded_0
4 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
53 ms
jot
85 ms
TY3MhkXpWJ-.js
127 ms
am2.ca accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
am2.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
Issues were logged in the Issues panel in Chrome Devtools
am2.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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Am2.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 Am2.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.
am2.ca
Open Graph description is not detected on the main page of AM2. 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: