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.
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.
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.
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.
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.
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.
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, queue 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 and 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.
Create your project
Sign up, create an organization and project, and grab your API key from project settings.
Register for free →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)"Add your framework package
Install the package, set your API key, and traces start flowing immediately.
composer require perfbase/laravelPERFBASE_ENABLED=true
PERFBASE_API_KEY=your-api-keyData 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
APAC
America
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 has dedicated integration pages for Laravel, WordPress, Symfony, Drupal, CakePHP, Slim, Joomla, Yii, CodeIgniter, plus a PHP SDK for custom applications.
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.