Adds optional lazy loading. Nothing changes until you turn it on.<\/p>","0.1.0":"
First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3785864,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3785864,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3785864,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3785864,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[146,3853,247,11676,794],"plugin_category":[52,54],"plugin_contributors":[290866],"plugin_business_model":[],"class_list":["post-391781","plugin","type-plugin","status-publish","hentry","plugin_tags-cache","plugin_tags-page-cache","plugin_tags-performance","plugin_tags-preload","plugin_tags-speed","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-mdraabiul","plugin_committers-mdraabiul"],"banners":{"banner":"https:\/\/ps.w.org\/cache-shark\/assets\/banner-772x250.png?rev=3785864","banner_2x":"https:\/\/ps.w.org\/cache-shark\/assets\/banner-1544x500.png?rev=3785864","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/cache-shark\/assets\/icon-128x128.png?rev=3785864","icon_2x":"https:\/\/ps.w.org\/cache-shark\/assets\/icon-256x256.png?rev=3785864","generated":false},"screenshots":[],"raw_content":"\n
Cache Shark saves a static copy of each public page and serves it to visitors before WordPress, your theme and your plugins have to run. Pages load faster and your server does less work.<\/p>\n\n
What it does<\/strong><\/p>\n\n Safe by default<\/strong><\/p>\n\n Pages are never cached for logged-in users, commenters, password-protected posts, search results, 404 pages, feeds, the REST API, AJAX requests, or any request with a query string (marketing parameters such as utm_source are ignored). WooCommerce cart, checkout and account pages are never cached, and visitors with items in their cart are always served live pages. You can add your own excluded URLs and cookies.<\/p>\n\n Not included yet<\/strong><\/p>\n\n CSS and JavaScript minification, delayed JavaScript, critical CSS, CDN and database cleanup are planned for later releases. Multisite network activation is not supported yet.<\/p>\n\n Privacy<\/strong><\/p>\n\n Cache Shark does not collect data, does not use cookies and does not contact any external service. Preloading only requests pages from your own site.<\/p>\n\n\n If Load a page twice while logged out and look at the response headers. The first request shows No. Two page caching plugins both want Cart, checkout and account pages are excluded from the cache by design, and visitors with items in their cart always get live pages. If you use WooCommerce, test your checkout after activating, and add any custom shop pages to the \"Never cache these URLs\" setting.<\/p><\/dd>\n WordPress security tokens (nonces) expire after 12 to 24 hours, and a cached page can contain one. Keeping the lifespan under 12 hours prevents \"link expired\" errors.<\/p><\/dd>\n Page caching works on any server. The GZIP and browser caching rules are added to Preloading uses WP-Cron, which only runs when someone visits your site. On quiet sites, or if Open Settings > Cache Shark and either untick lazy loading, raise \"Skip the first images\", or list the image's class name or file name under \"Never lazy-load these\". Clear the cache afterwards.<\/p><\/dd>\n Deactivating removes the drop-in, the line it added to Use Clear all cache<\/strong> on the settings page or in the admin bar. If a page shows content from another post (for example a related-posts list), it refreshes when its cache lifespan ends. Developers can add more URLs to clear with the \n
\n
cache-shark<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the plugin from the Plugins screen.<\/li>\nwp-config.php<\/code> is not writable, the plugin shows the one line to add yourself: define( 'WP_CACHE', true );<\/code><\/p>\n\n\n\n
How do I know it is working?<\/h3><\/dt>\n
X-Cache-Shark: MISS<\/code> and the second shows X-Cache-Shark: HIT<\/code>. You can also view the page source: cached pages end with an HTML comment saying when they were cached.<\/p><\/dd>\nCan I use it with another caching plugin?<\/h3><\/dt>\n
wp-content\/advanced-cache.php<\/code>. If another plugin already owns that file, Cache Shark does not overwrite it and shows a warning. Deactivate the other plugin first.<\/p><\/dd>\nDoes it work with WooCommerce?<\/h3><\/dt>\n
Why is the cache lifespan only 10 hours by default?<\/h3><\/dt>\n
Does it work on Nginx?<\/h3><\/dt>\n
.htaccess<\/code>, so they apply to Apache and LiteSpeed only. On Nginx, add equivalent rules to your server configuration.<\/p><\/dd>\nPreloading is slow or not running.<\/h3><\/dt>\n
DISABLE_WP_CRON<\/code> is set, add a server cron job that requests wp-cron.php<\/code> every few minutes.<\/p><\/dd>\nLazy loading changed how my page looks.<\/h3><\/dt>\n
What happens when I deactivate or delete the plugin?<\/h3><\/dt>\n
wp-config.php<\/code>, its .htaccess<\/code> rules and the cached files. Deleting the plugin also removes its settings. A drop-in belonging to another plugin is never touched.<\/p><\/dd>\nA page I changed still shows old content.<\/h3><\/dt>\n
cache_shark_related_urls<\/code> filter, or keep a page out of the cache with the cache_shark_should_cache<\/code> filter.<\/p><\/dd>\n\n<\/dl>\n\n\n0.2.0<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n