Frontend Optimizer
Frontend Optimizer speeds up first paint on public Capell pages.
What Frontend Optimizer helps you do
This private package is outside the Released and Beta channels, so no public install path is available.
Workflow screenshots
6 capturesFrontend Optimizer speeds up first paint on public Capell pages.
It extracts above-the-fold critical CSS from real rendered HTML and defers non-critical CSS and JavaScript.
Teams improve performance without rewriting every theme layout by hand.
Use it when public page speed needs a package-owned, cache-aware optimization path.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Frontend Optimizer adds when enabled.
- Frontend Optimizer
- Performance
- Assets
- Critical Css
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/frontend-optimizer -
02
Register the extension
php artisan capell:extension:enable frontend-optimizer -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Frontend Optimizer
Switch the evaluation lens to see how different roles should assess this package before installing it.
A dynamic CMS that serves flat files when it's hot — what to verify
Load a cached page repeatedly under traffic and inspect origin execution. The response should come from a flat file without a Laravel render while retaining correct public content.
Read more Show less
Acceptance evidence: Once a page is cached the origin short-circuits Laravel and Blade entirely and returns a stored file, giving near-static response times and real headroom under load with nothing for site owners to run. It still refuses to freeze any page carrying editor or gated content.
Boundary of fit: It won't rescue a genuinely heavy, custom-built frontend that's slow by design. An unusual, resource-hungry front-end is a job for a bespoke performance build rather than this automatic layer.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
0 releasesNo package release history is published yet. Check the source and documentation before installing.
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy hosts paid marketplace checkout and issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the licence, receipt, support history, and future install access. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
