test-performance

Measures page load times, API response times, and load behavior for Nextcloud apps.

1|Updated Jul 16, 2026
One-click install
npx skills add https://github.com/ConductionNL/buildiq --skill test-performance-conductionnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-performance
Source: https://github.com/ConductionNL/buildiq/tree/main/.claude/skills/test-performance
Command: npx skills add https://github.com/ConductionNL/buildiq --skill test-performance-conductionnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications often ship with hidden performance bottlenecks—slow API endpoints, oversized JavaScript bundles, N+1 query patterns—that only surface under real usage. This Skill systematically tests page load times, API response times, sequential load behavior, and frontend bundle sizes against defined performance budgets, producing a structured report with actionable bottleneck findings. ## Core Features & Use Cases - Page Load Timing: Uses browser Performance APIs to measure TTFB, DOM Ready, and full load times across dashboards, list views, detail views, and settings pages, graded against target/acceptable/poor budgets. - API & Load Testing: Measures endpoint response times with curl at varying data sizes and runs 20 sequential requests to detect degradation, errors, and rate-limiting behavior. - Bottleneck Diagnosis: Detects N+1 query patterns, oversized JS bundles, and container resource spikes, then generates a markdown performance report with prioritized recommendations. - Use Case: Before releasing a Nextcloud app update, run the performance test to discover that a 2000-object list view takes 5.9 seconds to load and the search API needs server-side indexing—then fix these before users complain. ## Quick Start Ask the agent to run a performance test on the current app, for example: "Run a full performance test on the openregister app and report any bottlenecks."

Frequently Asked Questions about test-performance

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

FAQPage Schema
How do I test page load performance of a web app?▼

Use the browser Performance API via browser_evaluate to read navigation timing entries, extracting TTFB, DOM Ready, and full load times. Compare results against budgets: TTFB under 200ms is good, DOM Ready under 1000ms, full load under 2000ms.

How to measure API response times with curl?▼

Use curl with the -w "%{time_total}" flag and -o /dev/null to discard the body, printing only total request time. Test endpoints at varying data sizes (limit=10, limit=100) to see how response time scales with payload.

What performance budgets should a Nextcloud app meet?▼

Target TTFB under 200ms, DOM Ready under 1000ms, full page load under 2000ms, simple API responses under 200ms, and complex API responses under 500ms. Times above 1000ms TTFB or 5000ms full load are rated poor.

How do I detect N+1 query problems in a web app?▼

Monitor network requests during a list page load by filtering Performance API resource entries for API calls. A healthy list page makes 1-2 API calls total; one call per displayed item indicates an N+1 pattern requiring backend aggregation.

Can this skill run distributed load tests with concurrent users?▼

No, it performs sequential load testing only—20 rapid sequential requests to check for degradation, errors, and rate limiting. It is not a substitute for dedicated concurrent load-testing tools like k6 or JMeter.