Difference between this plugin and other http2 push plugin?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author shawfactor

    (@shawfactor)

    8 years, 1 month ago

    I wrote mine because I was not happy with that plugin. The problem is that it pushes everything which you REALLY should NOT be doing if you want a fast site.

    Thread Starter sunnycmui

    (@sunnycmui)

    8 years, 1 month ago

    Okay cool.

    I’m trying it out and it seems like I’m getting a few console warnings that some of the resources preloaded weren’t used within a few seconds. Are there any plans to allow more fine grained control of which resources are pushed?

    Plugin Author shawfactor

    (@shawfactor)

    8 years, 1 month ago

    My plugin has a filter, but it that only works if you can code (and even then it is tricky as that bit of code is not very extensible). But if you send me the URL I’ll have a look at it.

    More broadly though, as I said my plugin only pushes assets in the head. So if you have assets in the head that are not being used you could dequeue them entirely or move them to the footer. You should be doing this anyway. There are plenty of plugins to do this or it is pretty easy to code.

    • This reply was modified 8 years, 1 month ago by shawfactor.
    Plugin Author shawfactor

    (@shawfactor)

    8 years, 1 month ago

    I am resolving this for good order. But I will still monitor the thread.

    As I said my plugin only pushes assets in the head, these can be assumed to be necessary.

    If they are not take them out of the head, problem solved.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Difference between this plugin and other http2 push plugin?’ is closed to new replies.