Blaze Deep-Dive
Blade components are slow. Really slow. At scale, they quietly become the biggest bottleneck in your Laravel application. We discovered this while trying to make Flux as fast as possible, and the result is Blaze: a package that fundamentally rethinks how Blade components are compiled and rendered. With multiple levels of optimization, Blaze can shave hundreds of milliseconds off a page load, making Blade rendering up to 25x faster in some cases.
In this series, we'll install it, benchmark it, build a toy version from scratch so you truly understand how it works, and then master every directive and edge case so you can squeeze maximum performance out of your own apps.
Series episodes
Getting Started (3)
Why Blaze Exists
1m 48sDiscover why Blade components caused slowness and how Blaze fixes performance for Flux, Livewire, and every Laravel app.
Installing Blaze
5m 21sInstall Blaze fast in Laravel, clear cache, and cut page loads from ~700ms to ~35ms—plus tips for optimizing custom Blade components.
Three Levels Of Optimization
4m 27sLearn Blaze’s 3 optimization levels—compiler, memoization, and code folding—to cut Blade overhead and speed pages from 750ms to 50ms.
How Slow Is Blade, Really? (2)
Benchmarking Blade
5m 41sHow fast is Blade? Benchmark 25,000 renders across components and inline PHP, and discover the surprising results for real-world performance.
How The Blade Compiler Works
5m 2sSee how Laravel Blade compiles .blade.php into cached PHP, inspect storage/framework/views, and learn where overhead comes from.
Building a Toy Version (8)
Intercepting Blade Compilation
5m 52sBuild your own Blaze: intercept Blade compilation, regex-match component tags, and output custom markup to learn how it works under the hood.
Refactor Into A Compiler Class
6m 52sRefactor your code into a dedicated Compiler class using named capture groups, boosting clarity and preparing for major performance optimizations.
The Optimized Compiler
4m 38sCompile Blade components for a big speed win—avoid costly loading overhead with Blaze's default optimization for dramatically faster apps.
The Blaze Directive
4m 2sLearn how to add a Blade @blaze directive so only opted-in components get optimized, while everything else renders normally.
How Fast Is Our Toy
3m 49sBenchmark Blaze’s speed, spot costly components, and go beyond Blade savings with memoization and code folding for bigger gains.
Adding Memoization
11m 46sLearn component memoization: render once, cache the output, and reuse it across the page for faster, near-free repeat renders.
Code Folding
8m 24sLearn Blaze code folding to pre-render components at compile time, bake HTML into output, and cut runtime cost to nearly zero.
From Toy To Real
7m 53sGo from toy to real: open Blaze’s source after building your own clone, and finally understand its architecture—no more black box.
Mastering Blaze (7)
Limitations And Edge Cases
5m 44sExplore Blaze’s limitations and edge cases: no class components, view()->share workarounds, and @aware boundaries—avoid surprises.
The Blade Profiler
7m 30sTurn on BLAZE_DEBUG=true to see a flame chart of Blade components with render times, counts, and hot spots—find what’s slow fast.
When To Memoize
6m 57sLearn when to use memoization to speed up slow components, why it beats folding sometimes, and where it fails so you can choose better fixes.
When To Fold
3m 55sLearn when to fold pure UI components to cut expensive renders. See a real app example where tens of thousands of renders drop fast.
Folding With Dynamic Props
15m 42sLearn Blaze’s clever approach to foldable components with dynamic props and unlock performance gains for components you thought were off-limits.
Punching Holes With Unblaze
7m 55sLearn how @unblaze keeps tiny dynamic regions live while folding the rest—ideal for validation errors, URL checks, and more.
Ai Powered Optimization
10m 3sUse Blaze’s Laravel Boost skill to analyze and auto-optimize your Laravel app, then review the changes and fine-tune what AI misses.
