3.8 sec in total
82 ms
2.4 sec
1.3 sec
Click here to check amazing Avaya content. Otherwise, check out these important facts you probably never knew about avaya.ca
Build great experiences for your brand with Avaya's suite of cloud-based solutions designed to suit the specific needs of your team.
Visit avaya.caWe analyzed Avaya.ca page load time and found that the first response time was 82 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
avaya.ca performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value8.8 s
1/100
25%
Value6.5 s
39/100
10%
Value1,580 ms
12/100
30%
Value0.105
88/100
15%
Value7.3 s
49/100
10%
82 ms
64 ms
236 ms
42 ms
54 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Avaya.ca, 86% (43 requests) were made to Avaya.com and 6% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Avaya.com.
Page size can be reduced by 2.4 MB (49%)
4.9 MB
2.5 MB
In fact, the total size of Avaya.ca main page is 4.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. 55% of websites need less resources to load. CSS take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 74.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 13.3 kB, which is 15% 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 74.9 kB or 82% of the original size.
Potential reduce by 21.3 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. Avaya images are well optimized though.
Potential reduce by 4.7 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 2.3 MB
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. Avaya.ca needs all CSS files to be minified and compressed as it can save up to 2.3 MB or 92% of the original size.
Number of requests can be reduced by 8 (17%)
47
39
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Avaya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
avaya.ca
82 ms
www.avaya.com
64 ms
236 ms
OtAutoBlock.js
42 ms
otSDKStub.js
54 ms
v4.js
93 ms
avaya-2.0.css
194 ms
odc.js
40 ms
avaya-home-vendor.js
26 ms
avaya-home.js
20 ms
avaya-menu.js
21 ms
jquery.cookie.js
25 ms
11fcaab1-94a5-4127-a288-57d67b245b37.json
18 ms
location
29 ms
symbol-defs.svg
132 ms
avatar-icon-sprite.png
745 ms
Hero-Logo-v1.png
135 ms
Satellite
375 ms
hero_frame.jpg
282 ms
Satellite
425 ms
cx-capabilities-hp-blade_906x860.jpg
135 ms
axp-promo-906x860.jpg
136 ms
Satellite
164 ms
Solutions-1-FRAME.jpg
356 ms
Satellite
333 ms
Solutions-2-FRAME.jpg
605 ms
Satellite
385 ms
Solutions-3-FRAME.jpg
670 ms
Satellite
1585 ms
Satellite
639 ms
Satellite
618 ms
Satellite
747 ms
Satellite
924 ms
Satellite
1189 ms
Satellite
883 ms
Satellite
989 ms
Satellite
869 ms
Satellite
954 ms
Satellite
1095 ms
Satellite
955 ms
Satellite
1038 ms
Satellite
1068 ms
Satellite
1251 ms
Satellite
1277 ms
Satellite
1223 ms
Satellite
1260 ms
Satellite
1373 ms
avaya-logo-red.svg
1232 ms
ajax-loader.gif
1243 ms
avaya-fonts.css
11 ms
avaya.ca accessibility score
avaya.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
Page has valid source maps
avaya.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Avaya.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 Avaya.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.
avaya.ca
Open Graph data is detected on the main page of Avaya. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: