1.3 sec in total
141 ms
941 ms
226 ms
Click here to check amazing Allegion content. Otherwise, check out these important facts you probably never knew about allegion.ca
We specialize in commercial security around the doorway and beyond: everything from commercial locks, door closer and exit devices, steel doors and frames to access control and workforce productivity ...
Visit allegion.caWe analyzed Allegion.ca page load time and found that the first response time was 141 ms and then it took 1.2 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.
allegion.ca performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value9.7 s
0/100
25%
Value8.0 s
22/100
10%
Value1,450 ms
15/100
30%
Value0.435
21/100
15%
Value18.4 s
3/100
10%
141 ms
76 ms
72 ms
55 ms
41 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 77% of them (55 requests) were addressed to the original Allegion.ca, 4% (3 requests) were made to Cdn.cookielaw.org and 3% (2 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (345 ms) belongs to the original domain Allegion.ca.
Page size can be reduced by 1.6 MB (38%)
4.2 MB
2.6 MB
In fact, the total size of Allegion.ca main page is 4.2 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. 70% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 96.9 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 33.3 kB, which is 31% 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 96.9 kB or 90% of the original size.
Potential reduce by 1.5 MB
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, Allegion needs image optimization as it can save up to 1.5 MB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 69.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 69.2 kB or 57% of the original size.
Number of requests can be reduced by 17 (34%)
50
33
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Allegion. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
allegion.ca
141 ms
76 ms
home.html
72 ms
satelliteLib-5deb0474226b0522042e65b4d04f313aa188bc3d.js
55 ms
main.min.css
41 ms
inbenta.min.css
33 ms
font-awesome.min.css
75 ms
css
70 ms
jquery.min.js
48 ms
api.js
81 ms
jquery.min.js
49 ms
utils.min.js
66 ms
contexthub.kernel.js
68 ms
main.min.js
39 ms
inbenta.min.js
28 ms
inbenta-common-us.min.js
29 ms
AppMeasurement.min.js
8 ms
OtAutoBlock.js
127 ms
otSDKStub.js
136 ms
js
64 ms
732a37a3-6edc-4c96-8525-0bfa6746f6d9.json
177 ms
-vFCHA2G-MvMYxRGDmck.infinity.json
99 ms
contexthub.pagedata.json
82 ms
contexthub.seg.js
82 ms
contexthub.commerce.cart.json
241 ms
contexthub.commerce.orderhistory.json
85 ms
contexthub.commerce.relatedproducts.json
85 ms
contexthub.commerce.smartlists.json
82 ms
allegion-logo.png
76 ms
allegion_logo_mob.png
77 ms
Advantage_120x120.png
75 ms
Falcon_120x120.png
77 ms
Glynn_Johnson_120x120.png
76 ms
Ives_120x120.png
78 ms
LCN_120x120.png
77 ms
Locknetics_120x120.png
79 ms
Schlage_120x120.png
79 ms
Von_Duprin_120x120.png
78 ms
Zero_120x120.png
77 ms
1649876083145.png
125 ms
1649876083145.png
184 ms
1649876083145.png
183 ms
1649876083145.png
191 ms
1649876083145.png
192 ms
1649876083145.png
192 ms
1649876083145.png
345 ms
1649876083145.png
297 ms
1592318929959.jpg
203 ms
1592318960671.jpg
205 ms
1620921969285.jpg
206 ms
1592319012569.jpg
204 ms
1592319035845.jpg
204 ms
1592319062768.jpg
206 ms
0.gif
207 ms
X_Sprite_Animation_Alpha.png
178 ms
arrow.png
180 ms
location
106 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
106 ms
Roboto-Regular.woff
112 ms
Roboto-Bold.woff
113 ms
fontawesome-webfont.woff
51 ms
glyphicons-halflings-regular.woff
116 ms
inbenta-core.css
72 ms
1592318929959.jpg
40 ms
1592319012569.jpg
79 ms
1592319035845.jpg
81 ms
1592318960671.jpg
80 ms
1620921969285.jpg
78 ms
1592319062768.jpg
79 ms
9392b880-53a7-0135-c1bd-06a9ed4ca31b
54 ms
s45330174153205
7 ms
allegion.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
allegion.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
allegion.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Allegion.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 Allegion.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.
allegion.ca
Open Graph description is not detected on the main page of Allegion. 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: