Category Archives: lang:en

Blogposts on in English (mostly because these posts are republished in a non-Dutch-speaking context).

We just joined the club!

Autoptimize just joined the “1+ million active installs”-club. Crazy!

I’m very happy, thanks everyone for using, thanks for the support-questions & all the great feedback therein and especially thanks to the people who actively contributed and especially-especially to Emilio López (Turl) for creating Autoptimize and handing it over to me back in 2013 and to Tomaš Trkulja who cleaned up al lot of the messy code I added to it and introducing me to PHP codesniffer & Travis CI tests.

Google Font display swap in Autoptimize?

Autoptimize 2.5.1 (out earlier this week) does not have an option to enforce font-display on Google Fonts just yet, but this little code snippet does exactly that;

function add_display($in) {
  return $in.'&display=swap';

Happy swapping (or fallback-ing or optional-ing) :-)

Easter bunny special: Autoptimize 2.5

Autoptimize 2.5 has been released earlier today (April 22nd).

Main focus of this release is more love for image optimization, now on a separate tab and including lazyload and WebP support.

Lots of other bugfixes and smaller improvements too off course, e.g. an option to disable the minification of excluded CSS/ JS (which 2.4 did by default).

No Easter eggs in there though :-)

My Hacker News 15 minutes of fame: the numbers

So on Feb 25th my Do Not Donate-page was featured on Hacker News and that obviously brought some extra page-views.

Here are some more numbers for that memorable day;

  • Most popular pages:
    1. Do not donate: 10 013
    2. Homepage/ archives: 1 108
    3. about:futtta: 235
  • Referrers:
    1. Hacker News 7 978
    2. Facebook 112
    3. Search Engines 84
  • Outgoing links:
    1. 959
    2. 809
    3. 596
    4. 87

And my server? Even at the busiest time (around 10-11 AM UTC+1) it quietly hummed along with a 0.11 system load :-)

How to (not) correctly load Gutenberg JS

On Facebook someone asked me how to do Gutenberg the right way to avoid loading too much JS on the frontend, this is a somewhat better organized version of my answer;

I’m not a Gutenberg specialist (for from it, really) but:

  • the wrong way is adding JS with wp-block/ wp-element and other gutenberg dependencies on init calling wp_enqueue_script,
  • the right way is either hooking into enqueue_block_editor_assets (see
  • or when using init doing wp_register_script and then register_block_type referring to the correct editor_script previously registered (see

I’ve tried both of these on a “bad” plugin and can confirm both solutions do prevent those needless wp-includes/js/dist/* JS-files from being added on the front-end.