Phase 1 · Week 1
Measure
28 days of your real field data, your slowest templates profiled, every third-party script traced. You get a written report: what's slow, why, and what it's costing you.
Out · audit doc + priority list
The problem
You didn't buy a slow store. You accumulated one.
A review widget. A chat widget. A page builder, four analytics tags, a theme running 900 queries on every product page. Each one was worth it on its own. Together they put two extra seconds between a shopper and your add-to-cart button — and your team never sees it, because you browse a warm-cached store on office wi-fi.
Your store
$3M/yr
traffic you have already paid for
Drag to your revenue
One sprint
4.6s → 1.4s
mobile LCP, measured on real field data
What that's worth
+$210k
a year, at a 7% lift per second — on the same traffic
Illustrative, using published ecommerce benchmarks and placeholder sprint figures. Your audit runs the same math on your revenue and your field data.
The process
Measure → fix → hold
Three weeks, one price, agreed before we start. You always know which week you're in and what lands at the end of it.
Phase 2 · Week 2
Fix
Server response, render path, images, JS budget, tag load order, database queries. Built on a staging clone, tested through checkout, deployed only once you approve the diff.
Out · shipped changes + changelog
Phase 3 · 90 days
Hold
Speed rots — the next plugin undoes the last sprint. We put a performance budget in your build and watch your field data for 90 days. If it drifts, we fix it.
Out · budget in CI + 90-day watch
What people say Colleagues from Automattic
“He’s the type of engineer you can trust to own a problem end-to-end and deliver results without cutting corners.”
Mehedi Hasan Masum
Manager · Automattic
Mehedi Hasan Masum
Manager · Automattic
“He’s the type of engineer you can trust to own a problem end-to-end and deliver results without cutting corners.”
Full testimonial → Denis Dvali
Manager · Automattic
“He doesn’t just apply quick fixes — he looks for root causes and long-term solutions.”
Full testimonial → Akeda Bagus
Teammate · Automattic
“He consistently looked for ways to optimize systems, improve reliability, and reduce friction in critical user flows.”
Full testimonial → Prahesa Kusuma Setia
Teammate · Automattic
“He was thorough, technically grounded, and brought the kind of attention to detail that work at that scale demands.”
Full testimonial → Who you'll be working with
Hi, I'm Anas. You get me on the call and me in the codebase.
Twelve years in PHP, WordPress and WooCommerce, from the theme layer down to the query plan. I started Tobasoft because performance work is usually sold as an open-ended retainer, and it shouldn't be. A store either passes Core Web Vitals on real traffic or it doesn't — finding out takes a week, not a quarter.
We're a small studio in Toba Tek Singh, Punjab, working with ecommerce teams in the US and Europe. No account manager between you and the person reading your query log. Everything we find gets written down — including the parts where the answer is "don't hire us for this".
In public
All teardowns → Store teardowns, with the waterfall and the fix.
The review widget that cost 1.9s on every product page Why your cart is slow even with full-page caching on 900 queries on one product page, and the four that mattered
Placeholder titles — swap for your published posts.
Free · no call required
Start with the numbers, not with a sales call.
Give us your store URL. In three working days you get the same written audit we'd use to scope a sprint. Act on it yourself, hand it to your developer, or ignore it. No obligation.
- 28-day field data for LCP, INP and CLS
- The three heaviest things on your product page
- What we'd change first, second and third
- A revenue estimate run on your own numbers
Request received
Thanks — we'll pull your field data and send the written audit within three working days. One email, nothing else.
Straight answers
What people ask before they hire us.
We already run WP Rocket and a CDN. Isn't that it?
Caching hides a slow site from the lab test. It doesn't help logged-in shoppers, the cart or the checkout — which is exactly where your revenue happens. Most stores we see already cache, and still fail Core Web Vitals on field data.
Will you break my theme or my checkout?
Every change is built on a staging clone of your store and tested through a full checkout before you see it. You approve the diff, we deploy, and everything is reversible in one step.
My host says the server is fine.
It usually is. Server response is one of six things that decide what your buyer experiences, and rarely the biggest. The audit tells you which one is actually costing you — including the honest answer “your host is fine, your tag manager isn't”.
You're in Pakistan. How does that work for a US or EU team?
We overlap US mornings and European afternoons, work in your Slack, and write everything down so nothing depends on catching us live. The free audit is the low-risk way to test how we communicate before any money moves.
What if the numbers don't move?
We agree the target before the sprint starts, in writing, measured on your field data. If your Core Web Vitals aren't green 90 days after we ship, you get the sprint fee back. We'd rather turn down a store we can't move than sell you a retainer.
What does it cost, and how long does it take?
Three weeks, one fixed price, quoted after the free audit — because we won't price work we haven't measured. Fixed scope, fixed price, no hourly billing and no change orders.
Book a call
Every day you wait, the slow version of your store is the one taking orders.
Thirty minutes, video, no deck. We pull your field data live, name the three things we'd change first, and tell you straight whether a sprint is worth it. You keep the notes either way.
Three sprints a quarter · 2 slots open for next quarter
Calendly embed 30 min · video
Your Calendly goes here Inline widget · 320px min height
No times work? Email hello@tobasoft.io and we'll find one. — Muhammad Anas, founder