> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Score by Template, Website Performance (PageSpeed + CrUX) > Score by Template for Website Performance (PageSpeed + CrUX) stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act... **Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Website Performance](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Performance Score broken down by page template** (homepage, product detail, collection, cart, checkout, etc.). **The most actionable surface for engineering prioritisation**: instead of "site is slow", the per-template view says "homepage scores 42, PDP scores 58, collection scores 48, fix homepage first because it has the worst score AND the highest traffic share". Template-level fixes have multiplier effects: one PDP template fix lifts all 78 product detail pages simultaneously. | | | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | Lighthouse Performance Score for each template's representative URL. Templates derived from the merchant's site map (homepage, PDP, collection, cart, checkout, search, account, etc.). Each row: template name, representative URL, mobile score, desktop score, traffic share. | | **Sample type** | **Lab data** from per-template Lighthouse audits, default mobile profile. | | **Why per-template matters** | The site-weighted aggregate score (e.g. 51 mobile) hides template-level variation. **One template typically dominates the average** because of its traffic share + score. Per-template view surfaces which template to fix first; template-level fixes ship to many URLs at once. | | **Template detection** | Vortex IQ uses URL-pattern heuristics + GA4 traffic data + BC theme template metadata to classify URLs into templates. Common ecommerce templates: homepage, PDP, collection / category, cart, checkout (multi-step), search results, account / login, blog, content / informational. | | **Reading the template view** | (1) **Sort by score × traffic share**, that's the prioritisation order. (2) **Identify shared-template patterns**: many low-scoring PDPs suggest a PDP-template-level issue rather than per-page issues. (3) **Confirm with [`psi_lcp_by_template`](/nerve-centre/kpi-cards/website-performance/lcp-by-template) and [`psi_cwv_pass_by_template`](/nerve-centre/kpi-cards/website-performance/cwv-pass-by-template)** for sub-metric breakdown per template. | | **Currency** | n/a, score values per template. | | **Time window** | `T/7D` | | **Alert trigger** | `worst-template score < 50` (red band on dominant template). | | **Sentiment key** | `psi_perf_score` | | **Roles** | owner, marketing, operations | ## Calculation Calculated automatically from your Website Performance (PageSpeed + CrUX) data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A UK-based BigCommerce fashion store, per-template lab scores Wednesday 15 May 26. | Template | Mobile score | Desktop score | Traffic share | Score gap to 80 | Priority signal | | --------------------- | -----------: | ------------: | ------------: | --------------------: | -------------------- | | Homepage | 42 | 76 | 22% | -38 × 0.22 = **-8.4** | **Highest priority** | | Product detail page | 58 | 82 | 25% | -22 × 0.25 = **-5.5** | High priority | | Collection / category | 48 | 79 | 28% | -32 × 0.28 = **-9.0** | **Highest priority** | | Cart | 62 | 88 | 8% | -18 × 0.08 = -1.4 | Low priority | | Checkout step 1 | 71 | 92 | 4% | -9 × 0.04 = -0.4 | Healthy, no work | | Checkout step 2 | 73 | 92 | 4% | -7 × 0.04 = -0.3 | Healthy, no work | | Search results | 54 | 80 | 8% | -26 × 0.08 = -2.1 | Medium priority | | Account / login | 68 | 90 | 1% | -12 × 0.01 = -0.1 | Negligible | What the template view is telling us: 1. **Collection page (-9.0) and homepage (-8.4) are the highest-leverage targets.** Collection edges out homepage because of higher traffic share (28% vs 22%) despite a slightly less-bad score (48 vs 42). 2. **PDP (-5.5)** is the third priority, meaningful traffic share (25%) with a moderate gap. Critical because PDP is the conversion page; performance work here translates directly to revenue. 3. **Cart, checkout, search, account** all have small priority signals because either traffic share is low (account, checkout) or score is acceptable (cart, search). **Don't optimise these first**; protect them from regression while focusing on the priority-3. 4. **Template-level fixes have multiplier effects**: one PDP template fix lifts \~78 individual PDPs; one collection template fix lifts \~12 collection pages. **Per-template work is more efficient than per-URL work** when the underlying issue is shared. 5. **Recommended sequence**: * **Week 1-2**: Collection template (filter widget refactor + responsive grid images) * **Week 3-4**: Homepage hero (image format conversion + responsive variants) * **Week 5-6**: PDP template (hero image + cart-drawer refactor) * Result: site-weighted mobile score from 51 → 70+ 6. **Cross-reference with [`psi_mobile_score_compare`](/nerve-centre/kpi-cards/website-performance/overall-score-mobile-vs-desktop)** for the same view with explicit mobile-vs-desktop gap; this card is mobile-focused and the device gap is implicit in the score values. The diagnostic flow: 1. **Sort by score gap × traffic share.** That's the priority order. 2. **For each priority template**, decompose by sub-metric ([`psi_lcp_by_template`](/nerve-centre/kpi-cards/website-performance/lcp-by-template), [`psi_cwv_pass_by_template`](/nerve-centre/kpi-cards/website-performance/cwv-pass-by-template), [`psi_opportunity_by_template`](/nerve-centre/kpi-cards/website-performance/opportunities-by-template)). 3. **Apply template-level fix patterns**: image responsive variants on hero templates, widget refactors on interactive templates. 4. **Re-audit** after each ship to confirm the template's score moved. Rapid-response playbook: | Time horizon | Action | | ------------ | ------------------------------------------------------------------------------------------------------------------------------- | | First 1 hour | Identify priority-3 templates by score × traffic. | | First week | Apply highest-leverage template fix. | | Day 28 | Field metrics reflect template-level changes via [`crux_lcp_p75`](/nerve-centre/kpi-cards/website-performance/page-load-speed). | ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | --------------------------------------------------------------------------------------------------------- | ---------------------------------------- | | [`psi_lcp_by_template`](/nerve-centre/kpi-cards/website-performance/lcp-by-template) | Per-template LCP. | | [`psi_cwv_pass_by_template`](/nerve-centre/kpi-cards/website-performance/cwv-pass-by-template) | Per-template CWV pass rate. | | [`psi_opportunity_by_template`](/nerve-centre/kpi-cards/website-performance/opportunities-by-template) | Per-template optimisation opportunities. | | [`psi_slowest_template`](/nerve-centre/kpi-cards/website-performance/slowest-template) | Worst-performing template singled out. | | [`psi_template_trend`](/nerve-centre/kpi-cards/website-performance/template-trend) | Per-template score over time. | | [`psi_perf_score_summary`](/nerve-centre/kpi-cards/website-performance/performance-score-summary) | Site-weighted aggregate score. | | [`psi_mobile_score_compare`](/nerve-centre/kpi-cards/website-performance/overall-score-mobile-vs-desktop) | Per-template mobile vs desktop. | | [`psi_slowest_lcp_urls`](/nerve-centre/kpi-cards/website-performance/slowest-lcp-urls) | Per-URL LCP ranking. | ## Reconciling against the vendor's own dashboard **Where to look:** * **PageSpeed Insights**, paste each template's representative URL individually; assemble per-template view manually. * **Lighthouse CI**, runs per-URL audits in build pipeline. **Why the Vortex IQ template view may differ from manual PSI checks:** | Reason | Direction | What to do | | ---------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------- | | **Template classification.** Vortex IQ uses URL-pattern + GA4 + theme metadata; manual checks may classify URLs differently. | Variable | Confirm template-to-URL mapping. | | **Run-to-run variance.** ±5-10 points per template per run. | Either direction | Use 7-day rolling. | **Cross-connector reconciliation:** primarily internal (with all per-template cards plus the per-URL ranking cards). **Quick rule for support tickets:** if a merchant says *"my homepage scores higher in PSI than your card shows"*, the difference is usually run-to-run variance plus URL choice. The Vortex IQ score is the 7-day rolling average; PSI is one snapshot. ## Known limitations / merchant FAQs **Should I optimise the worst-scoring template or the highest-traffic template?** The product. Worst-score × traffic share gives the priority order. A 30-point gap on a 5% traffic template (priority signal -1.5) is less leverage than a 22-point gap on a 25% traffic template (priority signal -5.5). **My checkout scores 73 mobile. Should I optimise it?** Probably not. 73 is in the orange-band but acceptable; the 4% traffic share means optimisation impact is small. Protect from regression but don't actively work on it. **Why does collection page have a worse score than checkout?** Different complexity. Collection pages have heavy filter widgets, 12+ product images, JS-driven sort/filter logic. Checkout pages are deliberately lean (fewer images, fewer scripts, focused on conversion). **Different optimisation curves apply** to different templates. **Will fixing the homepage hero image help PDP scores?** Sometimes, indirectly. If the homepage hero image and PDP hero use the same image-CDN config, fixing one may fix the other. **More commonly**: each template has its own optimisation work, with some shared infrastructure improvements. **Can Vortex IQ tell me which template fix has the biggest impact?** The "score gap × traffic share" column is exactly that. Sort descending; the top entries are the highest-leverage optimisations. *** ### Tracked live in Vortex IQ Nerve Centre *Score by Template* is one of hundreds of KPI pulses Vortex IQ tracks across Website Performance (PageSpeed + CrUX) and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.