LiteSpeed processes block the page after a post is published

Procesos de LiteSpeed bloquean la página después de publicar un post

I have been dealing with a problem for some time now for which I have not yet found a definitive solution. The issue is that, right after publishing a post, the CPU consumption skyrockets as well as the number of processes leaving the site practically inaccessible for long periods of time. This is

Function for adding an IndexNow link to your list of entries

IndexNow

IndexNow is a free and open source protocol under an Attribution-ShareAlike Creative Commons licence that allows you to notify search engines that you have just published something new, that a piece of content has been modified and updated or that a URL has been removed by sending a ping to the search engines

How to split long WordPress posts into pages without affecting SEO

Cómo dividir entradas largas de WordPress en páginas sin afectar al SEO

When I started blogging, I didn't follow any SEO or optimisation rules or anything else. I just posted and that was it. This caused me to accumulate thousands of unoptimised images and hundreds of long, very long articles. Then I continued to publish other long articles that I optimised just enough. So, to

AVIF, the inevitable rise

AVIF. Formato de imagen nueva generación

In the recent update of the LiteSpeed Cache for WordPress (LSCWP) plugin to version 7.0, the AVIF format has been added to its image optimisation option. Since 2023, WordPress version 6.5 allows uploading and serving images in AVIF format and since then I've been using them in longer posts and even manually replacing