2.9 sec in total
366 ms
2.4 sec
70 ms
Click here to check amazing Meetings Api Webex content for United States. Otherwise, check out these important facts you probably never knew about meetings-api.webex.com
Cisco Developer and DevNet enable software developers and network engineers to build more secure, better-performing software and IT infrastructure with APIs, SDKs, tools, and resources.
Visit meetings-api.webex.comWe analyzed Meetings-api.webex.com page load time and found that the first response time was 366 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
meetings-api.webex.com performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value14.3 s
0/100
25%
Value10.3 s
8/100
10%
Value1,560 ms
13/100
30%
Value0.785
5/100
15%
Value14.1 s
9/100
10%
366 ms
383 ms
69 ms
54 ms
87 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Meetings-api.webex.com, 56% (25 requests) were made to Static.production.devnetcloud.com and 9% (4 requests) were made to Rtp-static.marketo.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.production.devnetcloud.com.
Page size can be reduced by 13.4 kB (7%)
184.2 kB
170.9 kB
In fact, the total size of Meetings-api.webex.com main page is 184.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 141.3 kB which makes up the majority of the site volume.
Potential reduce by 5.6 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 5.6 kB or 73% of the original size.
Potential reduce by 7.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 28 B
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. Meetings-api.webex.com has all CSS files already compressed.
Number of requests can be reduced by 26 (87%)
30
4
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meetings Api 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 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
meetings-api.webex.com
366 ms
383 ms
main.css
69 ms
jquery.min.js
54 ms
pubhub.js
87 ms
project_list.js
79 ms
index.js
81 ms
sdk.js
78 ms
sdk.js
80 ms
sdk.js
129 ms
index.js
80 ms
app.js
121 ms
index.js
120 ms
index.js
368 ms
index.js
372 ms
gtm.js
50 ms
munchkin.js
22 ms
rtp.js
176 ms
app.css
26 ms
munchkin.js
4 ms
visitWebPage
66 ms
js
47 ms
analytics.js
24 ms
collect
30 ms
collect
28 ms
jquery.min.js
110 ms
jquery-ui-insightera-custom-1.9.6.css
101 ms
ga-integration-2.0.5.js
106 ms
fontawesome-all.min.css
22 ms
sdk.css
17 ms
jquery-custom-ui.min.js
15 ms
pubhub.css
22 ms
style.css
20 ms
90c048a9634b3d0c2821.woff
75 ms
CiscoSansRegular-webfont.woff
96 ms
8a1aa830a79407ae1ef8.woff
132 ms
CiscoSansBold-webfont.woff
121 ms
b8423ec0dacd4136d788.woff
71 ms
CiscoSansLight-webfont.woff
93 ms
e49291b62304ab877c95.woff
160 ms
CiscoSansExtraLight-webfont.woff
1162 ms
ee8395bd2febac7b9abe.woff
195 ms
CiscoSansThin-webfont.woff
172 ms
9c40b840611204374e98.woff
221 ms
CiscoSansHeavy-webfont.woff
208 ms
meetings-api.webex.com accessibility score
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
Heading elements are not in a sequentially-descending order
meetings-api.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
meetings-api.webex.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 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 Meetings-api.webex.com 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 Meetings-api.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.
meetings-api.webex.com
Open Graph data is detected on the main page of Meetings Api Webex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: