Application performance solutions like ARGOS Service provide a variety of measurement metrics: availability, response time, CPU usage and so on.
However, those metrics do not satisfy visibility and applicability of indicator values.
ARGOS now presents ARGOS SCORE to show key metrics at a glance so that you can detect directly affected performance issues among the various measurement indicators.
ARGOS SCORE can quantify and manage the performance quality of the online services as a single value.
Performance management of online service is one of the critical factors for business management, and ARGOS SCORE enables easy comparison with competitors to lead to a competitive edge.
ARGOS SCORE measures the key metrics: Availability, Response Time, Variation Rate, Page Size, and Number of Requests, using the weighted average because each one has different degrees of impact on performance quality..
The availability is a measurement metrics to see if the user can access the Web or mobile app service.
The highest level of online service requires triple 9 (99.9%), and it means 8.76 or fewer hours of service failure per year.
The response time is the speed of the Web or mobile app service that the user experience: time from the start of loading to the completion.
Response time should not exceed three seconds because the maximum endurance time of the end-user in the online services is 3 seconds before leaving to a competitive service.
Response Time Variation Rate
The response time calculates an average value of measurements over a certain period. But this average value does not reflect the actual response time when the variation of the sizes is significant.
In the figure, the average response time of service A and B shows both 2 seconds in 24 hours. However, in case of service B, the response time of service has to be 3 seconds because the response time of most high traffic hours, 10-18 o’clock, hits 3 seconds.
It is essential to keep the average response time low for a fast user experience rate, but it is also important to maintain the response times constant without large variations.
ARGOS uses the standard deviation to calculate the response time variation rate.
The page size is the byte count when a device is loading a web or mobile app page.
A larger page requires longer download time, and it can directly effect on end-user response time.
An inefficient large page size creates more costs not only for a service provider, and downloading a large page size in a mobile environment causes not just a delay in response time to the user but also an additional communication cost burden.
Most online services use CDN service, so a large page size incurs additional CDN cost for the service provider. It is cost effective to manage page size within 1MB for the PC environment and 500KB for the mobile environment.
Number of Requests
Excessive requests to the server result in response time delays, so you should limit the number of requests using CSS Sprites within 100 in the PC environment and 50 in the mobile environment.
Usage of ARGOS SCORE
The following figure is an example of ARGOS SCORE; it measured online shopping websites for Amazon and eBay.
The performance quality of eBay is 93.17, which exceeds Amazon’s 86.17.
ARGOS SCORE shows a radar chart to see the weak point at a glance and compare with a competitor.
In the example, Amazon’s page size and requests metrics are significantly lower than eBay, and you can read that Amazon’s page size is 5.94 MB and requests are 238, which is more than twice from eBay. It is clear that Amazon needs to optimize the page size and number of requests according to ARGOS SCORE.
- ARGOS SCORE’s key metrics gives a direct impact on performance.
- ARGOS SCORE shows the performance quality at a glance.
- ARGOS SCORE’s competitive management ensures continuity of online business.
CEO, ARGOS LABS