2.1 sec in total
91 ms
1.8 sec
214 ms
Welcome to support.avaya.com homepage info - get ready to check Support Avaya best content for India right away, or after learning these important things about support.avaya.com
Avaya support
Visit support.avaya.comWe analyzed Support.avaya.com page load time and found that the first response time was 91 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
support.avaya.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value8.0 s
2/100
25%
Value4.3 s
76/100
10%
Value400 ms
68/100
30%
Value0.015
100/100
15%
Value8.3 s
39/100
10%
91 ms
168 ms
21 ms
26 ms
26 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 80% of them (63 requests) were addressed to the original Support.avaya.com, 6% (5 requests) were made to Tags.tiqcdn.com and 3% (2 requests) were made to D3701cc9l7v9a6.cloudfront.net. The less responsive or slowest element that took the longest time to load (931 ms) relates to the external source S3-ap-southeast-1.amazonaws.com.
Page size can be reduced by 551.5 kB (37%)
1.5 MB
945.4 kB
In fact, the total size of Support.avaya.com main page is 1.5 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. Javascripts take 690.0 kB which makes up the majority of the site volume.
Potential reduce by 36.2 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 6.9 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 36.2 kB or 79% of the original size.
Potential reduce by 10.9 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. Support Avaya images are well optimized though.
Potential reduce by 434.9 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 434.9 kB or 63% of the original size.
Potential reduce by 69.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. Support.avaya.com needs all CSS files to be minified and compressed as it can save up to 69.5 kB or 82% of the original size.
Number of requests can be reduced by 54 (73%)
74
20
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support 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 46 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
support.avaya.com
91 ms
support.avaya.com
168 ms
reset.css
21 ms
grid.css
26 ms
common.css
26 ms
oo_style.css
31 ms
main-compiled_new.css
35 ms
fonts.css
28 ms
chat-form.css
29 ms
nrl5hwv.js
209 ms
jquery-1.7.1.min.js
55 ms
jquery.scroll-stop.js
26 ms
jquery.hoverintent.js
28 ms
jquery.autocomplete.js
27 ms
jquery.validate.min.js
32 ms
jquery.validate.additional.min.js
30 ms
jquery.color.js
31 ms
jquery-ui-1.8.16.custom.min.js
50 ms
json-2.js
50 ms
underscore.js
33 ms
backbone.js
48 ms
mustache-0.5.0.min.js
48 ms
ich-0.10.min.js
51 ms
jcookie.js
52 ms
avaya.customform.js
50 ms
avaya.global.js
107 ms
avaya.login.js
104 ms
avaya.tooltips.js
77 ms
avaya.modals.js
79 ms
avaya.seemore.js
52 ms
avaya.productsearch.js
81 ms
avaya.customscroll.js
58 ms
avaya.globalsearch.js
62 ms
avaya.welcome.js
69 ms
avaya.ticket.detail.modal.js
80 ms
jquery.multiselect.dd.js
104 ms
avaya.chat.modal.js
86 ms
avaya.chat.view.js
136 ms
support-home.css
85 ms
ticker-style.css
90 ms
jquery.blockUI.js
122 ms
supportTracking.js
113 ms
modernizr-2.6.2-respond-1.1.0.min.js
104 ms
avaya.homepage.js
124 ms
jquery.ticker.js
109 ms
s_code.js
115 ms
oo_engine.min.js
116 ms
oo_conf.js
147 ms
print.css
13 ms
p.gif
207 ms
getDefaultSoldTo.action
169 ms
webengage-min-v-4.0.js
121 ms
utag.js
124 ms
icon-search.png
102 ms
logo_left.png
92 ms
logo_right.png
92 ms
ladyavaya.png
92 ms
BRBWithText.png
92 ms
home-sprite.png
353 ms
avaya-tango-transparent-sprite.png
154 ms
conversive-agent.jpg
214 ms
support-home-select-background.png
128 ms
modal-background.jpg
154 ms
loader-transparent.gif
156 ms
ticker-next.jpg
104 ms
regular.svg
243 ms
bold.svg
179 ms
gz.js
69 ms
v4.js
64 ms
l3.jpg
90 ms
67 ms
feedback-widget-close.png
54 ms
~537e09f.png
931 ms
feedback-tab-bg-dark.png
54 ms
s56480591741856
60 ms
utag.8.js
14 ms
utag.14.js
24 ms
utag.53.js
24 ms
utag.57.js
25 ms
support.avaya.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
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
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.
support.avaya.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
support.avaya.com SEO score
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 doesn't use legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.avaya.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Support.avaya.com 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.
support.avaya.com
Open Graph description is not detected on the main page of Support Avaya. 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: