PERFORMANCE INSIGHT

HeadSpin Proposes Speed Optimizations as Worthiest Promotions for Auchan

Icon-Methodology-orange

Overview and Methodology For Our Analysis

Industry:

Shopping

Device/Network/Location:

iPhone XS / Orange / Paris

Products Used:

HeadSpin Connected Intelligence Platform

Recommendations:                                                         

  • Review multiple 3rd party SDKs that cause slowdown in launch time
  • Ensure that immediate content is loaded first before future content.
  • Optimize connection reuse
  • HeadSpin analyzed the latest version of the Auchan iOS app on a real iPhone XS in Paris, on the Orange network.
  • NO SDK, code change or instrumentation was needed to run the remote performance sessions.
  • HeadSpin’s AI engine sifted through network traffic, client-side metrics, and videos of the test execution to find areas of poor user experience and performance bottlenecks.
  • Recommendations were provided for every issue that was surfaced.
Icon-UserReviews-orange_1

User Reviews

HeadSpin looked at Auchan reviews in the App Store and found some users struggling with functional issues and technical errors.

Auchan ratings is currently 4.0/5 on the App Store.

Icon-Insight-orange

Insights and Recommendations

HeadSpin’s proprietary AI technology analyzes and prioritizes the core issues impacting critical user journeys. Using computer vision techniques to quantify blank screens, time to interact, loading time, loading or buffering animations, and content quality, our AI models can automatically diagnose server-side issues whether they arise from infrastructure deployment issues, poor performance, or API errors. For a custom analysis of your app, request a Performance Insight report from HeadSpin. 

HeadSpin Performance Session (link)

EXECUTIVE SUMMARY OF TOP PERFORMANCE AREAS

Analysed KPIs

Launch Time   2 sec  
   Search for an item and add to basket  6 sec

The sample performance analysis focusing on a typical critical user journey for Auchan. Following are the top performance areas that can be optimized for Auchan.

Slow Server The server response time for one or more api calls took more than 500ms which is considered to be slow. In particular calls made to had longer response times and this is where most of the performance improvements should take place.

Connection Reuse On a number of occasions the app didn’t reuse already opened TCP connections which adds additional overheads.

Duplicate Message The app received identical copies of some resources , although this had minor effects on our tests but it is something to consider in case there are other instances of the issue throughout the application.

HTTP Errors Some HTTP requests returned errors one of which was due to a call to HelpShift which should be further investigated throughout the application.

The app can benefit from further detailed analysis into the different performance affecting issues which Headspin can assist with. One example is how does the app perform at different times of the day in particular during peak times? How does the app perform on different devices with different specs, or in different cities?

We have analyzed the overall performance during the below key journeys in order to identify any bottlenecks or performance issues.

A) First Launch

   Time to first interaction      2 sec   

The time it takes for your users to start interacting with the app is of great importance and should be minimized as much as possible. We have used the below screen as our control screen to measure the the Time to First Interaction (TTI).

We have encountered the below issues that contribute to the increased TTI.

Slow TLS

   Slow TLS Impact Time     428 ms  
Your application waited longer than 300 ms to complete TLS handshakes with this host.
TLS handshakes add latency to requests due to additional round trips between the device and server. Consider moving your servers closer to users or using a CDN to cut down on round trip time.
Icon-Insight-red

HEADSPIN RECOMMENDATION: Consider enabling keep-alive to reuse established connections. Examine the costs of additional overhead incurred by any domain sharding optimizations. Consider caching strategies to reduce or eliminate handshake round trips.

B) Search and add item

   Search for item     6 sec

We have analysed how long your users have to wait until they receive a response for an item search.

We have excluded the time for any user input steps and only included loading times resulting from api calls and network performance.

We have encountered the below issues that contributed to the increased “Search for item” time.

Connection Reuse

   Connection Reuse Impact Time   565 ms

TCP connections come with their own overheads, everytime a connection is opened those overheads add to the time of the task being executed.

The app created multiple connections in close succession to the same hosts.

Icon-Insight-red

HEADSPIN RECOMMENDATION: Check the keep-alive settings on the host server. If keep-alive connections aren’t enabled, or if the keep-alive timeout is set too low, client connections will be terminated prematurely, resulting in unnecessary TCP/TLS handshakes.

Reusing already established connections can reduce the overall Search Time by 565ms

