Improve Responsiveness of Search and Browse Pages with UI Re-architecture

Read how GSPANN helped a US-based retailer with more than 700 departmental stores, 150 specialty stores, and annual sales of $25B in improving the responsiveness of their search and browse pages with UI re-architecture. We upgraded the in-house development ecosystem, used for managing UI of search and browse pages, to the latest Java version, separated UI from the back-end, and performed cosmetic enhancements.

Key highlights:

  • With the new responsive UI architecture, the page load time for search and browse pages reduced from approx. 13 seconds to less than 3 seconds. As a result, the ‘Add To Bag’ conversions also increased from 100K to 200K per month. 
  • Earlier, the client used to maintain a separate code base for search and browse pages of web and mobile sites on different servers. By developing a responsive design for search and browse pages, the cost of server maintenance was reduced by 40%.
  • After separating the development and release cycle of both back-end and UI, changes can be made to different components of UI in the production environment without impacting each other.

This case study demonstrates why separating the development and release cycle of UI and back-end services can help in minimizing the dependency of different UI components on each other. It is essential in today’s competitive environment, wherein the ability to quickly add and remove features is the key to success.

UI Re-architecture Case Study