@kev and fully loading your homepage takes less than 1 second in both the UK (https://www.webpagetest.org/result/220905_AiDc0Y_DXH/) and Canada (https://www.webpagetest.org/result/220905_AiDcXS_DXJ/).
While Australia does take a little bit longer (1.5 seconds - https://www.webpagetest.org/result/220905_AiDcTC_DXW/), it would be hard to make it load very quickly.
Congrats! I think you need to do a full write-up on what you've all done.
@g thanks. I might do a full write up at some point. It would be a looooong post though as I’d like to talk about what led me to each step in the process.
@antijingoist I think it’s more because of admins who don’t actually know what they’re doing, so instead of adding a bit of PHP to add some functionality, they add a plugin. And another. And another. And another.
All of a sudden they’re loading tonnes of CSS and JS on the front end, and their WP backend is like a sieve.
@kev Why inline things like CSS and your logo image which will be repeated on each page? Maybe you've maximized request speed for a single page, but subsequent page request responses will be larger than they need to be since clients will be re-downloading stuff they could have just retrieved from their cache. Is there a reason for that?
@Albright the amount of css is negligible in terms of the total page size. Removing unused CSS and reducing the number of requests made (thus removing render blocking requests) is a far superior solution (in my opinion) than having to rely on visitors local cache.
I defined favicon inline so that I can use an emoji. This helps avoiding another request for a single KB png image.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.