From bundle size to first paint — a practical checklist for mini-program performance.
From bundle size to first paint — a practical checklist for mini-program performance.
First-screen speed shapes retention. Drawing on several projects, here is a checklist you can apply directly.
One: control the main bundle. Move non-first-screen pages into sub-packages, serve images from CDN, and keep the main bundle under about 1.5MB.
Two: reduce launch-time requests. Merge first-screen data into a single endpoint rather than firing several requests sequentially in onLoad.
Three: cache wisely. Cache slow-changing data with an expiry policy, render cached content first, then update silently.
Four: use skeleton screens. Rendering a skeleton before data arrives noticeably reduces perceived waiting time.
Five: track real data. The platform's performance panel reflects real devices — use it as the source of truth rather than your dev-machine experience.