First release. Activating changes nothing: every switch starts off.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3721266,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3721266,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3721266,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3721266,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3721266,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3721266,"resolution":"1","location":"assets","locale":"","width":3811,"height":1825},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3721266,"resolution":"2","location":"assets","locale":"","width":3804,"height":1818},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3721266,"resolution":"3","location":"assets","locale":"","width":3797,"height":1828},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3721266,"resolution":"4","location":"assets","locale":"","width":3790,"height":1809},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3721266,"resolution":"5","location":"assets","locale":"","width":3834,"height":1806}},"screenshots":{"1":"Overview - what is switched off, per group, with the site-wide presets.","2":"A group tab - every switch with its impact badge, what it does and what might break.","3":"The performance test - pick pages, run, and see the difference with and without SlimPress.","4":"Test history - earlier runs, per-feature results, the settings each run used, and a trend\nchart for HTML size, PHP time and queries across runs.","5":"Tools - export, import and reset."}},"plugin_section":[],"plugin_tags":[3711,5901,187,247,6558],"plugin_category":[52,54],"plugin_contributors":[277115],"plugin_business_model":[],"class_list":["post-377697","plugin","type-plugin","status-publish","hentry","plugin_tags-disable","plugin_tags-heartbeat","plugin_tags-optimization","plugin_tags-performance","plugin_tags-xml-rpc","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-macvej","plugin_committers-macvej"],"banners":{"banner":"https:\/\/ps.w.org\/slimpress\/assets\/banner-772x250.png?rev=3721266","banner_2x":"https:\/\/ps.w.org\/slimpress\/assets\/banner-1544x500.png?rev=3721266","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/slimpress\/assets\/icon.svg?rev=3721266","icon":"https:\/\/ps.w.org\/slimpress\/assets\/icon.svg?rev=3721266","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/slimpress\/assets\/screenshot-1.png?rev=3721266","caption":"Overview - what is switched off, per group, with the site-wide presets."},{"src":"https:\/\/ps.w.org\/slimpress\/assets\/screenshot-2.png?rev=3721266","caption":"A group tab - every switch with its impact badge, what it does and what might break."},{"src":"https:\/\/ps.w.org\/slimpress\/assets\/screenshot-3.png?rev=3721266","caption":"The performance test - pick pages, run, and see the difference with and without SlimPress."},{"src":"https:\/\/ps.w.org\/slimpress\/assets\/screenshot-4.png?rev=3721266","caption":"Test history - earlier runs, per-feature results, the settings each run used, and a trend\nchart for HTML size, PHP time and queries across runs."},{"src":"https:\/\/ps.w.org\/slimpress\/assets\/screenshot-5.png?rev=3721266","caption":"Tools - export, import and reset."}],"raw_content":"\n
SlimPress turns off parts of WordPress core that your site does not use - emoji scripts, XML-RPC,\nthe REST API for logged-out visitors, Heartbeat, comments, feeds, author and date archives,\nsearch, revisions, image sizes, block editor extras, dashboard clutter, automatic updates,\nadmin emails and more - grouped by area and explained in plain language. A built-in performance test\nmeasures what it changes on your own pages, with and without SlimPress, without changing a setting.<\/p>\n\n
What makes it different:<\/p>\n\n
What SlimPress deliberately does not do: page caching, minification, \"remove unused CSS\",\ndelay-JS, per-page script managers, CDN rewrites. If a feature is not \"turn off something core\nWordPress does\", it does not go in.<\/p>\n\n
Nothing is switched off until you switch it off. Every switch is a runtime filter, so\ndeactivating SlimPress restores WordPress completely on the next request. SlimPress never writes to\ncore tables or core options.<\/p>\n\n
Each group has an on\/off switch of its own, so you can pause a whole group while you look for a\nproblem, and put it back exactly as it was.<\/p>\n\n
The Overview tab offers site-wide presets (Safe defaults, Blog, Brochure site, WooCommerce store,\nHeadless). A preset only ever switches things on: it shows you what it would change first,\nskips anything an active plugin relies on, and leaves everything else as it is.<\/p>\n\n
A feature that is off loads no code and adds no hooks. SlimPress adds no CSS, JavaScript or\nmarkup to your public pages, ever. With every feature off, SlimPress adds about 105 KB of memory\nand no database queries to a front-end request, and the time it adds was too small to measure\n(WordPress 7.1, PHP 8.4, median of 40 paired runs).<\/p>\n\n
The performance test tab has an optional \"Run Google PageSpeed test\" button. Only when you click it,\nSlimPress sends your site's homepage URL to Google's PageSpeed Insights API\n( This service is provided by Google: Terms of Service<\/a>,\nPrivacy Policy<\/a>.<\/p>\n\n\n No. Every feature is off by default and activation writes nothing.<\/p><\/dd>\n WordPress is back to stock on the very next request. SlimPress applies everything through runtime\nfilters and actions, so there is nothing to undo. The one exception is the \"Delete old\nrevisions\" button: revisions it deleted stay deleted, which is why it asks first.<\/p><\/dd>\n Every toggle that can visibly break something is marked Careful<\/strong> and says what might stop\nworking. The ones most likely to catch you out:<\/p>\n\n SlimPress also warns you when an active plugin is known to need something you are about to switch\noff.<\/p><\/dd>\n The version string is what makes browsers fetch a fresh file after an update. Removing it gains\nnothing measurable and can serve visitors stale CSS and JavaScript. SlimPress also has no switch\nfor turning off lazy loading, auto No. It works on any site. On a WooCommerce store it warns you about switches the shop relies on,\nand there is a WooCommerce store preset that leaves the shop alone. A WooCommerce tab with its own\nswitches (admin nags, tracking, background jobs and more) appears automatically while WooCommerce\nis active, and disappears - without losing your choices - if you deactivate it.<\/p><\/dd>\n SlimPress does not cache, minify or combine anything, so it does not overlap with a caching\nplugin. The performance test asks for uncached pages, and if a page cache answers anyway it says\nso rather than showing you the cache's numbers.<\/p><\/dd>\n Only if you click the optional PageSpeed button on the performance test tab. See \"External\nservices\" below.<\/p><\/dd>\n Yes. The Tools tab exports your settings as a JSON file and imports them on another site. It\nalso resets every switch to off.<\/p><\/dd>\n\n<\/dl>\n\n\nhttps:\/\/www.googleapis.com\/pagespeedonline\/v5\/runPagespeed<\/code>) to fetch Core Web Vitals for that\npage. No other data is sent, no API key is used, and nothing is sent automatically.<\/p>\n\n\n
\/wp-content\/plugins\/slimpress\/<\/code>, or install it from the Plugins screen.<\/li>\n\n
Does activating SlimPress change anything on my site?<\/h3><\/dt>\n
What happens if I deactivate SlimPress?<\/h3><\/dt>\n
Which toggles are risky?<\/h3><\/dt>\n
\n
wp-cron.php<\/code>. Set that up first.<\/li>\nWhy doesn't SlimPress remove ?ver= query strings?<\/h3><\/dt>\n
sizes<\/code> on lazy images or big-image scaling, because each of\nthose makes sites slower. The Media tab explains big-image scaling on an info card instead.<\/p><\/dd>\nDoes SlimPress need WooCommerce?<\/h3><\/dt>\n
Will it conflict with my caching plugin?<\/h3><\/dt>\n
Does SlimPress contact any external service?<\/h3><\/dt>\n
Can I move my settings to another site?<\/h3><\/dt>\n
Unreleased<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n