Albert Peschar

Hi @gabikod,

Please read the first two entries of the FAQ, if you haven’t yet.

Generally, you should not have two plugins do the same thing, eg, both optimizing CSS, JS and images (which PhastPress already does). And if you do have two plugins that can do the same thing, you should disable this functionality in one of them.

I advise using PhastPress in combination with a caching plugin. I have no experience with LiteSpeed, but if it does caching or mostly caching, it should be compatible.

–Albert

Hi @kw11,

Unless you share a URL of an indexed resource, I cannot check.

However, PhastPress sends JSON as text/plain responses because not all server configurations automatically compress application/json responses. It could be that Google automatically indexes these.

In the latest release, I’ve added a header X-Robots-Tag: none to these JSON responses to avoid any indexing or link following from Google. This should fix the issue.

–Albert

Hi @vdn-staff,

Thanks for letting me know. I’ve tracked down an issue that may have caused this. If that was it, it should be fixed now, but I’ll keep an eye on it.

–Albert

At the moment you should not be experiencing this issue anymore. If you are, it is likely a network problem.

Lately I’ve received repeated complaints of this kind but I cannot correlate this with any reported connectivity or load problems from my own server monitoring.

I’ve added additional monitoring to hopefully support future reports of the same problem.

–Albert

Hi @no2s13,

Are you still experiencing this issue?

–Albert

Hi @scontomio,

Not yet. Probably we can drop support for IE altogether. I’ll add it to my backlog, but I cannot promise you it will be added soon.

–Albert

Hi @snipsnip,

That would be great. It’s on my wishlist to work on when I have time. Right now, I don’t expect it to be soon.

–Albert

The host is wrong. PDO/SQLite3 is missing. There are no issues with PHP 8.

Try creating a file phpinfo.php with these contents:

<?php phpinfo();

Or install this plugin: https://www.ads-software.com/plugins/phpinfo-wp/

You should be able to verify whether the SQLite3 extension for PDO is installed. (Just search on the page for pdo_sqlite.)

Hi @snipsnip,

Regarding WebP:

You seem to be using Cloudflare for your site. Unfortunately, Cloudflare [does not support Vary: Accept](https://serverfault.com/questions/780882/impossible-to-serve-webp-images-using-cloudflare), so sending WebP via Cloudflare can cause browsers that don’t support WebP to download the wrong image type. You can try using [Cloudflare Polish](https://support.cloudflare.com/hc/en-us/articles/360000607372-Using-Cloudflare-Polish-to-compress-images) instead.

I’m considering changing the logic to only serve WebP images. But this will break images on [old browsers](https://caniuse.com/webp) so I’m not sure yet.

Regarding CSS:

You don’t seem to have PhastPress enabled right now. Therefore I can’t check what’s happening. If you re-enable PhastPress or set up a testing copy of your site with PhastPress enabled, I can investigate further.

–Albert

Hi @scontomio,

40-50 ms is decent. You won’t get it much lower than that I’m afraid. It should save more than that in reduction of time to first paint.

The most intensive optimization is “Optimize CSS”. But that one is also one of the most effective ones, so I wouldn’t recommend disabling it.

With full-page caching enabled, the PhastPress optimizations will only delay the first render. I usually use WP Super Cache, but the other popular plugins mostly also work fine. See the FAQ.

–Albert

Hi @vdn-staff,

If you’re still seeing this error it’s most likely a firewalling issue on your site. The image optimization server is definitely online.

–Albert

Thanks for your follow up.

The real solution is probably to fix the root cause that is outputting stuff before the <!doctype. There’s probably some mistake in the plugin code.

Using ob_get_clean affects PhastPress’ output buffer apparently. The disabling might not work because it’s done too late (after PhastPress has already started).

Anyway, instead of using ob_get_clean to end the existing output buffer, use ob_start as a filter itself:

<?php

ob_start(function (string $output): string {
  return preg_replace('~^.*(?=<!doctype)~is', '', $output);
});

This code should run before the problematic plugin. You can ensure this by placing it in a file in wp-content/mu-plugins (you may need to create this folder). Eg wp-content/mu-plugins/kill-output-before-doctype.php.

• This reply was modified 2 years, 8 months ago by Albert Peschar.

Yeah, php -i will give you information about the PHP CLI (command line interface), not what’s installed in your web server. It can be completely different.

Next time, you can create a file phpinfo.php with these contents:

<?php
phpinfo();

When you visit this file on your webserver you can see the PHP config that is in use. This plugin should do the same: https://www.ads-software.com/plugins/phpinfo-wp/

Hi @alainmelsens,

In short: opcache speeds up the execution of PHP scripts, PhastPress changes what is sent to the browser to make it faster to load.

For a list of PhastPress features, see the plugin description.

There is no reason not to use opcache (it should always be enabled). Whether PhastPress is useful to you, is something you’ll have to investigate by testing it.

–Albert