How Magento 2 Customer Data Sections Can Quietly Hurt Page Load Performance

Magento 2 uses a customer data sections mechanism to deliver personalized content — such as mini-cart, wishlist counters, and customer names — on otherwise fully cached pages. Because full-page cache serves identical HTML to all visitors, personalized data must be fetched client-side via AJAX calls to the customer/section/load/ endpoint after each page load. A typical Magento store registers 15 to 25 sections, each triggering backend database queries that can collectively take 300ms to 1.2 seconds per request. Section data is cached in the browser's localStorage, which can balloon to 1–2MB per visitor and is vulnerable to aggressive eviction on mobile browsers like iOS Safari. These combined factors — repeated AJAX calls on every cached page and heavy localStorage usage — represent significant, often overlooked performance bottlenecks for high-traffic Magento storefronts.