Laravel maintenance for two established travel websites

How we took ongoing technical ownership of two live Laravel travel websites — cutting a key search page from about 17 seconds to about 1 second along the way.

~17s → ~1s search page load time
1,072 → 222 database queries on a key listing page

Our client runs two established travel websites on a shared Laravel platform. Both sites were live and taking bookings, so the brief was clear from day one: no risky rebuild — take ownership of what exists and keep making it better.

The challenge

The platform showed the typical symptoms of a mature application that had outgrown its original setup:

  • An important search page took around 17 seconds to load.
  • Production and staging bugs needed careful investigation and controlled releases.
  • Servers saw high load, including bot traffic spikes nobody had explained.
  • The business kept needing new features, which had to ship without destabilising the live sites.

What the client needed was not a one-off fix but a long-term technical partner responsible for the whole platform.

What we did

We became the ongoing technical owner of the platform — development, QA, project management and infrastructure support from one team, working the way we describe on How We Work.

  • Rebuilt the slow search. The cause was remarkable: the page loaded every result — images included — and hid them in the browser so search could filter on the frontend. We added real pagination, cut the image sizes and cleaned up the JavaScript. From about 17 seconds to about 1 second, verified through QA before release.
  • Took the same approach to a heavy listing page: 1,072 database queries became 222, the framework loaded 151 models instead of 1,806, memory use halved from 26 MB to 12 MB — and the page went from 1.21 seconds to 425 milliseconds.
  • Lighthouse performance scores followed: the about page went from 46 to 98, the homepage from 63 to 79, and a key property page from 66 to 80 — driven by image optimisation and a reorganised JavaScript bundle.
  • Fixed the surprises hiding in plain sight: the 404 page alone returned 431 kB of HTML and loaded a 3 MB image, taking up to 4.9 seconds just to say “not found” — it now answers in milliseconds.
  • Eliminated a production crash: one API endpoint could exhaust the server’s 512 MB memory limit answering a single request. Safe pagination fixed the crash — while the admin team kept the full list view they rely on every day.
  • Fixed business-critical production issues at the root cause — invoice views, upload behaviour, availability logic, broken routes — instead of patching symptoms on the server.
  • Set up CloudWatch monitoring with CPU and disk alarms, which caught unexplained load spikes — the trail led to scanner bots, and to a fix at the right layer (that story has its own case study).
  • Kept delivering business features — service levels, board types, weekly pricing, personal recommendation price boxes and integration planning for external availability sources.

The outcome

The headline number: the key search page went from about 17 seconds to about 1 second. Just as important, releases became routine — investigated, fixed, tested and shipped through a controlled workflow — and monitoring gave the client a real view of server health for future infrastructure decisions.

This is what our Laravel support and maintenance engagements look like: the platform keeps evolving, and someone is clearly responsible for it.

More case studies

Stabilising an inherited Laravel platform nobody dared to restart

Maintenance & Support Stabilising an inherited Laravel platform nobody dared to restart

A half-finished Typo3-to-Laravel migration, a 15 GB repository and a production server nobody dared to reboot. Audit first — then backups, security fixes, Docker and ~500 tests.

MySQL upgrade that cut about $10k a year in AWS costs

Modernisation & Upgrades MySQL upgrade that cut about $10k a year in AWS costs

An outdated MySQL 5.7 database was quietly adding about $900 a month in AWS Extended Support fees. We planned and ran a safe upgrade to 8.0 around a live legacy application.

SAP–Shopify sync rebuilt from legacy PHP to Symfony

Modernisation & Upgrades SAP–Shopify sync rebuilt from legacy PHP to Symfony

Six storefronts depended on a fragile black-box sync with SAP. We took it over and replaced it step by step with a Symfony middleware — without stopping the business.

Culinary events platform: years of maintenance and a UK launch

Maintenance & Support Culinary events platform: years of maintenance and a UK launch

We keep a Dutch culinary events platform stable through high-traffic ticket sales — and refactored its legacy Symfony core so the same system could launch in the UK.

300,000-SKU product catalogue: instant search and stable syncs

Maintenance & Support 300,000-SKU product catalogue: instant search and stable syncs

A custom PHP product information system struggled under 300k+ SKUs: slow searches and fragile Shopify and Shopware syncs. We modernised it in place — no rewrite.

REST API on a legacy Symfony app for a headless React frontend

Modernisation & Upgrades REST API on a legacy Symfony app for a headless React frontend

Instead of rewriting a Symfony 3.4 events platform, we exposed its existing business logic through 20+ REST endpoints — unblocking a full React migration at a fraction of rewrite cost.

From no-code prototype to a production SaaS platform

Product Development From no-code prototype to a production SaaS platform

A validated MVP built on Make, Bubble and Replit had hit its ceiling. We re-platformed it into a multi-tenant Symfony + React SaaS with a grounded AI content engine.

An AI legal-training MVP, live in about two weeks

Product Development An AI legal-training MVP, live in about two weeks

Law students practise argumentation against AI judge personas grounded in real legal documents. We designed and shipped the production-ready MVP in roughly two weeks.

Keeping a Symfony 1 / PHP 5.4 website safely in business

Maintenance & Support Keeping a Symfony 1 / PHP 5.4 website safely in business

A property website on Symfony 1 and PHP 5.4 still earned its keep. We maintain it carefully — SEO updates, feeds, cache issues — and brought production changes back under Git control.

The outage that wasn’t the application: a Route 53 DNS story

Rescue & Incident Response The outage that wasn’t the application: a Route 53 DNS story

Internal business systems stopped resolving even though the servers were healthy. We traced the outage layer by layer to incomplete Route 53 delegation and restored access.

Technical SEO cleanup for two Laravel travel websites

Maintenance & Support Technical SEO cleanup for two Laravel travel websites

After a difficult migration history, two travel websites had canonical, sitemap, redirect and indexation problems. We cleaned up the technical foundation as part of ongoing maintenance.

A real-time crypto signals SaaS on Symfony and ClickHouse

Product Development A real-time crypto signals SaaS on Symfony and ClickHouse

Tick-by-tick market data from major exchanges, analysed and delivered as trading signals in under half a second — through a web dashboard and a Telegram bot.

Monetising AI chatbots in WordPress — with no user accounts

Product Development Monetising AI chatbots in WordPress — with no user accounts

Five AI personas, a freemium paywall and Nordic Swish payments — built as a custom WordPress plugin that charges users without ever asking them to register.

industry

Travel & hospitality

tech stack

Laravel, MySQL, AWS

service

Maintenance & Support

system risk check

Want results like these for your application?

Start with a System Risk Check — a fixed-price technical audit of your application with a written, prioritised report. The report is yours, whatever you decide next.