Source
Snippet performance & flicker — found from sitemap — Tweakwise
Checked for Tweakwise on 17 Nov 2026
- Page
- https://docs.tweakwise.com/docs/how-to-optimize-diagnose-performance-when-using-tweakwise-personal-merchandising-in-magento
- Checked
- 17 Nov 2026, 12:17 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:62305062cb75dbce9ac1e0bc7ab63c3391e8936ae7c2f474739a579841bfca3b
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Pm dynamic sorting Report an error
“Enabling Personal Merchandising (PM) in Tweakwise introduces dynamic, real-time product sorting tailored to individual visitors.”
-
Pm varnish limitation Report an error
“Because each visitor sees a personalized sequence, category product lists cannot be fully cached in Varnish.”
-
Pm list block noncacheable Report an error
“The product list block (category.products.list) bypasses Varnish cache (PRODUCT_LIST_TTL = 0) to fetch personalized rankings. Individual product cards remain cached as ESI fragments.”
-
Pm warm cache latency Report an error
“Warm Cache (Best Case): Adds ~100 ms to 150 ms of extra PHP execution time per category page view.”
-
Pm cold cache latency Report an error
“Cold Cache: The initial request after clearing page cache incurs an extra +0.35s to +0.45s overhead.”
-
Pm storefront comparison Report an error
“Luma and Hyvä behave almost identically regarding PM overhead (~140 ms vs ~130 ms).”
-
Pm throughput impact Report an error
“Because requests hit PHP-FPM for the personalized list, server throughput drops under load (e.g., from ~850–975 req/s down to ~47–50 req/s per node at 10 concurrent users).”
-
Pm API time share Report an error
“Tweakwise Navigation API Call: ~53% – 57% (~60–72 ms).”
-
Pm magento time share Report an error
“Magento Core / Layout Rendering: ~43% – 47% (~53–54 ms).”
-
Pm instance scaling caveat Report an error
“Larger client instances with extensive product catalogs, complex merchandising rules, or heavy personalization setups will experience higher API processing times than a simple demo instance.”
-
Pm optimize minimize payload Report an error
“Minimize Payload: Ensure the category.products.list API request only asks for necessary attributes and bypasses unused facets/filters.”
-
Pm optimize baseline benchmark Report an error
“Establish an Instance Baseline: Benchmark the Tweakwise API response time directly from your production server using your actual catalog data before going live.”
-
Pm scale php workers Report an error
“Scale PHP Workers: Ensure your hosting environment has adequate PHP worker processes and CPU capacity to process concurrent un-cached requests during peak sales events.”
-
Pm network latency Report an error
“Optimize Network Latency: Ensure keep-alive connections are enabled and latency between your Magento server and Tweakwise endpoints is minimized.”
-
Pm diag core threshold Report an error
“Check if Magento core execution time (excluding the API call) exceeds ~50 ms.”
-
Pm diag TLS handshake Report an error
“Measure TLS/TCP handshake times (~40 ms on cold connections) and verify connection reuse.”
-
Pm diag esi modification Report an error
“Refactoring layout handles or creating lightweight custom ESI endpoints yields negligible gains (~10 ms) and increases risk.”
-
Pm diag tools Report an error
“Use tools like Blackfire.io or Magento’s built-in profiler.”
-
Pm partner research Report an error
“Based on performance research conducted by our partner Emico.”
Scores citing this record
- The CRO Consultant Snippet performance & flicker
- The Data Protection Officer Snippet performance & flicker
- The E-Commerce Manager Snippet performance & flicker
- The E-Commerce Manager Pricing transparency
- The Growth Lead Snippet performance & flicker
- The Product Engineer Snippet performance & flicker
- The Skeptic Snippet performance & flicker