Next JS Website Core Web Vitals Improvements

[Sunil Joshi]

Hi,

I like to improve our website's core web vitals. Can someone help me with some expert inputs to what should I do first?

Here is my website link - https://crystaivf.com/

Thanks & Regards,

Sunil Joshi

[Robert Lozano]

I have created a personal playbook on things you can do to improve Core Web Vitals, but it is pretty lengthy, requires a lot of engineering hours. In some areas, it helped us to cut performance in half. 

-Robert

From: chrome-u...@chromium.org <chrome-u...@chromium.org> on behalf of Sunil Joshi <sunil...@crystaivf.com>
Date: Wednesday, January 7, 2026 at 3:14 AM
To: Chrome UX Report (Discussions) <chrome-u...@chromium.org>
Subject: [Marketing Mail] [CrUX Discuss] Next JS Website Core Web Vitals Improvements

EXTERNAL EMAIL

--
You received this message because you are subscribed to the Google Groups "Chrome UX Report (Discussions)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-ux-repo...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/4775ff4b-9631-4415-b158-39fd17292b79n%40chromium.org.

[❄ Johannes Henkel]

https://pagespeed.web.dev/analysis/https-crystaivf-com/ei3fisn9fl?form_factor=mobile

https://cruxvis.withgoogle.com/#/?view=cwvsummary&url=https%3A%2F%2Fcrystaivf.com%2F&identifier=origin&device=PHONE&periodStart=0&periodEnd=-1&display=p75s

Looks like most visits to the site come from phones, and the loading performance (LCP) is poor.

The PageSpeed Insights links gives some advice, e.g. looks that there's quite a bit of javascript on the mainthread and quite a few resources needed to render the page; and the lcp image may be experiencing a resource load delay - but I'm probably not the best person as to what to prioritize to work on, sorry.

For subjective experience, I opened this on my personal phone (Pixel 6a, wifi / cable internet) and it loaded ok; I didn't feel it was a terrible delay. It seems it loads quite a lot of content which then requires both vertical and horizontal scrolling to explore, in addition to the menu in the upper right (which links to even more content). Whether that's a good design choice I don't know - it could be good because a site visitor can read and see a lot of things without an additional navigation, but I would also speculate that some of the performance implications or difficulties to make the initial load fast come from that? I guess I'm wondering how much of the loading activity and Javascript main thread execution has to do with what's in the initial viewport (which looks nice on my phone) vs with what's going to need to be there if / once I scroll. Please don't overinterpret, I figured I'd just share my (maybe a bit naive) observations, if someone has expert thoughts on the site that's probably better. Good wishes.

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/SA6PR14MB7700AAB771DF61F9BFCFCA7FC684A%40SA6PR14MB7700.namprd14.prod.outlook.com.

[Robert Lozano]

Things to take into consideration:

• CDN for public caching
• HTTP/3 (at Edge)
• IPv6 Dualstack (at Edge)
• Persistent Connections for TCP reuse
• Compression FROM origin to CDN, NOT on the fly
• Image Management (compression and modern file formats)
• Early Hints
• Speculation Rules API
• ECC SSL Certificates
• Early Data 0-RTT

Robert

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/CAO3HAxwAGQaPM0CWXQWQGtyNUbstawFU2LeRTxMxxxx2zDeNFQ%40mail.gmail.com.

[Joan Leon]

As for the Core Web Vital LCP metric, the biggest problem is TTFB

----

Joan León
Google Developer Expert in Web Technologies
Cloudinary Ambassador
@nucliweb

📖 joanleon.dev

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/CAO3HAxwAGQaPM0CWXQWQGtyNUbstawFU2LeRTxMxxxx2zDeNFQ%40mail.gmail.com.