I received an email that my iPhone 16e will arrive tomorrow.I am looking forward to it now.

Yesterday I had trouble starting to write.Today I can start without problems.

iPhone 16e arrives tomorrow, February 28

I received an email from Apple.

Shipped today the 27th and my iPhone 16e is now in Ariake.It will be delivered tomorrow morning since it is in the Kanto region and close to Tokyo.Since it was handled by Yamato Transport, I was able to change the delivery to a morning delivery; it will be in my hands by the morning of the 28th.I will set it up during the weekend as I had just taken a vacation.

When it arrives, the first step is to apply the protective film.I’m not very good at this.It inevitably leaves air bubbles, or slightly shifts slightly.This time I got a glass film with a guide, so I expect that to work.

I will not migrate from my current iPhone7 plus, but will carefully select and install the apps I have included based on the need for them.There are quite a few apps that I don’t use.I will not be migrating my photos either.I will back them up to the NAS at the end and then let the rest of the photos taken with the iPhone 16e be backed up.

Initial setup is one of the most enjoyable times for me, not only for iPhone but for PC as well.

Migration from Google reCAPTCHA to Cloudflare Turnstile

We have completely migrated to Cloudflare Turnstile and have disabled Google reCAPTCHA which was used in Contact Form 7.

We have confirmed that the contact form, comments, and login are working.

Google reCAPTCHA doesn’t work very well with LiteSpeed Cache, unless you exclude JavaScript from the optimization.

So far, Cloudflare Turnstile is working without doing anything special on the LiteSpeed Cache side.

We will see what happens when the UCSS generation starts, and the month changes exactly on the weekend at the end of this month as well, so we will be on the lookout for display disruptions, etc.

LiteSpeed Cache and Cloudflare CDNs

Since the two functions overlap in the Cache section, we are pondering how to use them differently.

LiteSpeed Cache Changes

Review LiteSpeed Cache settings in conjunction with using Cloudflare CDN.

LiteSpeed Cache for image, HTML, JavaScript, and CSS optimization

Image optimization (WebP), HTML optimization (minify), JavaScript and CSS optimization are left to LiteSpeed Cache.However, I have made changes to avoid extreme optimization.

Guest mode and guest optimization changed to OFF

Specifically, Guest Mode and Guest Optimization were turned off.These two items work to improve PageSpeed Insights scores, but have significant side effects.If anything, they are enabled to improve scores.It’s a lot to handle, and it adds to the JavaScript and CSS exclusions.

We expect Cloudflare CDN to be effective.

UCSS continues to be used

We will continue to use UCSS for CSS optimization, as we know that CCSS has limitations as we have tried it on other sites. (Japanese site)

It is more effective to remove unnecessary CSS than to load it in parallel.

However, if the side effects are checked and there are too many CSS to be excluded to avoid, we may consider using CCSS.

Cache remains active

LiteSpeed Cache cache should be enabled.

The mobile cache was left in place.Some believe that a mobile-specific cache is unnecessary in a responsive environment.Personally, I believe at this point that it is better to keep the mobile cache because the layout is very different.

In extreme cases, the Cache function of LiteSpeed Cache may be turned off.As a test, I turned off all cache functions, and an alarm was displayed.It seems that this type of use is not intended.

I will try using it a little more and if it does not benefit from the Cache feature of LiteSpeed Cache, I will try running it with everything off.

Cloudflare CDN side configuration

No changes are made to the settings on the Cloudflare CDN side.

LiteSpeed Cache has been configured to use Cloudflare CDN.Switching to development mode (bypass) and clearing the Cloudflare CDN cache can be done in LiteSpeed Cache.

We will see how it goes for about a month in this state first.

Musubi

As if yesterday’s problems did not exist, today’s article entry could be finished smoothly.It started at 12:21 and ended at 12:55.