Quick boosting tips?

I had a look at the site and a pagespeed insights report (m:77,d:96);

1. I would not inline all CSS, as that makes the HTML a lot more bulky. Although the CSS does not have to be downloaded and thus it is not render-blocking, have such a big blob of CSS results in some performance loss when compared to the more lean approach of using above the fold/ critical CSS.

2. Additionally the LCP image is slower then it should be because it is a CSS background image which is discovered relatively late by browsers and the download of which will have a low-ish priority. The better approach is having the image in an <img tag as that is discovered sooner and (if I remember correctly) loads with a somewhat higher priority. Alternatively you can try preloading the image by going to the “edit” view of the homepage and in the “autoptimize this page” metabox adding the full URL to the image to the “LCP image preload” field and saving the page.

hope this helps,
frank

OK. It seems like the first thing might have helped a bit. About the second one, I can’t find this “autoptimize this page” metabox?. How do I find this please?

assuming you have the “Enable configuration per post/ page?” option near the bottom of Settings -> Autoptimize -> “JS, CSS & HTML” on, you should be able to see that metabox on the edit page of the page/ post in question jmkennedy ?

Oh, ok. Found it know. Maybe it could say that it’s for Autoptimize. Could make it easier to find. ??

Didn’t seem to make much different for Pagespeed numbers though. Is there something else I can do with Autoptimize to improve LCP time?

well, the fact the main image is a CSS background image defined in wp-content/et-cache/2/et-core-unified-tb-205524-deferred-2.min.css has some important performance disadvantages.

the preload is a way to limit the impact somewhat, but:
1. Divi is loading that file late, so the image will always be discovered late by the browser -> no loading that file late OR also defining the background image in some inline CSS would help.
2. the image isn’t “seen” by AO and hence not loaded via the Shortpixel CDN so not optimized -> You could change the image URL in Divi Builder to point to the URL on shortpixel maybe?

the best solution however, would be not to load such an important image as CSS background image ??