6 sec in total
1.6 sec
2.4 sec
2 sec
Visit vivint.ca now to see the best up-to-date Vivint content and also check out these interesting facts you probably never knew about vivint.ca
TELUS SmartHome Security keeps your home safe 24/7. ADT Canada is now TELUS, combining proven expertise with an award-winning network and systems.
Visit vivint.caWe analyzed Vivint.ca page load time and found that the first response time was 1.6 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
vivint.ca performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value4.5 s
37/100
25%
Value19.0 s
0/100
10%
Value23,450 ms
0/100
30%
Value0.037
100/100
15%
Value63.5 s
0/100
10%
1617 ms
52 ms
47 ms
129 ms
164 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Vivint.ca, 38% (28 requests) were made to Images.ctfassets.net and 4% (3 requests) were made to Telus.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Telus.com.
Page size can be reduced by 926.2 kB (59%)
1.6 MB
645.2 kB
In fact, the total size of Vivint.ca main page is 1.6 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. Only a small number of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.
Potential reduce by 896.1 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 896.1 kB or 89% of the original size.
Potential reduce by 30.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. Vivint images are well optimized though.
Potential reduce by 0 B
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.
Number of requests can be reduced by 37 (55%)
67
30
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vivint. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and as a result speed up the page load time.
smarthome-security
1617 ms
ruxitagentjs_ICANVfghqrux_10303241106123517.js
52 ms
0e333fb6d2621c46.css
47 ms
polyfills-42372ed130431b0a.js
129 ms
7205-43abacd5685cde08.js
164 ms
2158-a9b5c29e58858a77.js
160 ms
9808.2bbf802380ac7d9e.js
164 ms
1504.db0f88cc197ec2c4.js
163 ms
3815.37b46d4e2535233a.js
164 ms
9343.ab61cc6cea9b9df1.js
164 ms
2575.c394a192f6f4f80e.js
166 ms
3102.d965545e11bcafa1.js
189 ms
7360.2611ba31453c3f66.js
191 ms
2510.55da9a66024c20f1.js
191 ms
6977-3d3ce9cfe8bf7b8d.js
191 ms
7561.b323b35171307e15.js
184 ms
734-9a025446b6971dcb.js
195 ms
3615.bc7f12b37e319fc6.js
204 ms
9082.aa829c0bbe779e3e.js
209 ms
5689.b9881ee02889d3fb.js
215 ms
4463.af4e43818f3293d1.js
205 ms
1769.bf82ea67185b138f.js
216 ms
3099.de6b63057d0ea596.js
203 ms
5707.b63a7dd0414bec50.js
220 ms
6046.63dde2e0abc3860f.js
218 ms
2936.8ab2a1791b576257.js
224 ms
8928.ceef4b485d83d630.js
239 ms
9366.8daf1f72c24c1201.js
228 ms
3016.3f5a61c4fbc38b4a.js
227 ms
webpack-1ff22d9c9f12ac91.js
235 ms
framework-40461e51349ca8e7.js
305 ms
main-c89bdaa10995b6d7.js
311 ms
_app-d8b93ba98e20cb30.js
317 ms
8299-8d9c71a06d2e9ffd.js
309 ms
2303-da85151c1116d6a7.js
311 ms
1935-d516a8168033b3c0.js
312 ms
%5B...slug%5D-64e85b2348dd31f5.js
313 ms
_buildManifest.js
312 ms
_ssgManifest.js
274 ms
TELUS_Logo.svg
96 ms
SH_overview.png
63 ms
Hero-Protect-what-matters-most.png
73 ms
kid-dog-playing_2x.png
70 ms
XL-Design-your-perfect-plan.png
71 ms
XL-Smarter-Savings.png
78 ms
XS-M-smarter-savings.png
68 ms
Group_3393_copy_2.png
69 ms
BadgeApple_7.12.36_PM.png
69 ms
4.6_stars.png
70 ms
google-play-badge_1_copy.png
72 ms
4_stars.png
73 ms
XL-SHS-app.png
73 ms
Group_1.png
77 ms
EN__2_.png
73 ms
Mask_group__2_.png
74 ms
SHS_overview_Control_Video_card.png
75 ms
XL-Perfect-plan-Quiz.png
76 ms
XS-SHS-Overview-Quiz.png
77 ms
XL-Perfect-plan-Custom.png
82 ms
XS-SHS-Overview-custom.png
83 ms
XS-SHS-Overview-bundle.png
133 ms
XL-Perfect-plan-Bundle.png
130 ms
Q12024_SonnetxTelus_RiverFlowCard_EN_resized.png
82 ms
Q12024_SonnetxTelus_MobileXS_RiverFlowCard_EN.png
82 ms
XL-Lion_cub_testimonials.png
86 ms
XS-SHS-Overview-lion.png
85 ms
TELUS_LMTFF_EN_Hor_2021_Digital_RGB__2_.svg
82 ms
HNforTELUSSARegular_normal_normal-v3_1_0.woff
17 ms
core-icons.woff
23 ms
HNforTELUSSAMedium_normal_normal-v3_1_0.woff
22 ms
HNforTELUSSABold_normal_normal-v3_1_0.woff
50 ms
HNforTELUSSADisplay_normal_normal-v3_1_0.woff
50 ms
main.js
60 ms
vivint.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-*] attributes do not match their roles
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
vivint.ca 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
vivint.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
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 Vivint.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 Vivint.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.
vivint.ca
Open Graph data is detected on the main page of Vivint. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: