You will get Fix a slow PHP / Laravel / MySQL query
Project details
Most slow-query fixes are guesses — someone adds an index, hopes, and moves on. I
don't guess. I run query-plan analysis to find where the database is actually spending
time, then fix the cause: a missing composite index, an N+1 pattern, a query the
planner can't use an index for. Targeted, not index-everything.
I've done this in production at scale — one critical query went from 12 seconds to 87
milliseconds with the right plan analysis and indexing. Nearly five years of PHP
backend work means I read your query in context: if it's coming from Laravel Eloquent
or Yii, I fix the ORM-level cause too, not just the raw SQL.
You get the optimised query, the index changes, and a short note on what changed and
why — so the fix is maintainable, not a black box you're afraid to touch. Scoped, fast,
and delivered through Upwork's escrow protection.
don't guess. I run query-plan analysis to find where the database is actually spending
time, then fix the cause: a missing composite index, an N+1 pattern, a query the
planner can't use an index for. Targeted, not index-everything.
I've done this in production at scale — one critical query went from 12 seconds to 87
milliseconds with the right plan analysis and indexing. Nearly five years of PHP
backend work means I read your query in context: if it's coming from Laravel Eloquent
or Yii, I fix the ORM-level cause too, not just the raw SQL.
You get the optimised query, the index changes, and a short note on what changed and
why — so the fix is maintainable, not a black box you're afraid to touch. Scoped, fast,
and delivered through Upwork's escrow protection.
Database Type
MySQL, SQLite, PostgreSQLWhat's included
| Service Tiers |
Starter
$55
|
Standard
$120
|
Advanced
$250
|
|---|---|---|---|
| Delivery Time | 2 days | 3 days | 5 days |
Number of Revisions | 1 | 2 | 2 |
Number of Queries | 1 | 3 | 10 |
Query Debugging | - | ||
Query Optimization | |||
Query Scheduling | - | - | - |
Query Analysis | |||
Source Code |
Optional add-ons
You can add these on the next page.
Fast Delivery
+$35 - $60
Additional Revision
+$20
Additional Query
(+ 1 Day)
+$35
Query Debugging
(+ 2 Days)
+$40Frequently asked questions
About Pavel
PHP / Laravel Backend Engineer | Legacy Modernisation & Performance
Belgrade, Serbia - 3:39 am local time
apps, tangled legacy code, databases that turned into bottlenecks. Nearly five years
of production backend work. I write the code and ship it: containerised and
pipeline-ready, not handed off half-done.
What I do:
- Legacy modernisation and technical-debt refactoring — incremental, without stopping
the business (Service/Repository, layered architecture)
- Backend performance and SRE — profiling, caching (Redis), load testing, bottleneck
elimination
- Database query optimisation — query-plan analysis, index strategy, N+1 elimination
- Third-party API integration — webhooks, signature verification, async queues
(WhatsApp, Telegram, payment and delivery APIs)
- REST API design and backend logic in Laravel 7–10 and Yii2 (PHP 7.x–8.x)
A few recent results:
- Cut a critical PostgreSQL query from 12s to 87ms — query-plan analysis plus
targeted composite indexes
- Reduced CI/CD deploy time across 20+ services from 20 minutes to under 3
- Raised automated test coverage on a legacy codebase from 50% to 93%
- Extracted a hot data-processing job from PHP into Go: ~12× faster, 5× less memory
I deliver backends containerised (Docker, Nginx + PHP-FPM) and pipeline-ready
(GitHub Actions), so you don't need a separate DevOps resource to get my work into
production.
Working languages: English (strong written / async), French (fluent — FR, CH, BE, LU
with no language barrier), Russian (native). Based in Belgrade, CET — comfortable
across EU and US-overlap hours.
If you have a PHP codebase that's slow, fragile, or costing more to maintain every
quarter, send me the symptoms and I'll tell you what I'd look at first.
Steps for completing your project
After purchasing the project, send requirements so Pavel can start the project.
Delivery time starts when Pavel receives requirements from you.
Pavel works on your project following the steps below.
Revisions may occur after the delivery date.
Reproduce & analyse
I review your query, schema, and table sizes, reproduce the slow behaviour, and run query-plan analysis (EXPLAIN) to find where time is actually being spent — so the fix targets the real cause, not a guess.
Fix the root cause
I rewrite the query and/or add targeted indexes matched to your real access paths — addressing the actual bottleneck (a missing index, an N+1 pattern, an unusable plan) rather than indexing everything and hoping.