1.4 sec in total
66 ms
1.1 sec
275 ms
Click here to check amazing Webex content for United States. Otherwise, check out these important facts you probably never knew about webex.com
With industry leading video conferencing, calling, and contact center solutions, Webex fuels hybrid work for businesses of all sizes.
Visit webex.comWe analyzed Webex.com page load time and found that the first response time was 66 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
webex.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value13.5 s
0/100
25%
Value34.1 s
0/100
10%
Value75,120 ms
0/100
30%
Value0.227
55/100
15%
Value101.3 s
0/100
10%
66 ms
30 ms
24 ms
28 ms
82 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 49% of them (34 requests) were addressed to the original Webex.com, 9% (6 requests) were made to Assets.adobedtm.com and 9% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (312 ms) relates to the external source Connect.facebook.net.
Page size can be reduced by 1.3 MB (39%)
3.4 MB
2.1 MB
In fact, the total size of Webex.com main page is 3.4 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. 50% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 85.7 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 44.6 kB, which is 45% 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 85.7 kB or 87% of the original size.
Potential reduce by 199.4 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. Webex images are well optimized though.
Potential reduce by 845.1 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 845.1 kB or 76% of the original size.
Potential reduce by 182.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. Webex.com needs all CSS files to be minified and compressed as it can save up to 182.4 kB or 85% of the original size.
Number of requests can be reduced by 36 (57%)
63
27
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.webex.com
66 ms
header.css
30 ms
main.css
24 ms
header.js
28 ms
satelliteLib-e45bc6f4a5d6196ca952933248e1cb5a95188646.js
82 ms
jquery.js
62 ms
utils.js
56 ms
granite.js
54 ms
jquery.js
55 ms
main.js
52 ms
footer.js
103 ms
mbox-contents-8455df169de4dafc7d0e678348f7e6061b85090a.js
5 ms
mbox.js
18 ms
satellite-54c871666363360018590300.js
28 ms
target.js
34 ms
standard
50 ms
wCUX9pxu.min.js
176 ms
downarrow.png
160 ms
cse.js
204 ms
satellite-55ce236f663934001400005c.html
62 ms
s-code-contents-8b42f1b2acc33cb5e9d80eccfb7f03d4570d0169.js
62 ms
satellite-55dc9d80653532084600020b.html
115 ms
elqCfg.min.js
102 ms
separator-header.gif
43 ms
Cisco_WebEx_wordmark_lockupx2.png
42 ms
spr-basic-76x152.png
43 ms
spr-premium-76x152.png
40 ms
spr-event-center-76x152.png
47 ms
spr-training-center-76x152.png
64 ms
spr-support-center-76x152.png
64 ms
img-hp-sect3-476x353.jpg
69 ms
mobile.jpg
48 ms
promo-img-desktop.jpg
95 ms
meet_instantly.jpg
67 ms
stopli.png
68 ms
quote-l-small.png
92 ms
quote-r-small.png
91 ms
stop-li.png
90 ms
n-social-media-icons.png
91 ms
cisco-logo-new.png
90 ms
play_pause_button.png
106 ms
ciscosansextralight-webfont.woff
107 ms
ciscosansregular-webfont.woff
106 ms
ciscosansthin-webfont.woff
117 ms
insight.min.js
68 ms
ip.json
87 ms
pixel
105 ms
ip.js
79 ms
jsapi
86 ms
activityi;src=4226791;type=webex447;cat=webex728;ord=1867380840703.845
152 ms
svrGP
157 ms
pixel
29 ms
default+en.css
6 ms
default+en.I.js
13 ms
minimalist.css
30 ms
async-ads.js
65 ms
small-logo.png
35 ms
search.png
22 ms
fbds.js
312 ms
conversion.js
94 ms
clear.gif
34 ms
s37929653937462
33 ms
50 ms
17 ms
22 ms
23 ms
25 ms
18 ms
l
31 ms
webex.com 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
[aria-hidden="true"] elements contain focusable descendents
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
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
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.
webex.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
webex.com 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
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webex.com 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 Webex.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.
webex.com
Open Graph description is not detected on the main page of Webex. 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: