You should not disturb core files, lets say even if you copy those files in footer and tomorrow wordpress releases another new version, and you update it. The files that you moved from /wp-includes/js/… will be back. In my opnion, try to minimize them. Although you be fine with wordpress core files, when optimizing your … Read more
No real difference either way, really. Network installs make the most sense when you want all the sites to share a single set of users. But the basic table handling is pretty much the same either way.
Where is the fold now? to me, the fold is a little outdated, as it fully depends on the device/monitor size. It may be that JavaScript in the header of your site is blocking the page load. The best way to combat this is to simply load the JavaScript in the footer of the site … Read more
Use a tool like Gulp to minify using NodeJS packages. Gulp Uglify for JS, Gulp CSS Min for CSS. As for GZip, you’ll need to enable that on your server config – Apache using mod_deflate in .htaccess and In IIS, you can set it up in “website properties” (Tab Services), and then allow “compress application … Read more
There are multiple plugins out there that can do this for you! For example Checkout JS & CSS Script Optimizer.
I’m the author of that plugin. I think you should post such question on WP.org’s support forum or on my website so I can get to you faster. If not for the pingback from this site I wouldn’t know you are asking this :). About your issue, how did you enqueue that file? How does … Read more
I addition to the methods you have mentioned, the biggest way to speed up your loading time is with a caching plugin. There are many in the WordPress Plugin Directory, but my favorite is Quick Cache.
Not sure how dramatic this’ll be, but it should improve nontheless: <?php /** * You can try forcibly splitting the query (grabbing IDs *then* all fields) * Works well for large post results. (available WP 3.4+) */ add_filter( ‘split_the_query’, ‘__return_true’ ); $posts = get_posts( array( ‘post_type’ => ‘listings’, ‘posts_per_page’ => -1, /* Disable term caching … Read more
Caching full pages is not going to do you any good for a situation like you described. Users will update things and expect to see their updates right away — meaning you spend more server time invalidating cached pages. The database server is likely to be your biggest bottleneck in just about any webapp. Two … Read more
Functions and shortcodes that are never used, eat some processor time at launch, as WP is registering their existence. Deregistering them would take up some additional (and minimal) processor time. Because they are loaded with functions.php they will reside in memory, either registered or deregistered. Which amounts to the same, as the code is never … Read more