I will do load, stress and performance testing with jmeter and k6
Performance and load testing, test automation, API testing, 22 years in QA
Informazioni su questo servizio
Will your app survive launch day, or crash when real users arrive?
Professional load testing, stress testing and performance testing for web apps and APIs.
Most teams discover their limits in production: slow pages at peak, timeouts, a locked database and a post-mortem that costs more than any test. A generic load test with a pile of charts still doesn't tell you if it's safe to ship.
I give you a decision, not just charts. I build the load model from your real traffic, set SLOs, verify your NFRs and tell you GO or NO-GO at your target load, with the exact breaking point.
What's included:
- Load model and test scripts (JMeter or k6), reusable in CI
- Load, stress and spike runs on your staging
- Live Grafana dashboards, not a static PDF
- Bottleneck analysis and a prioritized fix list
- A clear GO / NO-GO verdict and a short report
Why me?
- 22 years in QA, Performance and QA Tech Lead
- Validated 50,000 concurrent users and 13,000 RPS on production platforms
- Results cross-checked across JMeter, k6, Gatling and Locust
Not sure which package fits? Message me your app, stack and target load, and I'll reply with an honest recommendation.
Applicazione di testing:
Sito web
Tecnologia di sviluppo:
Java
•
JavaScript
•
Python
•
Scala
•
TypeScript
Dispositivo:
Mac
Il mio portfolio
FAQ
Why should you choose me?
22 years in QA as Performance and QA Tech Lead. I've validated platforms at 50,000 concurrent users and 13,000 RPS. You get a clear GO / NO-GO decision at your target load and the exact breaking point, not just a pile of charts.
What's included?
A load model based on your real traffic, JMeter or k6 scripts, load and stress runs, live Grafana dashboards, bottleneck analysis, a prioritized fix list and a GO / NO-GO verdict. Scripts are yours and reusable in CI.
What's not included?
Rewriting your application code. I pinpoint the root cause and the fix, and Premium includes tuning recommendations, but code changes stay with your team. Also excluded: cloud compute for very large runs and testing production without your written OK.
Which package should I choose?
Basic: 1 page or endpoint, about 50 virtual users, a quick check before a release. Standard: load and stress test of your key flows with p95/p99, errors and bottlenecks. Premium: full audit with load, stress, spike and soak runs against your SLAs, root cause and tuning.
What do you need from me to start?
The URL or API endpoints, your expected peak load (users or requests per second), test accounts for logged-in flows and ideally a staging environment. Analytics data on real traffic helps me build a realistic load model.
Will load testing crash my live site?
Not by surprise. We agree limits and timing first. I test on staging or off-peak with a controlled ramp-up and stop at agreed error thresholds. Finding the breaking point in a test is exactly what protects your production.
Do you have the infrastructure to generate that load?
Yes. Load generators are spun up per test and torn down after: distributed JMeter or k6 in your cloud, my own spot cluster, or a managed grid (k6 Cloud, BlazeMeter). Compute for a big run is agreed upfront on the scoping call.
Which tools do you use?
JMeter and k6 as main engines, Gatling and Locust when your stack fits them, Grafana and InfluxDB for live dashboards. Key results are cross-checked across tools, so you can trust the numbers.
Can my team re-run the tests later?
Yes. You get clean, documented scripts and a short guide to re-run them. On request I also wire them into your CI (GitHub Actions, GitLab or Jenkins), so every release is checked against the same SLOs automatically.
Can you test AI or LLM apps too?
Yes. Besides classic load testing I test AI features: LLM response latency and cost under load, quality evals, red teaming for prompt injection and data leaks, and readiness checks for the EU AI Act. Ask me for a custom offer.

