Web performance · Core Web Vitals · WordPress · Caching
FassihFayyaz.com: 80 → 100 Desktop Without Changing Hosts
The affiliate site that preceded this portfolio went from 80 to 100 desktop PageSpeed and 42 to 74 on mobile, with Pingdom load time cut from 7.87s to 2.10s — on the same shared hosting.
Results at a glance
- Desktop PageSpeed
- 80 → 100
- Mobile PageSpeed
- 42 → 74
- Pingdom load
- 7.87s → 2.10s
- Requests
- 38 → 33
The problem
The old FassihFayyaz.com was an affiliate publishing site on Namecheap shared hosting: a Kadence build, content published continuously, no CDN and no caching layer. It worked, but it was slow in the way shared-hosting WordPress usually is.
PageSpeed showed 80 on desktop and 42 on mobile. Pingdom measured 7.87 seconds load time with 38 requests and a 943KB page. On mobile, the reader waited through a first contentful paint of several seconds before seeing anything.
Why we decided to solve it
The site earned from affiliate clicks, which meant the mobile reader was the customer. A seven-second load on mobile is not a design problem, it is a lost reader, and the content investment behind each article only pays if people reach the comparison table.
The constraint I set was deliberate: fix it on the hosting already paid for. Moving to a better server is the easy answer, and it teaches you nothing about the build.
How we did it
Caching and delivery first
Page caching and asset optimisation did most of the initial work: the server stopped rebuilding the same page on every request, and static assets were served compressed with sensible cache headers.
Then the images
The page was 943KB, with images well above the size they rendered at. Images were resized to their display dimensions, compressed and converted to a modern format, with everything below the fold lazy-loaded. That is the single largest contributor to the load-time drop.
Strip what the theme loaded but never used
Fonts were reduced to the weights in use, unused CSS and scripts from the theme and plugins were dequeued, and render-blocking assets were deferred. Requests fell from 38 to 33 and the page to 928KB.
Verify with independent tools
PageSpeed Insights on both profiles, plus Pingdom from Frankfurt, so the improvement was not one tool’s opinion of the same page.
The result
Desktop PageSpeed moved from 80 to 100. Mobile moved from 42 to 74 — a large gain, and still short of desktop, because a heavy mobile Lighthouse profile is unforgiving on shared hosting with no CDN.
Pingdom load time fell from 7.87s to 2.10s, a reduction of about 73%, with requests down from 38 to 33.
The site has since been retired and the domain now runs this portfolio, so these are the April 2024 captures rather than a current score.
Evidence
What the work looked like.
Captures from the engagement. Images marked as redacted have sensitive business data blurred before publication.
Contact
Want to talk through a project like this?
I am open to remote SEO, web design and performance roles. If you need more detail on a specific project, ask — I will share what the client allows.
- [email protected]
- Phone
- +92 322 6189669
- Location
- Multan, Pakistan · Remote
- Status
- Open to remote roles