Home › Forums › WoodMart support forum › Critical Performance Issue (29 Mobile / 65 Desktop) & WP Rocket CSS Conflict

Critical Performance Issue (29 Mobile / 65 Desktop) & WP Rocket CSS Conflict

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • March 8, 2026 at 7:35 am #711512

    noam.graphic
    Participant

    Hello WoodMart Support Team,

    I recently launched an e-commerce website (https://henricruchon.ch) using WoodMart, Elementor Pro, and WooCommerce. I chose WoodMart specifically because your sales page advertises it as \”Built for Speed,\” \”Mobile-First,\” and capable of achieving \”90+ PageSpeed scores without sacrificing design flexibility.\”

    Unfortunately, the current reality on my site is quite different. My Google PageSpeed Insights scores are currently 29 on Mobile and 65 on Desktop (Here is the report: https://pagespeed.web.dev/analysis/https-henricruchon-ch/imyj19evl6).

    To improve this, I purchased the WP Rocket optimization plugin. After extensive testing and discussions with WP Rocket support, I am stuck in a dilemma where I am forced to choose between a fast site or a functional site:

    Scenario A: WP Rocket \”Remove Unused CSS\” is ENABLED

    Performance: Excellent (99 Desktop / 84 Mobile).

    The Problem: It completely destroys the WoodMart mobile design. Product category pages break, typography fails to load (fallback fonts appear), and dynamic icons (add to cart, wishlist) disappear. Custom CSS (like hiding the \”in stock\” text) also stops working on mobile. WP Rocket\’s scanner seems incompatible with WoodMart\’s mobile-first DOM structure. Even after adding your classes (wd-, woodmart, etc.) and @font-face to WP Rocket\’s Safelist, the mobile layout remains broken.

    Scenario B: WP Rocket \”Remove Unused CSS\” is DISABLED (Using \”Load CSS Asynchronously\” instead)

    Design: 100% stable, no visual bugs.

    The Problem: Performance plummets back to 29 on Mobile and 65 on Desktop. The site is extremely sluggish and heavy.

    I have already tried using WoodMart\’s native CSS generator (Theme Settings > Performance > CSS > Generate CSS) and disabling unused elements, but without WP Rocket\’s aggressive CSS cleanup, the payload remains too heavy for good scores. I even encountered \”429 Too Many Requests\” errors on my server when trying to rebuild caches because of the heavy load.

    Since you state that WoodMart is engineered for performance with smart CSS/JS loading to achieve 90+ scores, I urgently need your technical expertise:

    WP Rocket Compatibility: Is there a definitive Safelist of CSS classes, files, or specific exclusions I need to provide to WP Rocket so \”Remove Unused CSS\” works without destroying WoodMart\’s mobile shopping experience?

    Native Optimization: If WP Rocket is too aggressive for WoodMart, how can I configure the theme natively to achieve the advertised 90+ PageSpeed scores on a WooCommerce/Elementor setup?

    The site is currently live, and it is crucial that we fix these slow loading times for our customers. Thank you in advance for your prompt assistance.

    Best regards,

    Noam Vulcan

    March 9, 2026 at 9:58 am #711585

    Artem Temos
    Keymaster
    Xtemos team

    Hello,

    Thank you for choosing our theme. Our theme is optimized for speed and should not significantly slow down your website. However, it’s possible that your website’s performance is affected by the content you have added. For instance, the use of too many plugins, large unoptimized images, or other resources can slow down your website.

    We recommend that you remove any unnecessary plugins and install a JS & CSS optimization plugin such as WP Rocket. Our guide on how to optimize your website using our themes can be found here: https://xtemos.com/wordpress-performance-optimization-the-ultimate-guide-in-2021/.

    If you have any further questions, please don’t hesitate to reach out.

    Kind regards,
    XTemos Studio

    March 9, 2026 at 2:37 pm #711642

    noam.graphic
    Participant

    Hello,

    Thank you for your reply and the link to your optimization guide.

    However, I must say that your response feels quite generic and does not address the specific issues I am facing. I am already using WP Rocket, and I have configured it as best as possible. Despite that, I am experiencing significant performance drops and conflicts, especially related to the “Remove unused CSS” feature, which notably breaks parts of my website — notably the category pages.

    My actual concern is to understand how to properly optimize the site without losing essential assets specific to the WoodMart theme, as these are crucial for the theme’s dynamic functionalities and overall performance.

    Could you please provide a more tailored analysis or guidance based on my actual setup? I am looking for concrete advice — not general suggestions — to resolve the current bottlenecks.

    Thank you for your understanding and assistance.

    Best regards,
    Noam

    March 9, 2026 at 4:43 pm #711712

    Artem Temos
    Keymaster
    Xtemos team

    Hi Noam,

    Thanks for the detailed report. The issues you see with WP Rocket’s Remove Unused CSS are expected with WoodMart’s responsive and dynamic styles.

    1) About Remove Unused CSS and a safelist
    – We do not recommend enabling Remove Unused CSS at all. It often strips responsive/mobile rules, icon fonts, and dynamic components, which breaks mobile layouts and typography.
    – We don’t maintain a safelist of classes/files for this feature. A universal list isn’t feasible because each site uses different elements and plugins.
    – If you still want to try it, the only reliable way is to build a per‑site safelist by testing each affected page and device. Otherwise, keep it disabled.

    2) Recommended setup for stable performance
    – Disable Remove Unused CSS. Keep WP Rocket’s other optimizations active (caching, minify, async CSS load).
    – Use a single lazy loader only. Configure lazy loading either in WoodMart > Performance or in WP Rocket, not both.
    – Optimize images and formats. Convert images to WebP (WoodMart Image Optimizer plugin or Imagify via WP Rocket), then retest.
    – Server cache policy. Ask your host to set long Cache-Control max-age for static assets (e.g., 1 year) to satisfy the “efficient cache policy” audit.
    – Reduce DOM size and heavy content. Elementor sections, large sliders, and very dense grids inflate the DOM and hurt mobile scores. Simplify sections and, if needed, use a lighter mobile layout (e.g., an HTML Block assigned for mobile).

    Kind Regards

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)