Async CSS Active but PageSpeed Still Shows Render-Blocking CSS

Title: Critical CSS and Async CSS appear active, but PageSpeed still reports render-blocking CSS

I am using LiteSpeed Cache 7.9.1 on a Hostinger WordPress/WooCommerce site built with Hello Elementor + Elementor Pro.

My mobile PageSpeed score has been fluctuating significantly, recently around 57–58, with LCP around 11.4 seconds.

The main issue is that PageSpeed continues to report roughly 3.6 seconds of render-blocking requests, mostly CSS files from Elementor, WooCommerce, Hello Elementor, Font Awesome, and related plugins.

My current LiteSpeed CSS settings include:

• Load CSS Asynchronously: ON
• CCSS Per URL: ON
• Inline CSS Async Lib: ON
• CSS Minify: OFF
• CSS Combine: OFF
• Generate UCSS: OFF
• UCSS Inline: OFF

I forced the Critical CSS cron and cleared the LiteSpeed cache.

I then checked the actual homepage source code. It appears LiteSpeed is working correctly:

• The page contains a <style id="litespeed-ccss"> block.
• CSS files are being changed to async/preload loading with data-asynced="1" and rel="preload".
• The bottom of the source says:
  • Page cached by LiteSpeed Cache 7.9.1
  • QUIC.cloud CCSS loaded

However, Google PageSpeed still identifies those CSS files as render-blocking.

I also temporarily removed the mobile hero image to test whether it was causing the slow LCP. The PageSpeed score and LCP were essentially unchanged, and the first product image simply became the new LCP element.

My question:
If CCSS is loaded and the stylesheets are being converted to async/preload, why is Lighthouse still treating these CSS files as render-blocking? Is there a known issue involving LiteSpeed Cache, QUIC.cloud, Elementor, WooCommerce, or Hostinger caching/CDN that could cause this?

I would appreciate guidance on what to check next rather than changing additional optimization settings blindly.

The page I need help with: [log in to see the link]