Technical SEO & Website Speed Optimisation
Most SEO consultants can tell you a page is slow. Fewer can open the code, find the script or image causing it, and fix it. This is technical SEO and performance work done by a frontend engineer who spent years making high-traffic pages fast.
- ✓Website delivered in 24 hrs
- ✓First draft in 3 hrs
- ✓Free online consultation
- ✓Free draft website
Any of this sound familiar?
What a technical SEO audit covers
- Crawlability: robots.txt, internal linking, orphaned and blocked pages
- Indexing: canonical tags, duplicate content, noindex mistakes, redirect chains
- Rendering: whether content and links exist in the HTML or only after JavaScript runs
- Sitemaps that list only real, indexable URLs
- Structured data: valid, linked, and matching what visitors see
- Mobile usability, HTTPS and security headers
Core Web Vitals, explained without the jargon
Google measures three things from real Chrome users. Largest Contentful Paint — how long the main content takes to appear; good is under 2.5 seconds. Interaction to Next Paint — how quickly the page responds when someone taps or types; good is under 200 milliseconds. Cumulative Layout Shift — how much the page jumps around while loading; good is under 0.1.
These are measured at the 75th percentile of real visits, so a fast laptop on office Wi-Fi tells you little. The audit uses field data where it exists and reproduces slow conditions where it doesn't.
Track record
- Bigbasket checkout, 5M+ transactions a month: Largest Contentful Paint cut from 4.2s to 3.4s and time-to-interactive from 6s to 3.6s, through memoisation, code-splitting and deferring non-critical assets
- Bigbasket sitemaps: automated builds across 500,000+ product URLs, cutting regeneration from 3 hours to 8 minutes and improving crawl efficiency by 15%
- bb Elevate rewards interface: page loads held under 1.5 seconds at peak for 1M+ subscribers
- Service routing reworked with AWS ALB and Nginx: p95 latency from 380ms to 300ms at 10,000 requests a minute, without adding servers
Next.js and JavaScript-framework SEO
JavaScript frameworks are where technical SEO most often goes wrong, and where an engineer's view helps most: which routes are statically rendered, which are rendered per request, what ends up in the initial HTML, and how metadata is generated. For Next.js sites in particular, most indexing and speed problems trace back to a handful of rendering and caching decisions.
What you get
Every engagement is scoped to what your business actually needs, then quoted as one fixed number on a free call — before anything begins.
Everything Google checks under the hood, with a prioritised fix list.
- Crawling, indexing, canonicals, redirects and sitemaps
- Rendering: what Google actually sees on JavaScript-heavy pages
- Structured data validated against what's on the page
Why the site is slow for real users, measured — not guessed.
- LCP, INP and CLS diagnosed to the element and script
- Images, fonts, third-party scripts and bundle size
- Server response and caching reviewed
The audit's recommendations actually shipped, not left in a PDF.
- Pull requests against your repository
- Before-and-after measurements
- Search Console monitored after release
Anything bigger or unusual is scoped on a call — you get a fixed quote before work starts.
Real work, live where you can check it
No stock screenshots and no invented testimonials — these are builds you can open yourself.
Tell me what you need
A mobile number is enough to start — I'll come back within one working day with a straight answer on what it would take and what it would cost.
Questions people actually ask
Speed is a ranking signal, but a modest one — it rarely lifts a weak page above a more relevant one. Its bigger effect is on people: slow pages lose visitors before they load, so faster pages usually convert noticeably better even when rankings don't move.
Either. The audit is useful on its own for an in-house team, and the fixes can also be implemented directly in your codebase with before-and-after measurements.
Yes — the audit covers any site. Fixes on hosted platforms are limited to what the platform allows, and the report says clearly which recommendations fall into that category.
Typically one to two weeks, delivered as a written report with a prioritised fix list — most important and least effort first.
Book a free consultation
30 minutes, no cost, no obligation — pick a slot that works for you.
- ›Sign in with Google to book instantly
- ›Or just email/WhatsApp if you'd rather
- ›We'll follow up with a free draft, not a sales pitch