optimalisatie

I am closing this support ticket. If the problem persists in the latest version, feel free to reopen it.

Hi masoudsafi,

Thank you for taking the time to report the problem!

The issue has been resolved in v2.5.11.

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi martychc23,

Thank you for your suggestion!

The feature is not available but you can easily add it using a WordPress hook in /themes/THEMENAME/functions.php:

add_action( 'init', 'disable_abtf' );
function disable_abtf() {
    // DISABLE ABOVE THE FOLD FOR LOGGED IN ADMIN USERS
    if (current_user_can('administrator')) {
        define('DONOTABTF',true);
    }
}

The method for any logged in user is is_user_logged_in().

[ Signature moderated ]

• This reply was modified 8 years, 4 months ago by optimalisatie.
• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi mmdijkman!

Thanks again for the suggestion! The urls will be updated in v2.5.11 (aprox 1-2 weeks).

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi mmdijkman,

Thanks a lot for reporting the problem!

The bug has been fixed in v2.5.10.

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi mmdijkman,

Thanks a lot for taking the time to report the problem!

I am not sure what could have caused the error. I did find a bug in the W3 Total Cache module that has been fixed in v2.5.10, but it did not cause the PHP error you have experienced.

I’ve tested the W3 Total Cache plugin extensively and I could not find a possible explanation for the PHP error.

Are you using other plugins that use an output buffer?

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi mmdijkman!

The modification has been added in v2.5.8.

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi!

I’ve discovered a new tool to download Google fonts:

Google Webfonts Helper
https://google-webfonts-helper.herokuapp.com/fonts/

The plugin has been updated (v2.5.6) to be able to remove Google fonts when placing them locally.

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi dave8441!

Thank you for reporting the problem.

A change in the new version is to exclude fonts.googleapis.com by default. This may have resulted in the PageSpeed warning for render-blocking CSS in above-the-fold content. Regrettably, it is required to exclude the resource as it serves content based on the client (e.g. different fonts and CSS on a mobile device).

An option to solve the issue is to fine tune the Web Font Loader configuration (CSS tab > Web Font Optimization). For example, instead of including webfont.js inline, the issue may be resolved by loading it async.

There is also an option to download the Google fonts and serve them from the local server. This will solve the issue and also provide the fastest font rendering during page navigation (to prevent a font flicker effect).

I’ve made a tool in the past to download Google fonts using Grunt.js:

https://github.com/optimalisatie/grunt-goog-webfont-dl

It is a few years old. There may be other tools to do it.

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi mmdijkman,

Thank you for reporting the problem!

I have not seen that problem before. My first idea that it may be caused by an invalid <base href="" /> tag in the HTML.

The relative URL conversion takes place using a simple javascript method (an <a> element is created and the href is set). It is not a possible cause.

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi micheleficara,

Thank you for reporting the problem!

The plugin is tested with WordPress multisite and it should work well.

Have you checked the server logs and is an exact error message available?

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi oshber,

The problem you describe appears to be related to CSS.

Have you verified (in the browser console) that all CSS files are loaded?

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi warriorx51,

Thank you for reporting the bug!

The problem has been resolved in v2.5.4.

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi RebellionNT1,

The plugin has been disabled for AMP pages in v2.5.4.

[ Signature moderated ]

• This reply was modified 8 years, 4 months ago by optimalisatie.
• This reply was modified 8 years, 2 months ago by Jan Dembowski.

Hi joacarlos,

The next version of the plugin will have improved performance. It will be released in aprox. 1-2 weeks.

Regarding the PageSpeed 100 Score at GT Metrix. It may be the same result as when using the Google PageSpeed API and the Chrome Console PageSpeed Insights plugin.

https://chrome.google.com/webstore/detail/pagespeed-insights-with-p/lanlbpjbalfkflkhegagflkgcfklnbnh

It may be that the official PageSpeed test evolves quickly and / or is more strict than the API. The API may be intended for website analysis by providing a more average score, while the online PageSpeed test is intended to provide an exact quality score.

In the details of the GT Metrix analysis there are several aspects with a less than 100 score, e.g. Leverage browser caching: 96. Perhaps the online tests shows the lowest value (weakest link based score).

[ Signature moderated ]

• This reply was modified 8 years, 2 months ago by Jan Dembowski.