Plugin / Autoptimize criticalcss.com power-up

Download from WordPress

Frequently Asked Questions (FAQ)

Please sign up at https://criticalcss.com then go to CriticalCSS.com API Keys. This is a premium service, so be sure to read the additional pricing information! At the time of writing (4 May 2018) the price for using CriticalCSS.com is: £2/month for membership + £5/domain/month. This means the total cost will be £7/month if you use this plugin for one site. If you’re not sure yet; with the 30 day free trial, you have nothing to lose!
No; CriticalCSS.com needs the pages for which it has to generate critical css to be publicaly visible to work.
See https://criticalcss.com/general/terms-of-service/.
Critical CSS generation is based on a job-queue. For jobs to be added to the queue, your site should have requests and those requests should not be served by a page cache (because in that case WordPress and Autoptimize are not triggered). If you want to speed things up, you can temporarily disable your page cache and click around on your website yourself. Once a job is in the queue it can be executed and sent to criticalcss.com and at one of the next queue runs the critical CSS is retrieved and turned into a rule and it will be used for the next matching request (again for a page not in page cache).
When just installed the plugin will be more active, generating new jobs and for most of those jobs making calls to criticalcss.com. As rules are automatically generated that way, the number of jobs and the number of requests to criticalcss.com will go down significantly. Most importantly; as the bulk of the work is done asynchronously (by the cronned queue processing job), there is no negative impact on the performance of your site, so your visitors will not notice any slowdown.
Autoptimize CriticalCss.com power-up uses scheduled jobs to go over a queue with URL’s for which to fetch critical CSS. If there are many items in the queue, the process can take a couple of minutes to finish. If your hosts limits the time scheduled PHP processes can run, you can change the number of requests sent to criticalcss.com (the “request limit”) under the Advanced Options (default is 5).
As from AO CCSS 1.7 there is an (advanced) option you can activate to enforce PATH-based rules creation for pages so each page will end up with its own critical CSS.
Yes; create a manual rule (can be both path- and conditional-tag based) and enter none for critical CSS. If the rule matches, no critical CSS will be added and the full CSS will be inlined instead.
If all jobs remain in “N” then wordpress “cron job” that does the queue processing is not getting triggered. To verify you can install the “wp crontrol”-plugin and then under Tools -> Cron Events look for “ao_ccss_queue” and check the “next run” time/ date. If the “ao_ccss_queue” job is not there, you’ll have to de- and re-activate the “autoptimize critical css” plugin to have it re-register the queue-processing task. If the “ao_ccss_queue” job is there, but has a “next run” date in the past, there is an issue with your site/ hosters WordPress cron and you will have to contact your hoster. Some hosters’ info on the topic: WP Engine, BlueHost, HostGator and SiteGround.
Ensuring the CSS is not render-blocking through this plugin is a first important step to improve rendering performance, but to get a significant better first paint time, you’ll need to ensure you have no other render-blocking resources. Some tips: * for jQuery: try enabling the advanced “Defer jQuery and other non-aggregated JS-files?”-option (introduced in AO CCSS 1.12.0). This will also wrap inline JS that depends on jQuery in a function for it to be executed late as well. Test your site thoroughly after enabling this option and disable it if anything breaks! * for other JS: try to find an Autoptimize configuration where no JavaScript-files have to be excluded. * for excluded/ external JS: try to async/ defer using the Autopitmize Extra Async field or using the Async JavaScript plugin. * for Google Fonts: try the options on Autoptimize “Extra” tab. Remove Google Fonts is great but might be too aggressive for designers, “aggregate CSS & Preload” is a good alternative that is inline with what Autoptimize does with CSS. * for YouTube videos: try a plugin that lazyloads embedded videos (e.g. WP YouTube Lyte).
As of AO CCSS 1.13.0 the plugin binds itself to a domain to avoid unexpected requests from cloned sites. You can either deactivate and reactivate the plugin to reset the “bound domain” or you can pass false to the autoptimize_filter_ccss_bind_domain filter to disable the domain binding.

Ratings

4.8
18 reviews

Rating breakdown

Details Information

Version

1.17.1

First Released

06 May, 2018

Total Downloads

119,220

Wordpress Version

4.9 or higher

Tested up to:

5.2.4

Require PHP Version:

-

Tags

above-the-fold autoptimize Critical CSS render blocking css

Contributors

Frank Goossens Deny Dias

Languages

The plugin hasn't been transalated in any language other than English.

DIRECTORY DISCLAIMER

The information provided in this THEME/PLUGIN DIRECTORY is made available for information purposes only, and intended to serve as a resource to enable visitors to select a relevant theme or plugin. wpSocket gives no warranty of any kind, express or implied with regard to the information, including without limitation any warranty that the particular theme or plugin that you select is qualified on your situation.

The information in the individual theme or plugin displayed in the Directory is provided by the owners and contributors themselves. wpSocket gives no warranty as to the accuracy of the information and will not be liable to you for any loss or damage suffered by you as a consequence of your reliance on the information.

Links to respective sites are offered to assist in accessing additional information. The links may be outdated or broken. Connect to outside sites at your own risk. The Theme/Plugin Directory does not endorse the content or accuracy of any listing or external website.

While information is made available, no guarantee is given that the details provided are correct, complete or up-to-date.

wpSocket is not related to the theme or plugin, and also not responsible and expressly disclaims all liability for, damages of any kind, arising out of the use, reference to, or reliance on, any information or business listed throughout our site.

Keep Leading Your Followers!
Share it for them.