site-performance-watch

gtmagents's avatarfrom gtmagents

Monitoring and alerting framework for ecommerce site speed, errors, and uptime.

⭐31stars🔀7forks📁View on GitHub🕐Updated Dec 23, 2025
[Monitoring]

When & Why to Use This Skill

The Site Performance Watch skill provides a comprehensive monitoring and alerting framework specifically designed for e-commerce platforms. It enables teams to track critical performance KPIs such as Core Web Vitals (LCP, FCP, CLS), checkout API latency, and uptime, ensuring proactive detection of technical issues that could impact user experience and conversion rates.

Use Cases

  • Campaign & Launch Monitoring: Establish proactive monitoring during high-traffic marketing events or product launches to ensure site stability and performance.
  • Conversion Drop Investigation: Correlate technical latency or API availability issues with sudden drops in sales to identify and resolve performance-related bottlenecks.
  • Cross-Functional Incident Management: Streamline communication between engineering, merchandising, and CX teams using standardized escalation matrices and status update templates during performance incidents.
  • Global Performance Segmentation: Analyze site speed and error rates across different geographies, devices, and browsers to optimize the shopping experience for a diverse global audience.
namesite-performance-watch
descriptionMonitoring and alerting framework for ecommerce site speed, errors, and

Site Performance Watch Skill

When to Use

  • Setting up proactive monitoring during campaigns or launches.
  • Investigating conversion drops tied to latency or availability issues.
  • Communicating performance incidents to merchandising and engineering teams.

Framework

  1. KPI Stack – FCP, LCP, CLS, TTFB, checkout API latency, error rates, uptime.
  2. Segmentation – device, geography, browser, promotion, traffic source.
  3. Alerting Rules – thresholds, aggregation windows, escalation paths, war-room triggers.
  4. Diagnostics – logging, tracing, screenshot/session replay hooks.
  5. Comms Kit – stakeholder updates, status pages, rollback plans.

Templates

  • Performance scorecard with spark lines + thresholds.
  • Incident log template with root cause, mitigation, and follow-up tasks.
  • Escalation matrix covering engineering, DevOps, merchandising, and CX leads.

Tips

  • Pair synthetic monitoring with RUM data to catch both systemic and localized issues.
  • Freeze experiment/merch changes when performance breaches critical thresholds.
  • Use alongside diagnose-conversion-drop to correlate experience and performance data.