performance-monitoring

Measure TTR, TTI, and custom operations with native and OpenTelemetry support.

3|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/guicheffer/devorch-cli --skill performance-monitoring-guicheffer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-monitoring
Source: https://github.com/guicheffer/devorch-cli/tree/main/templates/skills/observability/performance-monitoring
Command: npx skills add https://github.com/guicheffer/devorch-cli --skill performance-monitoring-guicheffer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you identify and fix performance bottlenecks in your application by providing tools to measure rendering speed, user interactivity, and custom operation times.

Core Features & Use Cases

  • Time to Render (TTR): Measure how long it takes for your UI to visually render.
  • Time to Interactivity (TTI): Measure when your app becomes responsive to user input.
  • Custom Performance Tracking: Monitor specific asynchronous operations or custom metrics.
  • Dual Native + OTEL Tracking: Integrates with both native performance tools and OpenTelemetry for comprehensive observability.
  • Use Case: Debug a slow-loading screen by using TTR to see if the UI is rendering slowly, or TTI to understand if JavaScript execution is blocking user interaction.

Quick Start

Use the performance-monitoring skill to measure the time to render for the current screen.

Frequently Asked Questions about performance-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I measure Time to Interactivity and Time to Render for my application?

You can measure Time to Interactivity (TTI) and Time to Render (TTR) by using performance monitoring hooks to track UI rendering speed and JavaScript execution blocking. This identifies bottlenecks and helps optimize user experience by ensuring application responsiveness.

What is the best way to track custom operation times alongside native performance metrics?

The best way to track custom operation times is using dual native and OpenTelemetry (OTEL) support, which integrates native performance tools with OTEL for comprehensive observability. This monitors specific asynchronous operations and custom metrics for detailed logging.

Why does my app feel slow to load even after the UI appears on screen?

Your app feels slow because JavaScript execution may be blocking user interaction after the UI renders. Measuring the gap between Time to Render (TTR) and Time to Interactivity (TTI) reveals if operations are delaying responsiveness, helping debug the loading screen.

Can I use OpenTelemetry to debug rendering speed and user interactivity issues?

Yes, you can use OpenTelemetry (OTEL) to debug rendering speed and user interactivity issues through dual native and OTEL tracking. It provides comprehensive observability and detailed metrics logging to identify performance bottlenecks and optimize application responsiveness.

Do I need OpenTelemetry set up to measure application performance metrics?

No, you do not need OpenTelemetry set up to measure application performance metrics because the system provides dual native and OTEL support. You can use native performance tools to measure TTR, TTI, and custom operations independently without an OTEL integration.

When should I use TTR versus TTI metrics to optimize user experience?

Use TTR metrics when the UI is visually rendering slowly, and use TTI metrics to understand if JavaScript execution is blocking user interaction. Tracking both metrics ensures application responsiveness by isolating visual rendering delays from interactivity delays.