So I presume you are taking the render delay issue from Lighthouse's advice?
Lighthouse tries to show what might be the issue under certain circumstances, but that may not reflect the actual issue your real users are experiencing, depending on whether they are on similar conditions (network, CPU) to the Lighthouse run. Luckily, you have some CrUX field data which is much more interesting:
This shows you have a TTFB of 2.2 seconds, and FCP of 3 seconds, and then the LCP also happens at 3 seconds (so LCP is not any slower than the first contentful paint).
This tells me that TTFB is your problem, not the render delay, and the Lighthouse audit is not a good explanation here.
With a TTFB of 2.2 seconds you're definitely going to struggle to get LCP under 2.5 seconds and the fact you get 3 seconds (0.8 seconds after the HTML starts arriving) is actually pretty impressive!
- You are using a CDN (keycdn) for your resources, but not your HTML document itself. This has a doubel impact in that i) you're HTML is not benefiting from being globally distributed and ii) it also means the HTML document has to make an extra connection to the keycdn origin before it can download the resources:=. You can see the impact of this delay in the following waterfall diagram, where there are large connection setup requests between 1.0 and 1.5 seconds:
- Your HTML has a cache-control header of max-age=0, meaning it should never be cached.
That means every single request always has to go all the way back to your server every single time. Adding even a short caching time (unless your content does update that much?) and using a CDN for the HTML itself would likely go a long way to solving your issues.
However, your server seems reasonably fast from the above test, so there may be other issues depending how you get traffic to your site. If a large proportion of traffic involves redirects (e.g. from ads, or from newsletter links) then that could also cause TTFB delays. It is worth looking at your traffic sources and seeing if that is the case, and if it is possible to r
educe any of those redirects (e.g. if you have multiple link shorteners in use, or are linking to a http site, that then just needs to redirect to https).
Thanks,
Barry