Home › Blog › Testing & QA
Testing & QA

Performance and Load Testing Basics: Will Your App Survive Launch Day?

Short answer

Performance testing checks how fast and stable your app is under realistic and extreme load. You define target users and response times, simulate traffic with tools such as k6, JMeter or Locust, find bottlenecks (database queries, caching, third-party APIs) and re-test. Specialised load and scalability testing is $50 per hour at AWI Digital.

AWI Digital Team 2026-10-06⏱ 3 min read

Types of performance test

TypeQuestion it answers
LoadDoes it hold at the expected peak (for example 500 concurrent users)?
StressWhere does it break, and how does it fail?
SpikeCan it survive a sudden surge (a campaign, a TV mention)?
SoakDoes it degrade over hours (memory leaks)?
ScalabilityDoes adding servers actually add capacity?

Metrics that matter

  • p95 and p99 response times, not just averages
  • Error rate under load
  • Throughput (requests per second)
  • Database CPU, connections and slow queries
  • Cost per 1,000 requests, especially with paid AI APIs

A simple plan

  1. Define realistic user journeys and peak numbers from analytics.
  2. Set pass/fail targets (for example p95 under 800 ms, errors under 1%).
  3. Script the journeys in k6 or JMeter.
  4. Run baseline, then ramp to peak, then stress.
  5. Fix the top bottleneck, re-run, repeat.

Web speed is a performance test too

For public sites, Core Web Vitals (LCP, INP, CLS) affect user experience and SEO. We tune images, scripts and caching on every SEO-ready website.

Example test plan for a booking app

ItemValue
Peak expectation300 concurrent users after a campaign
JourneysBrowse availability (60%), book (25%), view booking (15%)
Targetsp95 under 800 ms; errors under 1%; CPU under 70%
Phases5-minute ramp, 15-minute steady state, 5-minute stress to 2× peak
Typical fixesAdd database indexes, cache availability, queue emails, compress images

Reading the results

  • A rising p95 with flat CPU often points to database locks or slow third-party calls.
  • Errors that appear only at high load usually indicate connection limits or timeouts.
  • Always retest after each fix; one bottleneck often hides the next.

Load-test before launch From $50/h

Tell us expected traffic. We design and run the test.

Frequently asked questions

How many users should I test for?

Use peak concurrent users you expect in the next 6–12 months, then test at 2–3 times that for headroom.

Can you test apps that call LLM APIs?

Yes, and we also test rate limits and costs, since LLM calls can dominate both latency and budget.

Get a free quote in 24 hours

Tell us what you need. We reply with scope, timeline and a fixed price.

Keep reading