detect-bottlenecks

Detect performance bottlenecks in Laravel or PHP applications via static analysis and profiling.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Serg28/demosite --skill detect-bottlenecks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-bottlenecks
Source: https://github.com/Serg28/demosite/tree/main/.agents/skills/detect-bottlenecks
Command: npx skills add https://github.com/Serg28/demosite --skill detect-bottlenecks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps pinpoint the causes of slow or inefficient system performance in Laravel/PHP projects, enabling targeted optimizations.

Core Features & Use Cases

  • Performance Analysis: Detects CPU, memory, I/O, database query, caching, and locking issues that impair application speed.
  • Root Cause Identification: Provides insights into bottlenecks by examining various zones such as database queries, code hotspots, and resource contention.
  • Use Case: Developers troubleshooting a slow-loading Laravel page can use this Skill to identify whether the slowdown is due to database queries or memory leaks, then apply appropriate fixes.

Quick Start

Use the detect-bottlenecks skill to analyze a slow Laravel API endpoint and generate a detailed report on bottlenecks.

Frequently Asked Questions about detect-bottlenecks

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

FAQPage Schema
How do I find performance bottlenecks in a Laravel application?

To find performance bottlenecks in a Laravel application, analyze database queries, CPU usage, memory leaks, caching, and locking issues using static code analysis, query explain plans, and runtime profiling to deliver precise diagnostics.

What causes slow database queries in PHP applications?

Slow database queries in PHP applications are caused by inefficient query execution plans, resource contention, or locking issues, which can be identified by examining query explain plans and profiling database interactions.

Does this bottleneck detection approach work for general PHP projects or only Laravel?

This bottleneck detection approach works for both general PHP projects and Laravel applications, diagnosing CPU, memory, I/O, caching, and locking issues across deployment environments to optimize speed and resource usage.

What's the best way to profile CPU and memory hotspots in PHP code?

The best way to profile CPU and memory hotspots in PHP code is using static code analysis combined with runtime profiling to pinpoint code hotspots and resource contention, enabling targeted optimizations.

Why is my Laravel API endpoint experiencing slow response times?

Your Laravel API endpoint experiences slow response times due to database query bottlenecks, memory leaks, caching inefficiencies, or locking issues, which are diagnosable through static code analysis and runtime profiling.

When should I use static code analysis versus runtime profiling for optimization?

Use static code analysis to detect code hotspots and structural inefficiencies, and apply runtime profiling to examine live database query execution plans, resource contention, and memory usage across deployment environments.