Service
Website speed optimisation
Finding out why your site is slow, telling you plainly, and then fixing it - usually in the database rather than the design.
Audit from ₹6,000
The usual diagnosis
Slow sites are rarely slow because the code is slow. They are slow because the same work is being done over and over - the same query on every page load, the same list fetched to count it, a full-resolution image scaled down in the browser instead of on the server.
That is good news, because repeated work is the cheap kind of slowness to fix. It is also why speed work is worth buying as a standalone piece rather than as a reason to rebuild everything.
What gets looked at
- Core Web Vitals - LCP, CLS and INP - measured on a real page rather than a lab score you cannot act on.
- Database queries: the N+1 patterns, the missing index, the query that loads every row to display ten.
- Caching, and whether anything is cached at all. This is the single biggest win on most .NET and WordPress sites.
- Images - format, dimensions, and whether the browser is being handed a 4000px photo for a 400px slot.
- JavaScript weight, and how much of it runs before the page becomes usable.
- Hosting and server configuration, including whether you are paying for a plan that is throttling you.
What you get
A prioritised report: what is slow, why, how much each fix is worth, and roughly what each costs. Ordered by return, not by how easy it is for me.
It is written to be readable by whoever signs off the budget, not only by a developer - and you keep it whether or not I do the work. If the fixes are simple enough for your existing developer to apply, that is a perfectly good outcome.
An honest note on what speed buys you
Speed is a ranking input, but a small one next to relevance. Making a page faster will not rank it for something it does not answer.
What speed reliably does is stop you losing the traffic you already earned. The measurable effect usually shows up in bounce rate and conversions before it shows up in rankings, and that is the honest case for doing it.
Work you can go and look at
Questions people actually ask
- How much faster will my site get?
- I will not put a number on it before looking - anyone who does is guessing. What I can say is that the audit tells you the expected gain per fix before you commit to any of them, so you decide with the numbers in front of you.
- Do I have to rebuild the site?
- Usually not. Most of the gain comes from caching, queries and images, none of which need a rebuild. A rebuild only makes sense when the platform itself is the problem, and that is a conclusion the audit reaches with evidence rather than an assumption it starts from.
- Does this work on WordPress?
- Yes. The diagnosis is the same everywhere - repeated work, uncached queries, oversized images - and WordPress sites tend to have all three, usually contributed by plugins rather than by the theme.
- Can you fix it, or just tell me what is wrong?
- Either. The audit stands on its own and you keep it. If you want the fixes applied I will quote them from the report, itemised, so you can take some and leave others.

