How We Enforce a Performance Budget on Three Static Sites
How BBMM Technologies turns a web performance budget into failing builds: a byte limit on hero media, an inlined stylesheet, and scripts that load on demand.
Topic
9 articles on Performance.
How BBMM Technologies turns a web performance budget into failing builds: a byte limit on hero media, an inlined stylesheet, and scripts that load on demand.
Why bbmmtech.com, flowoapp.com and textpack.app ship as static files, how each site is built, and what static export removes from a Next.js or Vite project.
How rendering choices affect battery life on Apple platforms, and the patterns that keep an interface smooth without draining the device.
How caching makes applications feel fast, the strategies for keeping cached data fresh, and why invalidation is the hard part.
Launch time is the first impression. How to find what work blocks the first frame and defer or remove it so an app feels instant from the tap.
JavaScript is the most expensive resource a page ships. Code splitting, tree shaking, and dependency discipline keep bundles small and pages responsive.
Why how fast software feels matters as much as how fast it is, and how to design for perceived performance alongside raw numbers.
Images dominate page weight. How to serve the right format and size, defer offscreen images, and reserve space so layout stays stable as they load.
How to keep a native macOS app fast by protecting the main thread, measuring with the right tools, and working to explicit performance budgets.