Hello!
I'm using the Perfmatters WP plugin (LOVE IT!) with the Divi theme, which has several built-in performance options (Divi >> Theme Options >> Performance).
I'm wondering if any of these Divi settings might conflict with Perfmatters features?
The Divi options are:
- Dynamic Module Framework
- Dynamic CSS
- Dynamic Icons
- Load Dynamic Stylesheet In-line
- Critical CSS
- Critical Threshold Height
- Dynamic JavaScript Libraries
- Disable WordPress Emojis
- Defer Gutenberg Block CSS
- Improve Google Fonts Loading
- Defer jQuery and jQuery Migrate
How should I configure these options to ensure optimal performance without ANY conflicts?
Thanks!
Hi!
Firstly, read this article: https://onlinemediamasters.com/perfmatters-settings/
then, read this: https://www.elegantthemes.com/blog/divi-resources/divi-speed-optimization
test, compare and at the end watch this YouTube video (2+ hours long):
...and lastly - this article is interesting as well - again about Divi's performance: https://onlinemediamasters.com/divi-slow-loading-website/
Good Luck!
Cheers, Mik
Using Perfmatters with the Divi can greatly enhance performance.
However, there are some features that need to be configured carefully to avoid conflicts.
Here are my thoughts + settings:
1. Dynamic Module Framework
- What it does: Loads only the Divi modules used on the page, reducing bloat.
- Potential conflict: None. Perfmatters does not have a similar feature.
- Recommendation: Enable this in Divi for better efficiency.
2. Dynamic CSS
- What it does: Generates and loads only the CSS needed for the page dynamically.
- Potential conflict: None. Perfmatters doesn’t interfere with Divi-specific CSS loading.
- Recommendation: Enable Dynamic CSS in Divi.
3. Dynamic Icons
- What it does: Loads only the icon fonts used on the page.
- Potential conflict: None. Perfmatters doesn’t manage icon font behavior.
- Recommendation: Enable it in Divi to minimize icon font loads.
4. Load Dynamic Stylesheet Inline
- What it does: Loads dynamic styles inline instead of using external stylesheets.
- Potential conflict: None. Perfmatters doesn’t directly handle inline styles.
- Recommendation: Test this option. It can improve performance for small CSS but might hurt it if the inline styles are extensive.
5. Critical CSS
- What it does: Generates and loads critical CSS for above-the-fold content.
- Potential conflict: None. Perfmatters does not generate critical CSS.
- Recommendation: Enable it in Divi for faster rendering.
6. Critical Threshold Height
- What it does: Sets the height of the viewport for critical CSS generation.
- Potential conflict: None.
- Recommendation: Adjust this setting as needed based on your layout. It doesn’t overlap with Perfmatters.
7. Dynamic JavaScript Libraries
- What it does: Loads only the necessary JavaScript libraries.
- Potential conflict: Perfmatters’ Script Manager might conflict if you manually disable the same libraries.
- Recommendation: Enable it in Divi, but avoid manual script control in Perfmatters unless necessary.
8. Disable WordPress Emojis (they will still load in OS and browser)
- What it does: Stops WordPress from loading emoji-related scripts and styles.
- Potential conflict: Perfmatters offers the same option.
- Recommendation: Use this option in either Divi or Perfmatters, but not both.
9. Defer Gutenberg Block CSS
- What it does: Defers loading of Gutenberg block CSS.
- Potential conflict: Perfmatters can also defer Gutenberg CSS.
- Recommendation: Use this option in either Divi or Perfmatters, not both.
10. Improve Google Fonts Loading
- What it does: Optimizes how Google Fonts are loaded by combining or deferring requests.
- Potential conflict: Perfmatters offers similar Google Fonts optimization.
- Recommendation: Use this in either Divi or Perfmatters. Test both to see which works better.
11. Defer jQuery and jQuery Migrate
- What it does: Defers loading of jQuery and its migrate script.
- Potential conflict: Perfmatters offers a similar feature.
- Recommendation: Use this in either Divi or Perfmatters, but not both. Test carefully, as deferring jQuery may cause compatibility issues with plugins or custom scripts.
General Recommendations:
- Use overlapping features in either Divi or Perfmatters, not both.
- Test, test, test: Use tools like Google PageSpeed Insights or GTmetrix to monitor performance.
- AND MOST IMPORTANTLY!!! Use Perfmatters’ Script Manager: It provides precise control over scripts and styles, which Divi does not offer!
Cheers, madb 🙂