Albert Peschar

Hi unalgu,

Thanks for trying out PhastPress.

It looks like you’re using a caching plugin. Could you empty the plugin cache and try again?

–Albert

P.S.: If you like PhastPress, I would really appreciate it if you left a review here.

Hi,

You probably added the code to your wp-content/themes/…/functions.php. Because the theme gets loaded after the plugin, the disabling code does not run on time.

You can create a “must-use plugin” with your code so that it runs before PhastPress is loaded. Simply put your code in a php file in wp-content/mu-plugins.

Create a file wp-content/mu-plugins/disable-phastpress.php with this content:

<?php

add_action('phastpress_disable', function ($status) {
  return $status || is_page(40144) || current_user_can('manage_options');
});

That should work for disabling PhastPress on page 40144 or for logged-in administrators.

–Albert

• This reply was modified 5 years, 12 months ago by Albert Peschar.

Hi yeknafar,

Where are you seeing this message? In the browser, perhaps in your hosting panel, or somewhere else?

On the first load, PhastPress does a lot of processing to optimize images, scripts and stylesheets. Afterwards, the load should be minimal.

–Albert

Hi Steve,

Have a look at this GTmetrix comparison report: https://gtmetrix.com/compare/yLk6T9qY/aWxZ5k17

1. “Fully Loaded Time” is 11.1 s with PhastPress vs 13.9 s without.
2. More importantly, if you have a look at the Filmstrip, you see that with PhastPress the site is visible at 6 s vs 11 s without.

So, although those load times are not as great as they could be, it’s working.

The main issue with your site is TTFB: response time (TTFB) for your site, when bypassing the cache is about 3.5 seconds with PhastPress disabled, and 6.4 seconds with PhastPress enabled. Under normal conditions, a WordPress site should not need more than 0.5 – 1.0 seconds, and PhastPress should not add more than 0.1 – 0.3 seconds to the TTFB.

That means your server is slow. As such, I would recommend upgrading to faster hosting, although it seems only the search is impacted, as all other pages are loading from the cache.

Otherwise, everything seems to work pretty well. I wouldn’t worry about the WP Rocket preloading errors (although if they contain any detailed info, feel free to post them)– all pages on your site seem to be loading from the cache.

–Albert

Hi Steve,

Thanks for giving PhastPress a try.

If you post your website URL, I can have a look and perhaps give you some pointers.

PhastPress accelerates the perceived load time of the site by asynchronously loading CSS and JavaScript files so the page can be rendered as quickly as possible. It might be that the GTmetrix measured page load time increases, although the time to first paint (ie, the time until you see the page appear) actually decreases. That should be obvious from your own experience. You can also use GTmetrix’s video feature to compare page load with and without PhastPress. (Tip: add ?phast=-phast to your page’s URL to disable PhastPress.)

By the way, I would recommend using WP Super Cache rather than other caching plug-ins. It’s simpler, and doesn’t have unnecessary features that PhastPress already provides. (See the FAQ.)

–Albert

Hey yeknafar,

Thanks for trying out PhastPress. I didn’t receive a notification email for your post here, as I usually do, so please excuse my late response.

Please share the URLs of the sites that you’re working on, and the testing tool that you’re using to get the score.

–Albert

Hi Toufic,

Thanks for your review!

Probably it is caused either by a rule in your .htaccess file, or by the configuration of the Varnish caching server.

To verify that the problem is with your hosting, and not with PhastPress or another plugin:

Please create a file called etag.php on your server with the following contents:

<?php header('ETag: "Hello"'); echo date('r'), "\n"; ?>

Check the URL in https://websniffer.cc and see if the ETag header is added correctly (example).

Please also post the URL to etag.php here.

If the ETag header is missing, then the problem is somewhere in your hosting configuration. In that case, you can post your .htaccess file to https://dpaste.com and share the link here. I will check if it’s possible to fix the issue there.

–Albert

Hi Viorel,

Thanks for making an effort to make your plugin compatible with PhastPress!

I’ve added the requested hook. It’s called phastpress_disable.

Since PhastPress is started during plugins_loaded, you must insert your hook as soon as your plugin’s PHP files are included, or using plugins_loaded with a priority lower than the default 10.

Good luck!

–Albert

Hi Toufic,

Thanks for trying out PhastPress.

Your hosting is using caching (with the Varnish caching server). This seems to cause the query string (the part of the URL after ?) to be ignored, so that URLs like this don’t work:

https://bronze.qa/wp-content/plugins/phastpress/phast.php/__p__.js?service=bundler&p=157911764&f=00uggcf%3N%2S%2Soebamr.dn%2Sjc-vapyhqrf%2Spff%2Sqvfg%2Soybpx-yvoenel%2Sfglyr-egy.zva.pff&v&g=o8p031145232r3rs

Unfortunately, this is required for PhastPress. You can ask your hosting provider to change their configuration so that query strings are not ignored, or disable the “Load scripts asynchronously” option in PhastPress.

The “Specify a cache validator” error is also due to your server configuration. PhastPress sends the required ETag header by default, but it is removed by your server before the response is sent to the browser.

–Albert

Hi wpsenior,

Thanks for trying out PhastPress.

In order to diagnose your issue, could you share the URL of the website where you are using PhastPress?

–Albert

It seems the PHP installation on your server is slow. Normally, when using WP Super Cache, pages should load in less than 200 ms.

Some possible reasons for slowness include:

• PHP is loaded via CGI instead of FastCGI or mod_php.
• You are using PHP 5. PHP 7 is much faster.
• The server is overloaded.
• The server hardware is ancient.

I suggest that you configure WP Super Cache to use “Expert” mode. This causes it to load files via .htaccess, without hitting PHP, and is thus much faster.

–Albert

Moderator, could you please remove the segment I tested your site […] is acceptable, as requested by the user, from my previous reply. Thank you.

Hi Jan,

Thank you for making me aware of this policy, I honestly did not know. I do agree this policy makes sense.

In future, I will help users by asking them only for a link to their site, so that I can investigate the problem without accessing their backend.

Hopefully, the delay in replies due to moderation will be minimal. In any case, you can be sure that this mistake will not be repeated.

I appreciate your vigilance and the work your doing for the WordPress community.

–Albert

Hi bheem,

Thanks for your message and for trying out PhastPress.

PhastPress does optimizations that take some processing on the server. This slows down the response time. On a fast server, the response time should not be increased by more than 150 ms (0.150 s).

You can reduce the response time (TTFB) by using a caching plugin such as WP Super Cache.

I tested your site studyread.com using this tool that measures the TTFB from many locations around the world and the TTFB of your site is acceptable.

Google uses a threshold of 200 ms. Without caching, this is difficult to achieve on WordPress, especially when you’re also using PhastPress. As long as the TTFB is below 400 ms, I would not worry about it.

Let me know if you have any additional questions. If you like PhastPress, I would really appreciate it if you left a review here.

–Albert

Hi suprim,

Great. WP Super Cache is recommended over WP Fastest Cache anyway, and there are no settings you have to disable in WP Super Cache. ??

If you like PhastPress, I would really appreciate it if you left a review here:
https://www.ads-software.com/support/plugin/phastpress/reviews/#new-post

–Albert