Tools & Wizards About Us
api.webex.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

api.webex.com

Cisco Developer and DevNet: APIs, SDKs, Sandbox, and Community for software developers and network engineer

Page Load Speed

748 ms in total

First Response

109 ms

Resources Loaded

576 ms

Page Rendered

63 ms

api.webex.com screenshot

About Website

Visit api.webex.com now to see the best up-to-date Api Webex content for United States and also check out these interesting facts you probably never knew about 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 api.webex.com

Key Findings

We analyzed Api.webex.com page load time and found that the first response time was 109 ms and then it took 639 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

api.webex.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.306

38/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

api.webex.com

109 ms

82 ms

style.css

51 ms

fontawesome-all.min.css

61 ms

sdk.css

73 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Api.webex.com, 53% (9 requests) were made to Static.production.devnetcloud.com and 12% (2 requests) were made to Munchkin.marketo.net. The less responsive or slowest element that took the longest time to load (196 ms) relates to the external source Static.production.devnetcloud.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.8 kB (40%)

Content Size

75.4 kB

After Optimization

45.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Api.webex.com main page is 75.4 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. 50% of websites need less resources to load. HTML takes 37.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 29.0 kB

  • Original 37.9 kB
  • After minification 37.8 kB
  • After compression 9.0 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 29.0 kB or 76% of the original size.

JavaScript Optimization

-14%

Potential reduce by 860 B

  • Original 6.0 kB
  • After minification 5.8 kB
  • After compression 5.2 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 860 B or 14% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 31.4 kB
  • After minification 31.4 kB
  • After compression 31.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. Api.webex.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (86%)

Requests Now

14

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

api.webex.com

api.webex.com

109 ms

82 ms

style.css

style.css

51 ms

fontawesome-all.min.css

fontawesome-all.min.css

61 ms

sdk.css

sdk.css

73 ms

pubhubdoc.css

pubhubdoc.css

118 ms

jquery.min.js

jquery.min.js

53 ms

sdk.js

sdk.js

69 ms

index.js

index.js

75 ms

sdk.js

sdk.js

69 ms

index.js

index.js

79 ms

pubhubdoc.js

pubhubdoc.js

196 ms

gtm.js

gtm.js

63 ms

munchkin.js

munchkin.js

80 ms

rtp.js

rtp.js

178 ms

munchkin.js

munchkin.js

34 ms

visitWebPage

visitWebPage

29 ms

Accessibility Review

api.webex.com accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

api.webex.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

api.webex.com SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.

Social Sharing Optimization

api.webex.com

Open Graph data is detected on the main page of Api Webex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: