Website Speed & Performance Audit

A deep technical audit of what is actually slowing your website down, with a fix list ranked by real-world impact on load time and Core Web Vitals.

Audit

Website Speed & Performance Audit

req/s, zero deadlocks
15Kreq/s, zero deadlocks
double-charges in production
0double-charges in production
production systems shipped
10+production systems shipped
years building for clients
7+years building for clients
Sound familiar

Signs you need this now.

Generic speed-test scores tell you a number is bad; they don't tell you why or what to fix first. This audit traces slow load times to their actual cause — unoptimized images, render-blocking scripts, bloated third-party tags, poor caching — and ranks fixes by how much load-time they'll actually save.

01

A speed test score everyone knows is bad

The report says "poor," but nobody on the team knows what's actually causing it or where to start. A number without a cause is not actionable.

02

Mobile visitors bounce before the page loads

Analytics shows a spike in mobile exits within the first few seconds — a strong sign speed is the culprit. Every second of extra load time compounds that exit rate further.

03

A redesign made the site slower, not faster

A recent visual refresh looks better but somehow loads worse, and no one's traced why. New design decisions often quietly reintroduce the same performance problems the old site had.

Scope

What you get.

Core Web Vitals report under throttled mobile conditions

LCP, INP, and CLS measured the way real visitors actually experience your site, not a best-case lab run.

Waterfall analysis of the biggest offenders

The specific render-blocking and largest-contentful-paint culprits identified by name, not by category.

Image and asset audit

Format, compression, and lazy-loading gaps flagged page by page, with the expected savings for each fix.

Third-party script and tag audit

Analytics, chat widgets, and ad pixels checked for how much they are actually costing you in load time.

Caching and CDN configuration review

Whether your current setup is actually serving cached, compressed assets the way it should be.

A prioritized fix-it list ranked by expected load-time improvement

Every recommendation comes with its estimated impact, so you know what to fix first.

Engagements

Three ways to work together.

Scoped in milestones, not one large commitment. Every engagement is quoted against a written plan; no figure gets invented before the scope is understood.

One-Time Audit

The diagnostic, on its own

3-5 business days

Best for: You want a clear, ranked list of what to fix, with no obligation to hire anyone for the fixes

  • Full audit as scoped for this service
  • Prioritized, ranked fix-it report
  • A live walkthrough call to go over findings
  • No pressure to continue past the audit
Most common

Audit + Fix Implementation

Findings, then the fixes get built

Audit + 2-6 weeks

Best for: You want the issues found and fixed by the same person who diagnosed them

  • Everything in the One-Time Audit
  • Implementation of the prioritized fixes
  • Verification that each fix actually resolved the issue
  • A short report showing before/after for the metrics that matter

Ongoing Monitoring

Catch regressions before they cost you

Monthly retainer

Best for: A site or store that changes often and needs regular checks, not a one-time snapshot

  • Recurring audit passes on a set cadence
  • Alerting when a key metric regresses
  • Priority access for fix implementation when something breaks
  • A running log of what changed and why it mattered
How it works

Four steps, no mystery.

01

Quick scoping call

A short call (or async over WhatsApp) to understand what you're working with and what "done" actually looks like for you.

02

Fixed scope, no surprises

A clear written plan of what's included and how long it takes, before any work starts.

03

The actual work

Progress you can see, not a black box. You get updates as milestones land, not just a status report at the end.

04

Handover

Everything documented and handed over cleanly, with a walkthrough so your team isn't stuck waiting on me for routine changes.

Questions

Frequently asked.

A mix of field data (Chrome UX Report), lab testing under throttled mobile conditions, and manual waterfall analysis — automated scores alone miss the "why," which is the part that actually matters for fixing it.

Start here

Tell me what you're dealing with.

Send a message and get a real reply within 24 hours, not an automated sequence.

Prefer email? info@hasnain.io

Or WhatsApp directly, same link as above