XStore 9.7 – Product carousel blocking LCP on mobile (5090ms render delay)

This topic has 6 replies, 2 voices, and was last updated 15 hours, 44 minutes ago ago by Andrei Andrei

  • Avatar: Andrei Andrei
    Andrei Andrei
    Participant
    May 22, 2026 at 15:31

    Hello,

    We are using XStore 9.7 with Elementor and LiteSpeed Cache on onedee.ro.

    We have a performance issue on mobile: our LCP element is the H2 heading inside the etheme_product_carousel widget (“Cele mai vandute produse din sex shop online”). Lighthouse reports an Element Render Delay of 5,090ms for this element because the browser cannot paint it until the carousel JavaScript finishes executing.

    Setup details:
    – Theme: XStore 9.7 + child theme
    – Page builder: Elementor
    – Cache: LiteSpeed Cache with UCSS enabled
    – Widget: etheme_product_carousel (bestsellers, grid type, 6 products)

    Our questions:
    1. Is there a way to lazy load the etheme_product_carousel widget so it does not block the initial render?
    2. Can the carousel heading be rendered as static HTML before the JS initializes, so the browser can paint it immediately?
    3. Is there a recommended approach in XStore 9.7 to reduce the JavaScript render-blocking impact of the product carousel on mobile?

    Thank you.

    5 Answers
    Avatar: Jack Richardson
    Jack Richardson
    Support staff
    May 22, 2026 at 15:41

    Hello @Andrei Andrei,

    If you would like to enhance the loading speed of specific widgets, please enable the “XStore Ajaxify” option in the Page Editor under “Widget → Advanced tab → XStore Ajaxify setting” (https://prnt.sc/gte5t_WqjmdN).

    To ensure this feature functions properly, please also activate the “Enable Ajaxify On Website” option in “Theme Options → Speed Optimization” (https://prnt.sc/mv0CLmmakYbJ).

    Best regards,
    Jack Richardson
    The 8Theme’s Team

    Avatar: Andrei Andrei
    Andrei Andrei
    Participant
    May 22, 2026 at 15:53

    Hello Jack,

    Thank you for the suggestion. We have now enabled “Enable Ajaxify On Website” in Theme Options and activated “XStore Ajaxify” on the product carousel widget (etheme_product_carousel, bestsellers, grid type).

    Our current setup for reference:

    XStore 9.7 + child theme, Elementor 4.0.9, LiteSpeed Cache 7.8.1

    XStore Speed Optimization settings:
    – CSS Minify (et_load_css_minify): OFF (disabled to avoid conflict with LiteSpeed UCSS)
    – Disable Block CSS: ON
    – Disable Elementor Dialog JS: ON
    – Disable Theme Swiper JS: ON
    – Menu Cache: ON
    – Ajax Search Cache: ON
    – Global Ajaxify: ON (just enabled)
    – Widgets Ajaxify: applied to product carousel widget

    LiteSpeed Cache settings:
    – CSS Combine + UCSS: ON
    – JS Defer: ON
    – Guest Mode + Guest Optimization: ON
    – Redis Object Cache: active

    Current mobile Lighthouse scores: Performance 86, LCP 3.1s, TBT 0ms
    CrUX (real users, 28-day): LCP 3.8s, INP 223ms, CLS 0.16, TTFB 2.8s

    Our remaining issues:
    1. LCP 3.8s on mobile – element render delay 5090ms on the H2 heading inside the carousel
    2. INP 223ms – slow interaction response on mobile, likely from XStore + Elementor JS
    3. CLS 0.16 – layout shift from announcement bar injected via JS

    Are there any additional XStore-specific optimizations you recommend for our setup to further reduce LCP and INP on mobile?

    Thank you,
    Andrei

    Avatar: Jack Richardson
    Jack Richardson
    Support staff
    May 22, 2026 at 17:38

    Hello @Andrei Andrei,

    You can find detailed information about the available configuration options in our article: https://www.8theme.com/documentation/xstore/troubleshooting/the-ultimate-2025-guide-to-boosting-wordpress-speed-with-xstore-theme/.

    Best regards,
    Jack Richardson
    The 8Theme’s Team

    Avatar: Andrei Andrei
    Andrei Andrei
    Participant
    May 22, 2026 at 20:51

    Hello Jack,
    Thank you for the article. We have reviewed it and applied all relevant optimizations:

    Disable Native WordPress Lazy Loading: ON
    Disable Old Browser Support: ON
    FontAwesome: Disabled
    Ajax Menu Dropdown: ON
    Menu Cache + Ajax Search Cache: ON
    Disable jQuery Migrate: ON
    Disable Gutenberg Styles: ON
    Disable Elementor Dialog JS: ON
    Disable Theme Swiper JS: ON
    Disable Emoji + Embeds: ON
    Static Block Cache: ON
    Ajaxify: ON on product carousel widget
    Elementor Global Fonts: all set to system fonts, no external fonts loading
    CSS Minify: OFF (LiteSpeed handles CSS optimization)
    Image Quality: 82

    Our remaining issue is the LCP element render delay of 5090ms on mobile for the H2 heading inside the etheme_product_carousel widget. Even with Ajaxify enabled on the carousel, the heading still cannot be painted until the carousel JS executes.
    Is there a way in XStore 9.7 to render the carousel heading as static HTML independently of the carousel JS initialization? This would allow the browser to paint the LCP element immediately without waiting for the full widget to load.
    Thank you,
    Andrei

    Avatar: Andrei Andrei
    Andrei Andrei
    Participant
    May 22, 2026 at 21:09

    Subject: XStore – HTTP API calls to 8theme.com on every page load

    Hi,

    I’m running XStore on onedee.ro and I’ve identified a performance issue using Query Monitor.

    On every page load, the theme makes 2 external HTTP requests to your servers:

    1. https://8theme.com/import/update-history/xstore/ — ~0.20s
    2. https://8theme.com/x-api/?action=check — ~0.44s

    Total: ~0.64 seconds added to every single page load, for every visitor.

    This is happening on the frontend, not just in wp-admin. These requests appear to be a license check and an update history fetch. Both are blocking the PHP execution and contributing significantly to our TTFB.

    Questions:
    1. Is there a setting to disable or limit these checks to wp-admin only?
    2. Can the frequency be reduced (e.g. once per day via transient, not on every request)?
    3. Is there a known fix or upcoming update addressing this?

    Currently I’ve blocked these requests at the WordPress level as a workaround, but I’d prefer an official solution.

    Please advise.

    Thank you

  • Viewing 6 results - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.Log in/Sign up

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.