C2 worked with the Hyster-Yale team to identify the root cause of the performance degradation and implement a structured set of changes designed to address it at the architecture level.

‍

The AutoMapper service was changed from a Transient to a Singleton lifetime, meaning it is now initialized once at startup and reused across requests rather than rebuilt each time. A mapper warm-up process was added to the application startup sequence to absorb first-request cost before live traffic hits the system. To ensure correctness after moving to singleton behavior, related type converters were hardened for thread-safe execution, maintaining accurate personalization context on a per-request basis.

‍

The results were measurable across every environment tested. Response times improved significantly, with the strongest observed gain reaching over 50% faster performance against the established 1.75-second page load threshold. Other environments showed gains in the range of 19% to 43% on the same metric. HTTP success rates improved as well, rising by roughly 9% to 20% depending on the environment.

‍

Beyond the immediate numbers, the work established a more stable and efficient baseline for the platform going forward. Better response performance lowers bounce risk and supports a stronger user experience. More consistent behavior under load reduces operational noise and creates a healthier foundation for future enhancements, without the compounding cost that comes from building on an unstable base.

‍