Update README.md

Author: ganyicz

README.md

@@ -13,8 +13,15 @@ Blaze supercharges your Blade components by compiling them into direct PHP funct
 
 Blaze is designed as a drop-in replacement for anonymous Blade components. It supports all essential features including props, slots, attributes, and `@aware`. The HTML output is identical to standard Blade rendering.
 
-> [!IMPORTANT]
-> When using `@aware`, both the parent and child components must use Blaze for values to propagate correctly.
+### Limitations
+
+Blaze focuses on anonymous components. The following are not supported:
+
+- Class-based components
+- The `$component` variable
+- `View::share()` variables
+- View composers / creators
+- Component lifecycle events
 
 ## Installation
 
@@ -46,9 +53,6 @@ This optimizes all [anonymous component paths](https://laravel.com/docs/12.x/bla
 php artisan view:clear
 ```
 
-> [!NOTE]
-> Blaze focuses on anonymous components. Class-based components, the `$component` variable, `View::share()` variables, view composers, and component lifecycle events are not supported.
-
 ## Configuration
 
 ### Directory-Based Optimization
@@ -91,6 +95,13 @@ Optimization strategies can be specified directly:
 
 Component-level directives override directory-level settings.
 
+### Using @aware
+
+Blaze fully supports the `@aware` directive for sharing data between parent and child components.
+
+> [!IMPORTANT]
+> When using `@aware`, both the parent and child components must use Blaze for values to propagate correctly.
+
 ## Optimization Strategies
 
 Blaze offers three optimization strategies, each suited to different use cases:
@@ -178,11 +189,25 @@ If `<x-icon name="check" />` appears 50 times on a page, it renders once and reu
 
 ### Compile-Time Folding
 
-Compile-time folding is Blaze's most aggressive optimization. It pre-renders components during compilation, embedding the HTML directly into your template. The component no longer exists at runtime.
+Compile-time folding is Blaze's most aggressive optimization. It pre-renders components during compilation, embedding the HTML directly into your template. The component ceases to exist at runtime - there is no function call, no variable resolution, no overhead whatsoever.
+
+#### Benchmark Results
+
+Because folded components are rendered at compile-time, the runtime cost is effectively zero. The rendering time remains constant regardless of how many components you use:
+
+| Components | Blade | Blaze (folded) |
+|------------|-------|----------------|
+| 25,000 | 500ms | 0.68ms |
+| 50,000 | 1,000ms | 0.68ms |
+| 100,000 | 2,000ms | 0.68ms |
+
+The time doesn't grow because there are no components to render - just static HTML.
 
 > [!CAUTION]
 > Folding requires careful consideration. Used incorrectly, it can cause subtle bugs that are difficult to diagnose. Review the [Folding](#folding) section before enabling.
 
+#### How It Works
+
 ```blade
 @blaze(fold: true)