Client: KeyStone · Regulated Verticals · UK property SaaS (85 staff)

Improving Load Times for a Property Portal

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team maintained KeyStone’s PHP and MySQL property portal. Over six months, the client’s Sentry records show page-load time falling from 5.4 to 1.8 seconds. Recurring defects in Jira fell from 22 to 6 per quarter.

Client and engagement facts

Client
KeyStone
Industry
Regulated Verticals
Business context
UK property SaaS (85 staff)
Delivery model
Software maintenance
Application
Property portal with tenant portal
Supplied geography
UK
Company size in source
85 staff

Application stack and tools

Application stack

  • PHP/Laravel→Node.js
  • MySQL
  • AWS

Tools used

  • Sentry
  • Jira
  • client mobile analytics

Why Support Was Needed

A page load triggered about 40 database queries, and property search queried MySQL directly. The engineers consolidated the repeated queries and moved search to an indexed service.

Technical Work

  • Consolidated 40 queries to 6.
  • Moved property search from MySQL to a Node.js service with an index.
  • Fixed an N+1 query that had been there for two years.

Representative Incident

A CDN outage produced a page-load spike in month four. The team documented the incident and recorded it separately in the maintenance report.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Page load5.4 s1.8 ss6 monthsClient Sentry; Scope: The six-month page-load trend excludes the CDN outage.
Recurring defects22/q6/q/q6 monthsClient Jira
Mobile bounce41%19%%6 monthsClient analytics

Evidence and Limitations

The six-month page-load trend excludes the CDN outage. The table uses Sentry, Jira and the client’s mobile analytics.

Page Load Investigation

The engineers reduced the query count from 40 to six and moved property search to an indexed service.

Scope a Similar Engagement

Share which pages are slow, how performance is measured and the permission boundaries for repairs. Request a support plan or explore software maintenance.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.