W30 - Performance & Manpower

• Some performance considerations for the checkout.The project refactored with Vue has a clear disadvantage in bundle size. From a product perspective, the checkout has specific characteristics: rigid presentation and high-frequency use. In Q3 we need to propose targeted strategies for the checkout use cases. Broadly, there are three areas: first, compressing bundle size — there is still room to reduce the current first-screen bundle. Second, caching — as a high-frequency page, an effective caching strategy should yield immediate metric improvements. For first-time opens of the checkout, consider adding prefetch. Third, some relatively aggressive, large-scale experiments. For a checkout that is small in customization and whose presentation can be exhaustively enumerated, I found a potentially fitting optimization approach in the community,Offline Prerender (OPR). This is a Prerender-based approach that moves the task of rendering static HTML files into an offline service that runs on a schedule, serving the corresponding static files directly when users visit.

• Some thoughts on staffing the B-side checkout.As the B-side checkout onboards more clients, payment features expand, and platform capabilities improve, I often switch between many small tasks — for example, helping troubleshoot daily production issues and developing minor feature requests. Given the current workload for B-side checkout, two full-time staff are somewhat surplus; but adding an intern would provide backup and strengthen organizational resilience while freeing me to focus on larger, higher-value work. Right now I have limited bandwidth for planning and data monitoring.