Frontend School

Optimizing Perceived Performance for Delhivery's Premium Customer Dashboard

Theory
medium

Optimizing Perceived Performance for Delhivery's Premium Customer Dashboard

Medium
Frontend
Web Performance
Metrics
User Experience
L4

Overview

Delhivery is launching a new "Premium Customer Dashboard" for its enterprise clients, offering real-time logistics data, shipment management, and custom reporting. Early pilot feedback suggests the dashboard can feel "slow" or "unresponsive," particularly with complex data or interactive elements. Ensuring a smooth and efficient user experience is critical for client retention and satisfaction.

What you need to do / Task

You are tasked with outlining a comprehensive strategy to address the perceived performance issues of the Premium Customer Dashboard. Your strategy should cover the identification, measurement, and improvement of key web performance aspects.

The question

As a senior frontend engineer, how would you approach identifying, measuring, and improving the perceived performance of Delhivery's "Premium Customer Dashboard"? Detail specific web performance metrics you would focus on, the tools and methodologies you would employ for measurement, and concrete, actionable steps you would recommend to enhance the user experience.

What a strong answer covers

  • Identification of relevant performance metrics, including Core Web Vitals and others specific to a data-heavy, interactive application.
  • Discussion of various measurement tools and techniques (e.g., RUM, Synthetic Monitoring, browser dev tools).
  • Strategies for setting performance budgets and targets.
  • Actionable technical recommendations for performance improvement (e.g., code-splitting, lazy loading, data optimization, rendering strategies).
  • Consideration of the user's perception of speed and responsiveness.

Examples

1

Example 1

Input:

Outline your strategy for improving the Premium Customer Dashboard's perceived performance.

Output:

  • Identify Key Metrics: Focus on LCP, FID/INP, CLS for core experience, plus TTI, FMP, and custom metrics for interactive elements.
  • Measurement Strategy: Implement RUM for real-user data (network, device variations), use Synthetic Monitoring for consistent baselines and regression detection, leverage browser DevTools for detailed analysis.
  • Improvement Actions: Optimize bundle size (code splitting, tree shaking), lazy load components/data, virtualize large lists, debouncing/throttling for input, optimize critical rendering path, use CDNs.
  • Monitoring & Iteration: Set performance budgets, continuously monitor, and iterate based on user feedback and metric trends.

Constraints

Constraints & assumptions

  • The dashboard is a single-page application (SPA) built using a modern JavaScript framework (e.g., React, Angular, Vue).
  • Users are enterprise clients, potentially accessing the dashboard from various network conditions and device types (desktop being primary, but tablets/laptops on varying Wi-Fi/LTE are common).
  • The backend APIs are generally performant, but large data payloads are common.
  • Expected depth: Your answer should demonstrate a deep understanding of web performance principles, practical application of metrics, and the ability to propose concrete, implementable solutions. Aim for a response that would typically take 15-20 minutes to articulate thoroughly in an interview.

Out of scope

  • Detailed backend infrastructure optimizations (focus on frontend and client-side perception).
  • Specific code implementations; focus on conceptual approaches and strategies.

What interviewers evaluate

  • Ability to identify and prioritize relevant web performance metrics for a complex application.
  • Understanding of various performance measurement tools and their appropriate use cases.
  • Practical strategies for diagnosing and resolving common frontend performance bottlenecks.
  • Capacity to think holistically about user experience beyond raw load times, considering perceived performance and responsiveness.

Loading editor...