Thoughts & prayers or Thoughts & actions?
Month: March 2023
Autoptimize Pro 1.3; instant.page
New booster in Autoptimize Pro 1.3: instant.page, a 3rd party JS component that can significantly improve performance for visitors going from one page to another on your site by preloading a page based on visitor behavior.
Do take into account that it could increase the number of page requests as the preloaded page might end up not being requested after all.
More info on https://instant.page.
How to fix Autoptimize & Critical CSS cron issue
Critical CSS (either through Autoptimize with your own Critical CSS account or through Autoptimize Pro which includes Critical CSS) requires WordPress’ scheduling system to function to be able to communicate with criticalcss.com on a regular basis. In some cases this does not work and you might see this notification in your WordPress dashboard;
It looks like there might be a problem with WordPress cron (task scheduling)
If this is the case, go through these steps to troubleshoot:
- install the “WP Crontrol“-plugin and go to Tools -> Cron Events
- WP Crontrol will warn if “cron” (another name for job scheduling) is disabled
- Look for “ao_ccss_queue” and check the “next run” time/ date.
- If the has a “next run” date is in the past, there is an issue with your site/ host’s WordPress cron. Some hosts’ info on the topic can be found for WP Engine here , here for BlueHost, here for HostGator and lastly here for SiteGround.
- Alternatively you can click on “manually process job queue” in the jobs pane in Settings -> Autoptimize -> Critical CSS
AOPro 1.2; delay JS, CSS & HTML as long as you want
Autoptimize Pro has “Boosters” to delay JavaScript (esp. interesting for external resources), CSS and HTML (which can be very impactful for long and/ or complex pages). Up until today’s release the delay was either until user interaction OR a set timeout of 5 seconds, but now you can choose the delay time yourself, setting it to e.g. 20s or 3s or -and that’s where things get a teeny bit shady- 0s to disable the time-out, waiting for user-interaction to load the delayed resources.
Setting the delay to 0 is a bit shady because at that point you are hiding those assets for performance tests which -although artificial- is likely to improve (lab test) performance scores. If you do use the 0s delay then do take into account that *real* users will still need to load/ render those assets and that that still may be a sub-optimal experience.