Fixed-price project

Laravel performance optimization: find why your app is slow and fix it

I find why a Laravel app is slow, fix the biggest causes first, then measure again and show you the before and after. It suits apps with slow pages, queries or jobs, from $300 for a written report in 3 days.

Price
From $300
Delivery
3 days
at the Performance audit tier
Packages
3 tiers

Who it is for

Who this helps

  • Apps that feel slow, or that slow down when more people use them
  • Teams with slow pages, slow reports or jobs that take too long
  • Owners who see database load or server cost rise and do not know why
  • Developers who want an outside senior review before they tune by guess

Signs

Signs you need this

  • Some pages take seconds to load, and it gets worse as your data grows.
  • The app is fine in the morning and slow at peak hours.
  • Jobs pile up in the queue, or emails and exports arrive late.
  • The database server is busy even when traffic is normal.
  • You added server power before and the app is still slow.

Scope

What I do

  • I measure before I touch anything

    I start with numbers: slow pages, database queries, queue timing and cache use. Telescope shows one request in depth on a local or staging copy. Pulse shows slow routes, queries and jobs across real traffic. The first list of problems comes from this data, not from guesses.

  • Queries and indexes

    The database is the usual cause. I look for N+1 queries, where code runs one query for every row instead of loading related data at once. I also look for missing indexes, queries that load too much, and reports that should run in the background.

  • Cache and queues

    I check what can be cached and for how long, and how often the cache is hit or missed. The Laravel deploy guide says to cache config and views on every release, and routes in a large app, so I check that too. For queues I look at slow jobs and at how workers and retries are set up.

  • Server and monitoring

    In the largest package I also look at the server side, such as PHP and web server settings and the cache and queue backends. I set up monitoring so you can watch the same numbers after I finish. I build the open-source Guzzle Watcher for Telescope and the Guzzle Recorder for Pulse, so slow calls to outside APIs are visible too.

  • What I need from you

    Access to the code, a list of the pages or jobs that feel slow, and your stack: PHP, database, cache and queue. Send slow query logs or monitoring data if you have them. If not, I tell you what to switch on first. A copy of your data helps, because queries behave differently on a small test database.

  • What is not included

    Buying a bigger server, changing your host, and rewriting the app are not part of these packages. I also do not promise a set speed. The result depends on your data and traffic, so I show you the numbers before and after each fix.

Packages

Pick a package

Fixed price in US dollars. Each package lists what is included.

Performance audit

$300

3 days · 1 revision

You need to know what is slow and why before you pay for fixes.

  • Measurement of slow pages, queries, jobs and cache
  • Written report of the top slow spots and their causes
  • Ranked fix plan, biggest wins first

Audit and fixes

$900

10 days · 2 revisions

You want the worst problems fixed, not only listed.

  • Everything in the performance audit
  • Fixes for the worst slow queries
  • Fixes for caching and slow jobs
  • New measurements after the fixes

Full tuning and monitoring

$2,000

21 days · 3 revisions

A busy app needs deeper tuning and a way to keep watching it.

  • Deep tuning of queries, cache and queues
  • Server-side tuning
  • Monitoring setup, so you can keep watching the numbers

Process

How it works

  1. Step 1

    You send code and slow spots

    You give me read access to the code and name the pages or jobs that feel slow.

  2. Step 2

    I measure

    I record where the time goes: requests, queries, queues and cache. You get the causes, ranked by impact.

  3. Step 3

    I fix the biggest causes first

    In the packages with fixes, I change code, indexes, cache and jobs, one cause at a time.

  4. Step 4

    I measure again and report

    I repeat the measurements so you can see what changed. You get the report and notes for your team.

Proof

Related work and reading

Case study

Laravel Telescope Guzzle Watcher

Open-source Laravel package for observing outbound HTTP requests made through guzzlehttp/guzzle inside Laravel Telescope. The package uses...

Case study

Laravel Pulse Guzzle Recorder

Open-source Laravel package for recording outbound Guzzle HTTP calls in Laravel Pulse. The recorder helps teams inspect slow or high-volume...

FAQ

Questions about this project

I measure first. I look at slow requests, database queries, queue timing and cache hits on your real app or a copy of it. Telescope shows one request in depth on a local or staging copy, and Pulse shows slow routes, queries and jobs across traffic. The fix list comes from these numbers, not from guesses.

No. I cannot promise a number before I see your data and traffic. What I do promise is a measured before and after for each fix, so you can see what changed. Some causes give a big gain and some give a small one, so I rank the fixes by expected gain.

It is a query that runs once for every row in a list, instead of once for the whole list. The Laravel docs show a list of 25 books that runs 26 queries, where eager loading needs two. On big lists this adds up fast, so it is one of the first things I look for.

Start with the audit if you do not know the cause. It is the smallest package and gives you a written, ranked plan. If you already know the slow pages and want them fixed, the middle package does both. The largest suits a busy app that also needs monitoring.

Yes, in the largest package. I set it up so you can watch the same numbers after I finish. I build the open-source Guzzle Watcher for Telescope and the Guzzle Recorder for Pulse, so slow calls from your app to outside APIs show up as well.

Yes, with care. I work on a copy of the code and check each change before it goes live. On the live app I only use tools that are meant to run in production, and you decide when each fix is released. I do not need live passwords or keys to read the code.

Need something different?

If your work does not fit these packages, tell me what you need and I will reply with a plan.

More projects

From $350

Laravel upgrade

Upgrade an old Laravel app step by step, with login, payments and queues checked.

  • Audit and step-by-step plan
  • One version at a time
  • Login, payments, queues checked

From $300

HubSpot integration

Contacts, companies and deals kept in step between Laravel and HubSpot.

  • Two-way sync with retries
  • Failed records logged and retried
  • Code in your repository

From $250

Stripe integration

Checkout, subscriptions and webhooks that keep your records in step with Stripe.

  • Verified, queued webhooks
  • Duplicate events handled
  • Code in your repository

See all services