Full Page Cache Booster

主な機能

Advanced full-page cache layer integrated via Magento\PageCache plugins and observers — zero core modifications, upgrade-safe

Cron-driven warm-up crawler that primes cache from sitemap.xml and top-traffic URLs after every cache:flush or deploy

Varnish integration and tuning: custom VCL, grace mode, ESI hole-punching for cart/customer sections, health probes

Per-page and per-customer-group cache rules so retail, wholesale and B2B price tiers cache independently

Cache analytics dashboard with hit-rate, miss reasons, and per-cache-tag invalidation reporting in the admin

Admin ACL-gated configuration under Stores > Configuration, with separate view and manage permissions

Smart cache-tag invalidation tuned to product, category and CMS save events to avoid full-store purges

Compatible with Magento 2.4.x on Adobe Commerce (Cloud & on-prem) and Magento Open Source

REST and GraphQL request paths kept cache-safe so PWA / headless frontends are not served stale private data

Configurable TTLs per content type (category, product, CMS, search) via di.xml-driven service config

Built-in CLI command for on-demand warm-up and hit-rate reporting (bin/magento ecosire:fpc:warm)

Optional Redis/Varnish backend selection with connection validation and fallback handling

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

Magento 2's built-in Full Page Cache (FPC) gets you part of the way, but on a real catalog it leaks: low hit rates after every deploy, cold pages for logged-in customer groups, and Varnish defaults that were never tuned for your VCL, ESI blocks or hole-punched mini-cart. Full Page Cache Booster is an ECOSIRE-engineered Magento 2 module (Ecosire_FullPageCacheBooster under app/code) that hardens and extends caching across Adobe Commerce and Magento Open Source.

The module adds an advanced full-page cache layer that plugs into Magento's \Magento\PageCache flow via plugins and observers — no core hacks. A cron-driven warm-up crawler primes the cache from your sitemap and top-traffic URLs immediately after cache:flush or a deploy, so visitors hit warm pages instead of cold ones. We integrate and tune Varnish (VCL, grace mode, ESI for the cart/customer sections) so private data stays uncached while everything else flies. Per-page and per-customer-group cache rules let you cache wholesale, retail and B2B price tiers independently without cross-contamination.

This is build-to-order, not a one-click Marketplace download. After purchase, ECOSIRE engineers build the module against your Magento version (2.4.x), your theme and your hosting (Cloud, Adobe Commerce on-prem, or self-managed), install it on staging, validate hit-rate and TTFB, then deploy to production. You get an admin panel (with proper ACL), cache analytics and a hit-rate dashboard, REST/GraphQL-safe behavior, and source code you own. We measure before/after with real Core Web Vitals — no invented numbers, just your own LCP and TTFB on your store.

得られるもの

Custom-built Ecosire_FullPageCacheBooster module source under app/code, version-pinned to your Magento 2.4.x release

Tuned Varnish VCL file and configuration matched to your hosting and theme (or Redis FPC config if Varnish is unavailable)

Installation and deployment on your staging environment, then production, by ECOSIRE engineers

Admin configuration guide plus CLI usage notes (warm-up, hit-rate reporting, invalidation)

Before/after performance report using your real TTFB and Core Web Vitals (LCP) measurements

30 days of post-deployment support, bug fixes and tuning included after go-live

これは誰のためのものですか

Performance-Focused Store Owner

A merchant whose product and category pages render slowly and whose Core Web Vitals are hurting rankings and conversions — needs measurable TTFB and LCP improvements without re-platforming.

Magento Solution Architect

An agency or in-house architect who wants an upgrade-safe FPC layer built with plugins, di.xml and proper ACL — not a core hack — that survives 2.4.x upgrades and composer updates.

B2B / Wholesale Operations Lead

Runs multiple customer groups and price tiers and needs per-group cache rules so logged-in wholesale pricing is fast yet never leaks into the retail cache.

Full Page Cache Booster の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
Built, installed and supported for your exact Magento 2.4.x environment	付属	部分的なサポート	含まれていない	含まれていない
Tuned Varnish VCL with ESI hole-punching for cart/customer sections	付属	部分的なサポート	部分的なサポート	部分的なサポート
Per-customer-group cache rules for B2B/wholesale price tiers	付属	部分的なサポート	部分的なサポート	含まれていない
Cron warm-up crawler that primes cache after deploy/flush	付属	部分的なサポート	部分的なサポート	含まれていない
Cache hit-rate and invalidation analytics in the admin	付属	部分的なサポート	部分的なサポート	含まれていない
Upgrade-safe (plugins/di.xml, no core hacks) with source ownership	付属	部分的なサポート	部分的なサポート	付属
Before/after Core Web Vitals validation on your real store	付属	含まれていない	含まれていない	含まれていない

Full Page Cache Booster に関するよくある質問

How long does delivery take, since this is build-to-order?

Typical lead time is 5 to 10 business days from kickoff. After purchase, an ECOSIRE engineer reviews your Magento version, theme, hosting and current cache setup, builds the module against your environment, installs and validates it on staging, then schedules production deployment with you. Complex multi-store or Adobe Commerce Cloud setups may add a few days; we confirm the exact timeline at kickoff.

What ongoing support and updates do I get after go-live?

Every build includes 30 days of post-deployment support covering bug fixes, cache-rule tuning and any compatibility issues. Because you own the source, you can maintain it in-house afterward. We also offer optional retainer plans for Magento 2.4.x upgrade compatibility, new customer-group rules and continued Varnish/Core Web Vitals tuning.

Will this conflict with Magento's built-in Full Page Cache or break upgrades?

No. The module extends Magento\PageCache through plugins, observers and di.xml rather than overriding core files, so it remains upgrade-safe across composer updates. We disable or reconfigure the stock FPC only where our layer supersedes it, and validate the full cache flow on staging before production.

Does it work with Adobe Commerce Cloud and headless / PWA storefronts?

Yes. It supports Magento Open Source and Adobe Commerce (Cloud and on-prem) on 2.4.x. For Cloud we tune the managed Fastly/Varnish layer rather than installing our own; for headless or PWA Studio frontends we keep REST and GraphQL request paths cache-safe so private customer data is never served from cache via ESI hole-punching.

Can it cache pages differently for logged-in wholesale versus retail customers?

Yes — that is a core feature. Per-customer-group cache rules let each price tier (retail, wholesale, B2B) cache independently using the customer-group context, with ESI hole-punching for truly private blocks like the mini-cart. This keeps logged-in pages fast without leaking group-specific pricing into the shared cache.