Magento 2 + Hyvä speed, Core Web Vitals (LCP/INP/CLS), TTFB tuning, indexer + cache strategy.
11 articles
Ranking is not enough. SXO blends SEO, UX, and CRO so your Magento page satisfies the searcher and converts. Here is why optimized pages still fail, and how to fix them.
FrankenPHP worker mode boots your framework once and reuses it across requests for roughly 3–4× the throughput of nginx + PHP-FPM. Here is how it works, where it shines, and the honest take for Magento.
Everything that actually matters about Magento 2 indexing: the two modes, how Update by Schedule works under the hood, the CLI you need, and how to clear a stuck "index locked" reindex.
When Magento cron stops firing, your store silently breaks: indexes go stale, transactional emails queue forever, and scheduled prices never apply. This guide covers the exact crontab lines, cron groups, cron_schedule diagnostics, and every root cause fix for Magento 2.4.4-2.4.9.
Most Magento REST vs GraphQL articles compare syntax. After benchmarking three real queries against a Magento 2.4.9 store with 50,000 SKUs, the answer flips depending on the call pattern: REST wins single-resource by URL (95 ms vs 140 ms), GraphQL wins relational and grid loads by an order of magnitude (180 ms vs 665 ms), and the FPC versus @cache directive story decides whether either survives Black Friday. Here is the curl trace, the wrk concurrency test, and the cache invalidation pattern from client work on Magento 2.4.4-2.4.9.
You edit a LESS file, push it to production, run `bin/magento setup:static-content:deploy -f en_US`, and the old CSS still serves. The deploy reports success in under two seconds. The browser still shows the old rules. The issue is not Cloudflare, not OPcache, not the browser, it is Magento reusing the preprocessor output cached under `var/view_preprocessed`. The `-f` flag clears `pub/static` but does not always touch `view_preprocessed`. This is the exact wipe sequence we run on every Magento 2.4.4-2.4.9 Hyvä store to force a true LESS-to-CSS recompile, why the order of operations matters, and the one-liner that catches the nested `_module.less` reused-output trap.
Most Magento 2.4.9 stores hit a visible wall the moment a category crosses ~5,000 products. The price index swells, the EAV join fan-out balloons, and a category that rendered in 400 ms now takes 1.8 seconds before TTFB even starts. After tuning 22 catalogs between 8k and 180k SKUs in 2025–2026, only three remediations consistently bring category page TTFB back under 250 ms: legacy flat catalog (yes, deprecated, still works under 50k SKUs), the Hyvä Catalog add-on, and a custom slim query for SKU-only listings. Here is the EXPLAIN ANALYZE for each, the millisecond numbers, and the SKU ceiling for each option.
Four real diagnoses from production Magento + Hyvä stores in 2026. LCP element pinned in DevTools Performance (usually the hero image or an H1 stuck in font-swap), a 10 KiB inline critical CSS budget, a 1200w / 800w / 480w WebP <picture> matrix, INP traced to a 3-second Knockout boot on Luma checkouts, and CLS killed by reserving min-height on the cookie banner. Real Lighthouse JSON excerpts, a recipe checklist, and the mobile P=52 → P=88 numbers that came out the other side.
Most Magento performance guides stop at FPM_CHILDREN and "enable Varnish." The real wins live in six config keys nobody talks about: Redis eviction policy, Varnish ESI hold-times, OpenSearch query clause limits, and a handful of header rules. Here is the diff per key, the ROI measured on a real 80k-SKU prod trace, and the safe-rollback notes.
Most Magento TTFB advice stops at "enable Varnish". After dragging one Magento 2.4.9 store from 1.8 s down to 180 ms, three fixes mattered: PHP-FPM pm.max_children sized to actual per-process memory, a Redis cache_id_prefix collision that two stores quietly shared, and Varnish ESI scoped to cart and wishlist blocks. Here is the real var/log/php-fpm.log, redis-cli MONITOR output, and varnishlog trace that pinned each one: with a table that separates what hits TTFB from what only hits LCP and INP.
