Apropos Tech Solutions Corp. Blog

Category: plugins

  • Web: is my site on a LiteSpeed server? (Finding out from Firefox)

    Being on a LiteSpeed server, you can possibly use the LiteSpeed Cache.

    The following is by my understanding.

    Once a site gets busy, for instance a WordPress site, a cache can make the difference between the site being slow versus normal.

    On my oldest WordPress site, which went up in 2012, I have always used LiteSpeed Cache, except for a couple of interruptions during updates. When I had to run the site without it, I really noticed how much slower it loaded. On that site, LiteSpeed Cache is the only plugin I use. (See my post from June 5, 2026 for some background thoughts about plugins.)

    So, LiteSpeed Cache is a plugin that I like. However, as I understand, in order to use the LiteSpeed cache, one needs to be hosted on a LiteSpeed server. (Perhaps that’s a slight oversimplification, but likely good enough for a starter’s perspective.) How does one discover if they are?

    Here’s how I did so on Firefox:

    1. On a page from the site, right-click on a non-active part. From the drop-down, click Inspect.
    2. On the new pane that appears, find Network and click on it.
    3. Reload the page. A bunch of resources will be listed as they load.
    4. Click on any of the resources. A new pane will appear; on it, find Headers and click it.
    5. Underneath the Headers title, find Response Headers and scroll down. An entry like server: LiteSpeed indicates that, indeed, the site is on a LiteSpeed server.

    There are many potential directions to follow from this post. One motivation for finding if one’s on the LiteSpeed server is to discover whether using the LiteSpeed Cache is a possibility, perhaps even as a plugin if the site is WordPress.

    For follow-up I intend to mention corresponding directions relevant to Chrome and related browsers.

    Source:

    docs.litespeedtech.com

    w3.org

    -JS

  • WordPress: Plugins: another let-down

    WordPress: Plugins, continued…

    The following is my take.

    I start about WordPress plugins in my post from June 2, 2026. I typically run a cache one, and sometimes that’s it.

    I thought about doing a post today about a plugin to make backups. Backups are important to safeguard content from errors, malfunctions, etc. Before doing any manual update, making a backup is likely a good idea. That’s what I do, anyway.

    So, I had a plugin installed which I was going to use to do a backup, then report about it.

    The plugin crashed: it just remained stuck at 0 percent completion. When I clicked the “Stop” button in its menu, I got a message back saying the process couldn’t be stopped.

    I logged into the server and stopped the plugin from there. Next, I deactivated, then deleted the plugin.

    I never keep plugins around that don’t stop when I click “Stop.”

    A plugin isn’t needed to make a backup of a WordPress site; a backup can be created manually. However, some plugins, assuming they work, might make it more convenient.

    Not in this case, apparently:)

    -JS