diagnose-request

Analyzes HTTP performance metrics to identify bottlenecks in page-loading speed.

1|Updated Feb 19, 2026

Search Tags:#performance #debugging #api #diagnostics #http #network

Ready to run

npx skills add https://github.com/andreilupu/my-claude-skills --skill diagnose-request

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose-request
Source: https://github.com/andreilupu/my-claude-skills/tree/main/skills/diagnose-request
Command: npx skills add https://github.com/andreilupu/my-claude-skills --skill diagnose-request

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify the root cause of slow HTTP requests by breaking down the request lifecycle into distinct phases and pinpointing performance bottlenecks.

Core Features & Use Cases

Detailed Timing Breakdown: Measures DNS lookup, TCP connect, TLS handshake, Time to First Byte (TTFB), and total transfer time.
Bottleneck Identification: Analyzes each phase against defined thresholds to identify slow components.
Actionable Recommendations: Provides specific suggestions for fixing identified issues, such as DNS problems, TLS overhead, server processing delays, or large data transfers.
Use Case: When a web application API endpoint is responding slowly, use this Skill to diagnose whether the issue lies in network latency, server-side processing, or data transfer size.

Quick Start

Use the diagnose-request skill to analyze the performance of the URL https://example.com/api/health.

Frequently Asked Questions about diagnose-request

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

FAQPage Schema

How do I diagnose slow HTTP request performance in my web API?▼

Diagnosing slow HTTP request performance requires measuring each lifecycle phase: DNS lookup, TCP connect, TLS handshake, TTFB, and transfer time. Breaking down these timings pinpoints whether network resolution, server-side processing, or data transfer size is the primary bottleneck.

How can I check DNS, TCP, and TLS handshake timings for an API endpoint?▼

You can check DNS, TCP, and TLS handshake timings by executing a curl request against the API endpoint. This provides a detailed timing breakdown for each network resolution and connection phase to identify specific latency issues.

Do I need curl installed to analyze HTTP request bottlenecks?▼

Yes, curl is required to analyze HTTP request bottlenecks. The diagnostic process requires curl for request execution to capture precise timing metrics across DNS, TCP, TLS, and transfer phases for performance analysis.

What is the best way to identify if high TTFB is causing API latency?▼

The best way to identify if high TTFB is causing API latency is to measure Time to First Byte alongside other phases. If TTFB dominates the timeline, the bottleneck is server-side processing rather than network resolution or data transfer.

Why does my HTTP request take so long during the TLS handshake phase?▼

Your HTTP request takes long during the TLS handshake phase due to cryptographic overhead and certificate exchange delays. Analyzing this phase against performance thresholds determines if TLS configuration optimization is needed to reduce connection latency.