analyzing-test-results

Analyze k6 load test metrics to diagnose performance bottlenecks.

10|1|Updated Mar 1, 2026

Search Tags:#optimization #load testing #performance analysis #k6 #test results #bottleneck identification

Ready to run

npx skills add https://github.com/KimDoubleB/grafana-k6-skills --skill analyzing-test-results

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyzing-test-results
Source: https://github.com/KimDoubleB/grafana-k6-skills/tree/main/plugins/grafana-k6-skills/skills/analyzing-test-results
Command: npx skills add https://github.com/KimDoubleB/grafana-k6-skills --skill analyzing-test-results

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you understand the output of your k6 load tests, identify performance bottlenecks, and make informed decisions for optimization.

Core Features & Use Cases

Interpret k6 Output: Understand key metrics like response times, error rates, and throughput.
Identify Bottlenecks: Analyze the breakdown of HTTP request durations (e.g., waiting, connecting, receiving) to pinpoint performance issues.
Optimize Performance: Receive actionable recommendations for tuning thresholds, improving scripts, or scaling infrastructure.
Use Case: After running a load test, you see high http_req_duration. Use this Skill to analyze the http_req_waiting and http_req_receiving components to determine if the bottleneck is on the server-side or due to large response payloads.

Quick Start

Analyze the provided k6 test results to identify any performance bottlenecks and suggest optimizations.

Frequently Asked Questions about analyzing-test-results

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

FAQPage Schema

How do I interpret k6 load test results to identify performance bottlenecks?▼

Interpreting k6 load test results involves analyzing HTTP request duration breakdowns like waiting, connecting, and receiving times to pinpoint performance bottlenecks. This Skill evaluates metrics such as error rates and throughput to determine if issues are server-side or network-related.

What is the difference between http_req_waiting and http_req_receiving in k6 metrics?▼

In k6 metrics, http_req_waiting measures time spent waiting for the server response, while http_req_receiving measures time transferring the response payload. Analyzing these components helps identify whether performance bottlenecks are due to slow server processing or large response sizes.

How do I tune k6 thresholds based on load testing performance analysis?▼

Tuning k6 thresholds requires evaluating current load testing performance analysis data to set realistic pass/fail criteria. This Skill provides actionable recommendations for adjusting thresholds based on identified metrics like HTTP request durations and error rates to optimize test configurations.

Why does my k6 test show high http_req_duration and how can I optimize it?▼

High http_req_duration in k6 tests indicates slow overall request processing, which can be optimized by analyzing sub-metric breakdowns. This Skill helps diagnose whether the bottleneck stems from server-side waiting times or receiving large payloads, suggesting infrastructure adjustments or script optimizations.

Can I use k6 test results to determine if I need to scale my infrastructure?▼

Yes, analyzing k6 test results helps determine infrastructure scaling needs by evaluating throughput and error rates under load. This Skill translates performance bottlenecks and request timing breakdowns into actionable guidance for scaling infrastructure or improving script efficiency.

What do high error rates and low throughput in k6 test output indicate?▼

High error rates and low throughput in k6 test output indicate severe performance bottlenecks, often pointing to server overload or connection failures. This Skill analyzes these metrics alongside request duration components to diagnose root causes and recommend optimizations.