Cache External Scripts vs WP-PJAX

Often when trying to optimize the Google Pagespeed score, there is one script which still causing the ‘Leverage browser caching’ rule popping up: Google’s own gtag.js and/or analytics.js file… With this plugin you will be able to cache this file on your local server and enable browser caching for longer than 2 hours. The plugin will check every day if there is a newer version of the file to keep the cache up to date.

THIS PLUGIN IS STILL EXPERIMENTAL – USE AT YOUR OWN RISK! The plugin is under development. Please try it and contact me if you encounter any bugs or have any questions or suggestions. If you want to help me develop this further send a pull request on GitHub. The plugin is not ready for production yet, but I will soon release version 0.1 that will be production ready. WP-PJAX – PJAX for WordPress Plugin. Makes your site faster and saves you a lot of bandwidth and CPU power by making your WordPress site PJAX powered! What is PJAX? PJAX is a technique that uses AJAX and PushState to deliver a faster browsing experience by only loading and updating parts of the page HTML each page load. PushState makes it possible to add real permalinks, page titles, and a working back button so that your visitors won’t be able to tell the difference between PJAX page load and ordinary full page loads, except for the increased speed of course :). Why PJAX? It makes your site significantly faster in most cases and saves you both processing power and bandwidth! Features Speeds up any website. With the built in page cache enabled you can expect 10-50+% faster page loads. Supports 4 Levels of application cache! This plugin uses browser cache and page cache. It is also enabling reverse proxy(i.e. Varnish) cache by (optionally) striping sessions and cookies and it works very well with underlaying object and database cache using third party cache plugins such as W3 Total Cache (recommended). Works well with W3 Total Cache. Configurable. No need to dig into the code. You will still need basic knowledge about HTML and how WordPress works to make this plugin reach it’s full potential. Live notices with a report for every page load (Load time, page cache hit or miss, Reverse proxy/Varnish cache miss or hit etc – See screenshot). This is great for debugging and testing and is of course only visible for admins. Only a few changes in your theme and you are ready to go. Should not take more than 5 minutes and requires only basic knowledge. Browser support PJAX is not supported in Internet Explorer 9 and earlier(IE 10+ supports this), but the plugin handles this gracefully by falling back on regular page loads for unsupported browsers. Details on browser support Development All development of this plugin occurs on GitHub. Please help me develop this by forking and sending pull requests. Planned features / To-Do Better handling of menu active classes. Will probably use regex for this. Support for marking parent pages active would be nice but I don’t know any good ways to accomplish that. Better control over exceptions for when to disable PJAX, when you use Page cache, and when and what cookies and sessions that should be striped. Regex support will be added. Refresh cache on publish/update. Separate loading of sidebars with separate cache. Page loading notice / icon. This should also be customizable with css, text(localizable) and it should be possible to upload your own icon. Page cache prefetch needs to be revisited. WP-Cron is a bit tricky and its hard to handle timeouts gracefully and reliably cross different environments. Remove all debug code and general code cleanup. This will be finished before the 0.1 release. Add an optional menu to the admin bar for clearing cache(all and current page). Optimize execution flow for better performance Maybe: Better way to generate the configurable javascript. I think of two options for this, ether use wp_localize_script to inject variables into javascript or to generate a javascript with PHP file when settings are saved. Known issues The PJAX toggle checkbox does not work. $.pjax.disable() does not seam to work as it should. Maybe I need to set a cookie with AJAX to set this for the current user and then handle it on the server side. Development All development of this plugin occurs on GitHub. Please help me develop this by forking and sending plull requests.