API Performance Dashboards
At APImetrics, our job is to test APIs so companies know how well they’re doing – in real time. Every website in the world uses APIs. Some are far better than others. When your API isn’t doing its job correctly, users get a less than great experience. When they are working, users come away thinking your site or app is great.
This is why it’s important to know how well your APIs are performing. You can have the greatest site in the world – but if it has a ton of lag time or goes down, people will go somewhere else.
In other words, making sure your APIs work correctly is mission critical. We’ve all been on a site and tried to make a comment. We’ve seen sites where that happens seamlessly. And we’ve all been on sites where posting a comment is a real drag. It’s the APIs that make the difference.
Let’s look at the results of three marketplaces we recently looked at – Social Media sites, Corporate IT sites and CMA9 sites. You’ll get to see where the differences are in these API examples.
API Example: Social Networking Sites
Here you can see which site has the slowest API. That’s right – Tumblr. Ever have trouble posting something on Tumblr? Now you know why.
The fastest API was Foursquare. But by far the best quality API was on Twitter – which is probably one of the reasons people like it.
And the worst quality API was…. Facebook. Which shouldn’t really be a surprise when you consider just how often your friends complain about not being able to post, postings gone awry, or simply not being able to get to love a post.
API Example: Corporate IT Sites
Here you can see Docusign has the slowest API. Meanwhile, Slack has the fastest. Meanwhile, the overall worst API comes from Cisco Spark. And the best comes from Salesforce.
Let’s compare the difference between Cisco Spark and Salesforce. Cisco had an API Quality Score of 656. Meanwhile Salesforce came in with and overall score of 948. Imagine if Cisco just spent a little bit more investment in their APIs and simply tracked them to see whether or not they worked.
API Example: CMA9 Sites
Here the overall slowest API was from Santander. The fastest was from HSBC – which is great for their banking customers. AIB had the best quality API overall. While Halifax had the worst.
Now, if you were choosing who to bank with, where would you go? Do you want to have to wait a long time for your information to come up? Do you want the transaction to randomly crash? Or do you want to simply log in and get the data you need?
API speed and quality are what make the difference.
None of this is meant to disparage any of the companies we monitor. It is, useful, however, to look at this information and see what it tells us about how well they deliver to customers.
If some companies just made a little more effort and investment in their APIs, the results of these API examples would look very different.
ered here, then just let us know – we’re here to help. Happy reading!