Slow Server

   Slow Server Impact Time       1.44 sec  

The application waited longer than 500 ms to receive the first byte in HTTP responses from these hosts.

Icon-Insight-red

HEADSPIN RECOMMENDATION: The slower than optimal response time could be due to a number of reasons, long server side operations, serving resources from the incorrect edge of a CDN.

We recommend that you investigate the above host and try to reduce the overall time to be within the optimal 500ms response time by doing so can shave off approx of the overall search time by 1.44sec.

Connection Reuse

   Connection Reuse Impact Time     440 ms  

TCP connections come with their own overheads, everytime a connection is opened those overheads add to the time of the task being executed.

The app created multiple connections in close succession to the same hosts.

Icon-Insight-red

HEADSPIN RECOMMENDATION: Check the keep-alive settings on the host server. If keep-alive connections aren’t enabled, or if the keep-alive timeout is set too low, client connections will be terminated prematurely, resulting in unnecessary TCP/TLS handshakes.

Reusing already established connections can reduce the overall search time by 440ms.

Duplicate Messages

   Duplicate Messages     2.3 sec  

 

The app received identical copies of the below resources.
Download CountSize Each (bytes)Total Download Time (ms) Impact Time (ms) Impact
/Total (%)
 StatusContent Type URL
2103457338366.8200 application/json; charset=utf-8Link
2677827913448200application/jsonLink
21026128216056.7200application/jsonLink
374591265071.3200application/jsonLink
3711756836263.7200application/jsonLink
418132725778.6301n/aLink
579758643874.7200application/json;charset=UTF-8Link
Icon-Insight-red
HEADSPIN RECOMMENDATION: It’s rare for an app to really need to download the same resource multiple times. Consider caching your HTTP requests so that duplicates never reach the server.

HTTP Errors

   HTTP Errors Impact Time  990 ms  

 

The below requests returned errors as listed below
 Impact Time (ms) Status Code Status MessageContent Type URL
9400Bad Request application/json  https://api.auchan.fr/carts/v0 
38400Bad Requestapplication/jsonhttps://api.auchan.fr/carts/v0
45400Bad Requestapplication/jsonhttps://api.auchan.fr/carts/v0
97400Bad Requestapplication/jsonhttps://api.auchan.fr/carts/v0
229400Bad Requestapplication/jsonhttps://api.auchan.fr/carts/v0
281400Bad Requestapplication/jsonhttps://api.auchan.fr/carts/v0
291400Bad Requestapplication/jsonLink
Icon-Insight-red

HEADSPIN RECOMMENDATION: We recommend that you investigate the above requests in detail to better understand the cause of the errors by doing so Auchan can shave 291ms off search time and 990ms of the overall user session.

Icon-HowTo-orange

How to Work With HeadSpin

HeadSpin Powers Flawless Mobile App Performance

HeadSpin’s state-of-the-art Digital Experience Intelligence Platform™ will empower your engineering teams to:

  • Execute automation tests on real carrier-enabled devices worldwide
  • Discover performance bottlenecks
  • Collect and visualize your performance data
  • Seamlessly integrate with your CI/CD workflow
  • Monitor every critical user flow of your mobile experience
  • Pinpoint issues that cause performance regressions and impact user experience earlier in your development cycle
Overarching Areas of Opportunities

  • Launch new features confidently by monitoring and analyzing root causes of performance issues throughout the development life cycle
  • Drive new user installs and user engagement with optimized performance
  • Forge user trust and safety, accelerating consumer services for critical user paths across your apps and website
  • Benchmark KPIs for mobile performance to understand how your user experience for your mobile app and website compares to your peers in the same industry
  • Support localized testing across thousands of devices and 70+ countries around the world, on real devices under real-world conditions
Expert Holistic Consultation and Strategy 

HeadSpin has the product and solutions expertise to help you perfect the digital experience for your customers! Our team hails from digital pioneers, such as Google and Facebook, and has already delivered enhanced mobile-centric experiences for a diverse set of Fortune 1000 clients. HeadSpin’s strategic insights can help you:

  • Drive new user acquisition, user engagement, and feature adoption
  • Deploy app security measures on iOS and Android
  • Build consistent performance standards and experiences across all your mobile apps and websites 

... insight from HeadSpin helps us prioritize issues so we could deliver a better user experience.

Maria Zhang, CTO, Tinder