描述
DietPress puts your WordPress on a diet and speeds it up. It pairs a complete set of performance optimizations (the ones that used to ship in “Zero Config Performance Optimization”) with a clean, risk-based interface to disable the WordPress features you do not use. Everything is configurable, and the performance optimizations are already on by default, so you can simply activate and enjoy a faster site, or fine-tune every detail.
Coming from “Zero Config Performance Optimization”? This is the same plugin, now called DietPress and fully configurable. All your previous optimizations stay active by default; you just gained a settings page and a whole new set of WordPress-diet options.
By default WordPress loads functions, services and scripts that most sites do not need. They slow down loading times and consume hosting resources. DietPress lets you trim that fat and apply battle-tested performance tweaks, with a clear description of what each option does and what might break, organized by risk level so you always know what is safe.
TWO THINGS IN ONE PLUGIN
1. Performance optimizations (on by default)
- Automatic Critical CSS inlined in the head (optional experimental deferral of non-critical CSS)
- JavaScript defer parsing with smart dependency handling
- Image loading attributes safety net: lazy loading, decoding=async and fetchpriority for images that bypass core
- Automatic image dimensions for better CLS scores (including picture elements)
- Resource hints: preconnect and DNS prefetch for common third-party origins
- Theme stylesheet, critical fonts and logo preloading for a faster LCP
- Google Fonts display=swap
- RSS feed optimization (cache headers and item limit)
- Server rules in .htaccess: browser caching, GZIP and Brotli compression, immutable cache headers, CORS for fonts and keep-alive (master switch plus per-feature toggles)
- Database maintenance: daily expired-transient cleanup and safe query optimizations
2. Put WordPress on a diet (risk-based, opt-in)
- Light (safe for any site): emojis, RSD/WLW tags, shortlinks, self-pingbacks, comment pagination, admin email check, and more
- Moderate (evaluate first): oEmbed, jQuery Migrate, Dashicons on the frontend, Global Styles and Duotone, remote block patterns, avatars and Gravatar, comment threading, and more
- Strict (site-specific): granular RSS feed control, Heartbeat API mode, post revisions and autosave, disable comments, XML sitemap, native lazy loading/fetchpriority, content types, and more
- Widgets: dashboard widgets (including third-party ones from Yoast, WooCommerce, Elementor, Jetpack, Wordfence, Rank Math, Gravity Forms), classic sidebar widgets, block-editor widgets and the Customizer
SCALE, PROFILES AND ANALYZER
- Savings indicator: HTTP requests removed, CSS/JS saved and active optimizations at a glance
- Quick profiles: Personal Blog, WooCommerce Store, Landing Page and Maximum Cleanup
- Site analyzer: personalized recommendations based on your active plugins and content
- Import and export your whole configuration as a JSON file
COMPATIBILITY AND EXTENSIBILITY
The plugin includes filters for developers:
dietpress_critical_css– Customize the inline critical CSSdietpress_critical_css_handles– Define which CSS handles are criticaldietpress_skip_defer_script_handles– Opt scripts out of the JavaScript deferdietpress_skip_defer_style_handles– Opt stylesheets out of the CSS deferraldietpress_preconnect_hints– Customize preconnect originsdietpress_dns_prefetch_domains– Customize DNS prefetch domainsdietpress_critical_fonts– Define critical fonts to preload
Compatible with:
- Well-coded themes and page builders (Divi, Elementor, Beaver Builder, Gutenberg)
- Cache plugins (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, etc.)
- Security plugins (DietPress focuses on performance and deliberately leaves security to them; we recommend our free Vigilant)
- CDNs (Cloudflare, StackPath, KeyCDN, etc.) thanks to CORS and Vary headers
- WordPress Multisite
HOW TO VERIFY THE OPTIMIZATIONS
- Cache rules: check your
.htaccessfor a block marked# BEGIN DietPresswithimmutableCache-Control headers - Logo preload: view page source and look for
<link rel="preload" ... fetchpriority="high">pointing to your logo - Critical CSS: view source and look for
<style id="core-diet-critical-css">in the head - Compression: test at giftofspeed.com/gzip-test
Always measure with tools like Google PageSpeed, GTMetrix or WebPageTest, and run each test at least twice to account for caching.
Support
Need private support or custom development?
Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need.
Need help or have suggestions?
Love the plugin? Please leave us a 5-star review and help spread the word!
About AyudaWP
We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.
螢幕截圖
安裝
- Go to your WP Dashboard > Plugins > Add New and search for ‘DietPress’, or upload the
wpo-tweaksfolder to/wp-content/plugins/. - Activate the plugin through the ‘Plugins’ menu in WordPress.
- Open the DietPress menu to review the settings. Performance optimizations are already on; the diet options are off until you enable them.
常見問題
-
I was using “Zero Config Performance Optimization”. What changed?
-
It is the same plugin, now called DietPress. All the performance optimizations you had are still active by default, so nothing breaks on update. On top of that you now get a settings page, individual control over every optimization, and a complete set of options to disable unused WordPress features.
-
Is it still zero-config?
-
Yes, if you want it to be. The performance optimizations are on by default, so you can just activate and go. The difference is that now you can fine-tune everything and, optionally, put WordPress on a diet by disabling features you do not use.
-
I also have the standalone “DietPress” (core-diet) plugin installed. What do I do?
-
Nothing needs to be done by hand. When this plugin is active it detects the old “core-diet” plugin and deactivates it automatically (and core-diet 1.0.4 also steps aside on its own). Your settings are preserved because both plugins store them in the same place. The only thing left for you to do is delete the “core-diet” plugin whenever you like.
-
Where are the security options the standalone DietPress had?
-
They were intentionally left out. The standalone DietPress (core-diet) included a few security toggles (disable XML-RPC, hide login errors, disable Application Passwords, hide the WordPress version, close pingbacks). Security belongs in a security plugin, where those protections are implemented properly and maintained as such; we recommend our free Vigilant. If you migrate with any of those toggles enabled, DietPress shows you a one-time notice listing them, and those features simply return to the default WordPress behavior.
-
Will it break my site?
-
The performance optimizations are designed to be safe and are tested across many sites. The diet options only change something when you explicitly enable each toggle, and every option has a description of what might break. If something fails, turn the toggle off; deactivating the plugin restores default WordPress behavior.
-
Is it compatible with caching plugins and CDNs?
-
Yes. DietPress works alongside caching plugins and includes CORS and Vary headers for full CDN compatibility.
-
Something went wrong after activation
-
If a plugin or theme does not enqueue scripts correctly, the JavaScript defer may affect it; you can turn that option off or use the
dietpress_skip_defer_script_handlesfilter. If you get a 500 error, edit your.htaccessand remove the block that starts with# BEGIN DietPress(or# BEGIN Zero Config Performanceif you updated from 2.x and the rules have not been rewritten yet), or disable the “.htaccess server rules” option. -
Can I customize the optimizations as a developer?
-
Yes. See the filters listed in the description (the
dietpress_*hooks).
評價
貢獻者及開發者
修改日誌
3.1.0
- Improved: Performance – JavaScript defer now skips a built-in list of third-party scripts that must run on load (reCAPTCHA, Typekit, HubSpot forms, payment SDKs and more), matched by URL, and extendable with the new
dietpress_skip_defer_script_patternsfilter. - Improved: Performance – image optimization now leaves images already handled by another lazy-load solution untouched, honoring the
skip-lazy/data-skip-lazymarkers and the markup of common sliders (LayerSlider, Soliloquy), the Contact Form 7 captcha and the WooCommerce placeholder. - Improved: Performance – image optimization is skipped inside page builder editors and previews (Beaver Builder, Divi, Oxygen and WordPress previews) so layouts are not altered while editing.
- Improved: Performance – site logo detection for image priority is now filterable via the new
dietpress_logo_class_patternsfilter. - Improved: Performance – missing dimensions are now added to SVG images too (read from their width/height or viewBox), reducing layout shift.
- Improved: Performance – the Scale tab savings counter now also accounts for the performance optimizations (defer, critical CSS, image loading, resource hints, feeds, transient and query optimization, and .htaccess rules).
- Improved: Performance – the .htaccess rules now declare the AVIF MIME type so AVIF images are served correctly on older Apache servers, and set the document charset from your site settings.
- Improved: Security – the .htaccess performance rules no longer keep a copy of your site .htaccess inside the plugin folder. They are written non-destructively (only their own marked block is added or removed), so that copy was never used to restore anything; any backup left by earlier versions is removed automatically on update.
- Fix: the per-tab “Restore defaults” button now also resets the performance options shown on that tab, which it previously skipped.
- Fix: settings export files now use the “dietpress” identifier; imports still accept files exported by earlier versions.
For older changelog entries, please check the changelog.txt file.