Sumeet Sarna

A near-perfect Lighthouse score and what actually moved it

18 Jun 2026performancewebLighthouseNext.js
Listen0:00 / 0:00

I ran sumeetsarna.com through PageSpeed Insights. Performance came back 99 on mobile and 100 on desktop, with accessibility, best practices and SEO all at 100. None of that came from a plugin. It came from a handful of boring choices.

PageSpeed Insights scorecard for sumeetsarna.com: 99 mobile, 100 desktop, 100 accessibility, best practices and SEO

Fonts that don't cause layout shift

I load fonts with next/font, which serves them from my own domain and reserves their space before they arrive. No flash, no jump. Layout shift is one of the metrics the score weighs and fonts are the most common cause of a bad one.

Send less JavaScript

Most of the site renders on the server and arrives as plain HTML. The interactive parts, the menu, the theme toggle and the search are small and load only where they are needed. Less JavaScript to download and run means a faster first paint and almost no blocking time.

Few images, and the ones I have are sized

The site is mostly text. Where there is an image, it has a fixed width and height so nothing reflows when it loads. Unsized images are a common cause of both slow loads and layout shift.

The other three 100s are just hygiene

Accessibility, best practices and SEO are not about speed. They come from semantic HTML, enough colour contrast, alt text on images, a title and description on every page and a sitemap. The tool checks for these directly. None of it is hard. It just has to be done.

Measure, don't guess

The score is not the point. The point is that PageSpeed Insights tells you exactly what to fix and how much each item is worth. Run it on your own site. It is free, it takes a minute and it turns a vague feeling that the site is slow into a list you can work through.