mashsb.min.css not using wp_register_style

  • Resolved wrestleclub

    (@wrestleclub)


    9 years, 10 months ago

    I’ve been trying to optimize my site by removing unused css. when I checked chrome, it told me that mashsb.min.css had 81% unused css.

    The best practice for overriding a plugin css it to use wp_dequeue_style/wp_deregister_style and then wp_register_style/wp_enqueue_style to add your custom css to replace it.

    I went to mashsharer/includes/scripts and noticed that you are dynamically building the css and then doing a echo.

    It seems like it would be better to use the wp filesystem api to create the css when changes are saved. Then you can use wp_register_style/wp_enqueue_style. This would allow other developers to dequeue your css as needed.

    Does the premium code do this or is there any chance this would be fixed in the next update?

    https://wordpress.org/plugins/mashsharer/

Viewing 1 replies (of 1 total)
  • Rene Hermenau

    (@renehermi)

    9 years, 10 months ago

    Hello,

    Only a very little number of css elements are included inline, 99% of these are parts which you have probably specified in the custom css form. (if you send us a screenshot or the claimed css i verify if thats the case) To solve this You can leave the custom css empty and put your css into a new file which you have registered with wp_enquee.

Viewing 1 replies (of 1 total)

The topic ‘mashsb.min.css not using wp_register_style’ is closed to new replies.