Disable Core Functions

Disable Core Functions

Why Disable Core Functions?

Like storing furniture in your garage that you will never use, it is easier to dispose of it than keep it. Under the same principle that some of the PWA functions need to be enabled, because you may not use them.  We let you turn off certain core functions in WordPress because you may not use them.  These functions are controlled through the admin console.

Optimized for Speed: There are a few core functions that are in WordPress that you may never use or want to stop others from using.  Some of the core functions actually will negatively affect page optimization because they add unnecessary weight to the CSS or JS files and some even negatively impact optimization.

Admin Interface: Some sites will never use Emojis.  If that is the case for your site, you can disable those and doing so will reduce the size of both the CSS and JS.

WordPress was originally designed to be a blog, but has developed into the most used CMS today.  Some sites do not have a blog so comments are not needed.  Also, sites that do have comments, find a different way to integrate them.  Comments attract spammers and some site owners are not willing to spend the time or resources to maintain them.  In the admin console, you can turn comments off, and reduce the size of the static assets.

News Feeds:just like comments, some times news feeds serve no purpose on the site.  The can be toggled off in the admin console and will also reduce the size of the static assets.

There are some functions that are automatically turned off and can not currently be turned back on.  The Gutenberg Editor loads static assets for its blocks whether you use it or not.  Currently Timber-Boot v2.5 does not fully integrate with the new editor.  As ACF and Timber fully integrate these features and have new stable versions released, Timber-Boot will then release updates to utilize the new editor.

A core feature of WordPress is to put the version numbers after loading static assets, so instead of a file ending being named jquery.js it is named jquery.js?3.0.1.  The same goes for css files.  If WordPress does not know the version number, it will default to putting the version number of WordPress after the asset.  The problem here is that if the file does not end in .js or .css. then they can not be compressed, as your servers modules that do this are instructed to do so by the final extension of the file.