• Resolved Kipex

    (@kipex)


    Love the plugin, but I have to bring up an older post from another user, where you responded planning to fix an issue for the next release. That however was a long time ago (1 year 6 months).

    Wpa.css is still showing up as a render-blocking resource in PageSpeed Insights. This is a completely unnecessary ~100-200ms slowdown for every page.

    Like the older post mentioned, the wpa.css file seems to be relevant only to the “Honeypot Test Widget”, which is an admin only tool. Not only could you defer the file, but there also seems to be no reason for this to be loaded for all users. It shouldn’t be loaded even for admin users considering I have specifically disabled the test widget.

    Hopefully you can now resolve this asap, as it seems like a quick, easy, and impactful improvement. I can easily disable the wp_enqueue_style line of code from wpa_functions.php, but manual edits to a plugin isn’t really a smart solution when updating multiple sites etc.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Kipex

    (@kipex)

    I did notice wpa.css also includes #altEmail_container, which will be visible in forms without the css file, and while adding it to my own stylesheet does hide it for the main frontend, it doesn’t hide it in the wp login form.

    So my initial idea of disabling wp_enqueue_style isn’t perfect, but the problem nonetheless needs a proper solution.

    Plugin Author Dnesscarkey

    (@dnesscarkey)

    @kipex,

    Thank you so much for your input. We will test and use deferred for css loading in our next release.

    Thanks

    • This reply was modified 10 months, 3 weeks ago by Dnesscarkey.
    Plugin Author Dnesscarkey

    (@dnesscarkey)

    Hi @kipex,

    We tried loading the css file of our plugin in footer. But seems like it will be not fit for all users.

    So i suggest you to use some external plugins like cache plugin that can help you load css in footer.

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘wpa.css is still render-blocking’ is closed to new replies.