Flame graph
Find the PHP path burning the time
Collapse vendor noise, follow the hot branch, and see the function stack that explains the slow trace.
Find what is
actually making
PHP slow
Perfbase shows the hot function path, repeated queries, queue regressions, cron bottlenecks, and framework overhead behind each trace, so performance work stops being guesswork. Supports PHP 7.4 through 8.5.
Hot paths N+1 queries Queue regressions Cron bottlenecks CLI profiling Framework overhead
console.perfbase.com
Business
Know where slowness is affecting revenue paths and internal throughput.
Technical
See whether the problem is one route, one worker type, or one framework path.
Practical
Get evidence the person fixing the issue can act on immediately.
Customers feel the lag first
Checkout, dashboards, internal tools, and APIs lose trust before anyone agrees on the cause.
Engineering loses time to guesswork
Logs, averages, and local repros rarely show the exact path that made the PHP application slow.
Leadership needs evidence, not blame
A profiler gives the team something concrete when performance drops after a release, migration, or config change.
Product insight
Move from slow trace to clear fix path
Start with the trace views that explain why PHP is slow, then zoom out to history views that show whether the same action, project, or organisation is getting healthier over time.
Query analysis
Separate database work from PHP work
Inspect query timing, duplicate SQL, and database cost in the same trace context as the application code.
Host resources
Compare trace cost with host pressure
Check CPU, memory, disk, and network activity beside the PHP trace so infrastructure pressure and code cost are easier to separate.
History per action
Follow one route, job, or command over time
See volume, p95, slow-request share, error rates, and the matching trace list for a single PHP action.
History per project
Understand project-wide performance drift
Roll up every action in a project so the team can spot regressions and compare top-level PHP health at a glance.
History per organisation
See organisation-level trace trends
Track total trace volume and response-time movement across projects, with recent activity and resources nearby.
What PHP profiling should give you
Move from “something is slow” to a clear fix path
The point of a profiler is not another chart. It is clarity: where the cost lives, which part of the stack caused it, and what the team should do next.
Request trace
01
Perfbase
GET /checkout
CartController::show
PricingService::calculate
SQL query x18
Request traces
See the request path, not just the latency number
Find the exact path that is dragging: the function stack, the branch consuming the time, and the query activity attached to the same request.
Find the hot path inside a request
See repeated queries in the same workflow
Keep framework context attached to the trace
Background execution
02
Perfbase
queue.ProcessInvoice
cron:nightly-rollup
console cache:warm
worker latency spike
Background work
Keep jobs, cron, and commands in the same picture
A lot of PHP pain lives outside browser traffic. Workers, scheduled jobs, and CLI commands need the same clarity as requests.
Profile queues, workers, and scheduled tasks
Trace CLI commands alongside web traffic
Use one workflow for foreground and background execution
Framework-aware
03
Perfbase
middleware stack
plugin overhead
route context
worker attributes
Framework context
Know whether the cost came from the app or the stack around it
Generic traces are not enough. You need to know whether the drag came from middleware, plugins, modules, routes, or commands so the next move is obvious.
Start with first-party PHP framework integrations
Use the SDK when the app is custom
Keep the traces readable for the whole team
Framework coverage
Start from the framework you already run
Perfbase has dedicated setup paths for the main PHP frameworks, plus a PHP SDK for custom applications and internal frameworks.
Browse all integrationsLaravel
Automatic profiling for HTTP requests, jobs, and Artisan commands.
WordPress
Automatic profiling with WooCommerce support and admin settings page.
Symfony
HTTP and console profiling for Symfony 5.4, 6.x, and 7.x.
Drupal
HTTP, Drush, cron, and queue profiling for Drupal 10.3+ and 11.
CakePHP
HTTP and command profiling for CakePHP 4.4+ and 5.x.
Slim
HTTP middleware and manual CLI profiling for Slim 3 and 4.
Getting started
Get to a first useful trace quickly
Create a project, install the extension, add the framework package, and start collecting traces. No long setup story required.
Extension support today covers Mac and Linux, across Intel, Apple Silicon, x86_64, and ARM64 environments.
01
Create your project
Sign up, create an organization and project, and grab your API key from project settings.
Register for free →02
Install the extension
One command installs the PHP extension. Auto-detects your PHP version, OS, and architecture.
bash -c "$(curl -fsSL https://cdn.perfbase.com/install.sh)"03
Add your framework package
Install the package, set your API key, and finish the framework setup.
composer require perfbase/laravel:^1.0PERFBASE_ENABLED=true
PERFBASE_API_KEY=your-api-key
PERFBASE_SAMPLE_RATE=0.1Data regions
Keep trace data in the region that fits your compliance requirements
Perfbase supports regional trace storage for teams that need data to stay in a specific geography, whether that is driven by compliance, contracts, or internal policy.
Available regions
Europe
🇫🇷 France 🇩🇪 Germany 🇬🇧 London 🇵🇱 Poland
APAC
🇮🇳 India 🇸🇬 Singapore 🇦🇺 Sydney
America
🇨🇦 Toronto
Compliance-friendly by design
Choose a storage region that matches customer requirements, procurement rules, or internal data-handling policy.
Same profiling workflow
Regional storage does not change how teams install Perfbase, collect traces, or work from the console once data starts flowing.
FAQ
Questions people ask before they adopt a PHP profiler
What is PHP profiling?
PHP profiling is the practice of measuring what your PHP application actually does during a request, job, or command: which functions ran, how long they took, how memory changed, and where query work happened.
How is Perfbase different from generic monitoring?
Generic monitoring can tell you that an endpoint is slow. Perfbase is built to show why it is slow by exposing the PHP execution path, framework context, and query activity behind a trace.
Can Perfbase profile queues, cron, and CLI commands?
Yes. Perfbase is designed for more than HTTP traffic. The integrations and SDK cover background jobs, scheduled work, and command-line execution so those bottlenecks stay visible too.
Do I need to instrument every code path manually?
No. The main PHP framework integrations are designed to get you useful traces quickly. You can add manual spans later through the SDK when you want extra precision.
Which PHP frameworks does Perfbase support?
Perfbase supports PHP 7.4 through 8.5, with dedicated integration pages for Laravel, WordPress, Symfony, Drupal, CakePHP, Slim, Joomla, Yii, CodeIgniter, plus a PHP SDK for custom applications.
Which platforms does the Perfbase extension support?
The Perfbase extension currently supports Mac and Linux environments, covering Intel, Apple Silicon, x86_64, and ARM64 setups.
Which data regions are available for trace storage?
Perfbase can store trace data in grouped regional locations: Europe: France, Germany, London, Poland; APAC: India, Singapore, Sydney; America: Toronto. This gives teams a way to align trace storage with compliance requirements or regional preferences.
Start profiling
Stop guessing where the PHP slowness is coming from
Start with the framework you already use, get to your first trace quickly, and see what is actually making the application slow.