Matt

Yeah, the new icon picker would be ideal there.

From a Cloud perspective, our CDN optimises the images so it's not really a concern. We don't really use many images now, but those listed are generally around 1kb as-is.

Use your "Find My" to locate your laptop, then open your laptop. Kidding aside, we will continue to build on this basic implementation.

Yes, at worst we can upgrade your site to the latest 5 beta after purchase.

You may notice that Beta 9.1 is now available. We no longer talk about Beta 9.0.

Oh and from Beta 10 onwards, those on PHP 8.3.2 or newer can upgrade through the ACP. We fixed that, but you need the fix before the fix is.. fixed.

There should be an update out in about 10 minutes or so.

Changed Long ID to 5000039

Yeah, I can reproduce. I'll get a patch out.

Beta 9 is here, and there's a little addition to the editor! Along with the usual weekly round up of bug fixes, we've added a basic implementation of tables in the editor. We're testing this out to see how it goes before we build on it, but you should be able to add rows and columns and do all the usual table-y things. Let us know what you think!

Changed Current Release to No

I love that!

If you can update your client area details with your Beta 5 installation, we can take a look.

That looks amazing! What a difference from v4.

Are you able to look at the server's error.log?

Also, as far as I know, the FCP timer starts as soon as the browser receives the content, the timer doesn't start when the test starts so a slow return from the server will not affect FCP. In other words, if it takes 10 seconds for the server to generate the page and send to the browser, the FCP time will not be 10 seconds + browser render time.

That will cache the HTML, it does not reduce the size of the HTML so it should not have any affect on FCP times.

Yeah, I'm not sure why it's flagging an image load as blocking. I'm not sure what we can do about that.

I think the issues with RocketLoader remain.

We wish. I think it works out slightly more expensive as we need to pay bandwidth from AWS to Cloudflare but it offers better protection and that ultimately is our goal. It should scrub more bot traffic which means less hits origin but overall, it won't really give us any savings.

If you scroll down, you can check what is causing the delay to FCP/LCP.

CloudFlare have worked really hard to build their business to become one of the best CDN/Firewalls on the market with excellent bot detection and attack mitigation. We always want the best for our Cloud Platform and we're happy that this means using CloudFlare.