optimalisatie

Hi cswilsn2k,

The proxy URL in the error log is a static file URL. If it redirects then the cause is likely to be found in the web server configuration or potentially a (security) plugin that modifies .htaccess (Mod Rewrite).

Regarding Font Awesome, when a CSS file contains relative links (to fonts or images) then they would break when the CSS is loaded from the proxy location. To solve the issue it would be possible to place the Font Awesome CSS locally and convert the relative paths to absolute paths within the WordPress installation or on a custom CDN.

We usually place Font Awesome in a conditional Critical CSS entry with the option “Prepend to any” with just the specific fonts that are used. You could save up to 80% of the CSS that way.

The option Prepend to any causes the font CSS to be included before other Critical CSS on a page so that rendering of the critical CSS that uses the fonts is smooth.

Hi jfireman,

Thank you for reporting the issue!

The used method for checking if the request is for the login page is the following:

/**
 * Register or login page
 */
if (isset($GLOBALS['pagenow']) && in_array($GLOBALS['pagenow'], array('wp-login.php', 'wp-register.php'))) {
    return false;
}

It is the official method.

If you use a custom solution, it would be possible to manually disable the plugin using the following code:

define('DONOTABTF', true);

Hi Roycegracie,

The plugin is not able to modify the contents of an iframe, however, it does provide a lazy script loading feature that makes it possible to hide scripts and iframes that are located below the fold.

The option is located on the Javascript Optimization tab (Lazy Load Scripts).

For example, to load a YouTube video when the user scrolls it in view, you could use the following code.

<div data-lazy-widget><!–
<iframe allowfullscreen=”” frameborder=”0″ height=”315″ src=”https://www.youtube.com/embed/UkWd0azv3fQ#t=2m30s&#8221; width=”420″></iframe>
–></div>

If you need to load a video in the above the fold view then the only option is to optimize the video itself. For example, if you just need to display the preview image until the user clicks the play button, you could convert the iframe to a image that replaces itself with the iframe embed code when the user clicks on it. There may be other solutions.

Hi 3dseo,

The custom proxy URL option is intended for experts. It would enable to use a custom proxy system to serve resources, for example a CDN. For most users it could be left default (blank). WordPress (PHP) will then proxy resources.

To improve the performance of the proxy it is possible to specifically pre-configure the resources that will be proxied. The resources will then be loaded directly from the cache location and potentially via a CDN so that the performance is the same as for any ‘static resource’.

It appears that the latest update v2.8.x has resolved the issue. The 2.8.x version has a client source code that has been compressed and optimized using Google Closure Compiler. The HTML5 script loader did not change.

Hi Paul,

The JSON editor warnings indicate that the JSON format is invalid. It would be best to start with a boilerplate. You could select Code mode and copy and paste an example manifest.json.

More information can be found on the following address:

https://developers.google.com/web/fundamentals/engage-and-retain/web-app-manifest/

Hi rbennett,

Please let us know if the issue has been resolved.

Hi psabbatella,

It would be best to do the following:

1) login via FTP
2) rename the directory /plugins/above-the-fold-optimization/ to /plugins/above-the-fold-optimization-disabled/
3) login to WordPress
4) rename the plugin back to /plugins/above-the-fold-optimization/

The plugin will then be specifically disabled and it would be possible to upgrade the plugin with the fix for PHP 5.3.

The issue is unrelated to access of WordPress.

Are you currently unable to login? If so, the ABTF plugin is not likely to be a possible cause since you were already able to access the PWA tab.

Hi psabbatella,

Our apologies. We intend to support PHP 5.3. Besides this relative small issue the plugin is compatible with older PHP versions.

The issue occurred when you tried to create the manifest.json file in the admin panel.

The issue has been resolved in v2.8.13.

Hi rbennett,

The error is related to CometCache. When upgrading the Above The Fold Optimization plugin the plugin will clear page related caches.

The following method is called for CometCache:

$GLOBALS['comet_cache']->clearCache();

It appears that the CometCache plugin may be incorrectly configured which is causing the error. This could be the cause of the issue on the frontend.

Did you check the console to see if there was a javascript error visible?

Thanks a lot for reporting the issue and for providing access to the development environment!

We discovered a bug when using custom WebFontConfig in Google Web Font Optimization settings. The bug has been fixed in v2.8.10.

Please let us know if it resolves the issue.

We discovered a bug when using custom WebFontConfig in Google Web Font Optimization settings. The bug has been fixed in v2.8.10.

Please let us know if it resolves the issue.

Hi rbennett,

Thank you for your feedback. We will do our best to resolve the issue a.s.a.p.

Is there a javascript error visible in the console?

Could the issue be related to a (custom) page or javascript cache?

Could you try to load the website in a incognito screen to test if the issue may be related to browser cache?