Frontend Optimizer
Prepare the CSS a page needs for its first view.
- Version
- 1.0.58
- Released
- 20 October 2026
- Licence
- Commercial
Price £29.00
Check access and installationCheck your application before checkout
Use it in your project
Generate critical CSS from rendered pages and configure how remaining assets load. Regenerate the prepared output when the public design changes.
Picture it on your site
For a design change, use representative rendered pages to regenerate the prepared CSS and review the first paint as well as later sections. Measure the result before claiming an improvement. Prepared assets can reduce delivery work, but they still need updating when the design changes and do not replace sensible images or page composition.
3 captures
Maintain and monitor your site
- Generate critical CSS for published pages.
- Choose page, layout or site optimisation settings.
Is this right for your project?
Make a signal actionable
An operational screen is most useful when a warning has an owner and a next step. Decide which checks matter to your site, who reviews them and how they distinguish an expected state from a failure. The package supplies its supported observations or controls; the application and hosting environment still determine the queues, schedules, credentials and infrastructure those checks depend on.
Exercise the recovery path
On a safe local or staging environment, follow one representative task from detection to resolution and confirm the public result afterwards. Check what happens when a dependency is unavailable and how the team knows the issue has cleared. Visible status is useful evidence, but it should sit alongside your deployment, monitoring and recovery procedures rather than replace them.
You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy
Your renewal price stays locked while you renew continuously, including during the grace period. After a full lapse, renewal uses the current list price.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Paid checkout adds access to the purchasing account after payment. Add a free package to your account, then review compatibility and site impact before installing it.
Explore the available extensions on the demo site.
Before you install
Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.
-
01
Require the package
composer require capell-app/frontend-optimizer -
02
Install the extension
php artisan capell:extension-install capell-app/frontend-optimizer
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.0.58 Oct 20, 2026
- Recent activity
- 23 approved releases in the last 12 months
Review evidence for this release
Automatic critical-CSS extraction from real rendered pages via a headless-browser pipeline, with deferred loading of non-critical CSS/JS on public Capell pages. Review found no critical or high-severity defects: the Playwright target resolver validates against registered site domains and blocks private/reserved IP ranges by default (SSRF-guarded), and rendered public output only contains allow-listed URLs and an escaped hash, no model IDs or internal state. One low-severity gap: failure redaction only scrubs the exception message, not the stack trace, so a trace containing a filesystem path could reach application logs unredacted.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.0.58
- Approval date
- Oct 19, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- Critical CSS generation depends on a working Node/Playwright runtime as an external process dependency.
- compatibility-integration is recorded as not-run, hand-corrected from attest.php's tool output of "passed": no per-package compatibility-integration runner exists in this repository, so nothing was actually executed for this check (see CAP-0489, in progress at write time, to give attest.php the same honest behaviour automatically).
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
10 releasesv1.0.58Oct 20, 2026v1.0.57Oct 17, 2026v1.0.56Oct 9, 2026v1.0.55Oct 9, 2026v1.0.54Oct 8, 2026v1.0.53Oct 8, 2026v1.0.52Oct 7, 2026v1.0.51Oct 4, 2026v1.0.50Oct 1, 2026v1.0.49Sep 29, 2026
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 is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy 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 Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. 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.
How do I request a refund?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
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.