Preloads and preconnects

  • Resolved fob

    (@fob)


    2 years, 10 months ago

    I would like to modify priorities on load but ran into some trouble with the latest version:

    1. The latest FVM version seems to ignore preload settings:

    For example: If I select the option “Disable CSS Link Preload” nothing happens. All “Async CSS Files” will still be preloaded (by FVM) on load but should not be preloaded at all in the current configuration. I would like to preload only the main css and javascript files, things that must be available very early (above the fold). All the other stuff can be loaded normal (behind a full size GDPR banner).

    2. I would like to preconnect a few external ressources behind the scene:

    I made a quick test with some “Pre* Party Resource Hints” (plugin) to make DNS checks available earlier (for later full connects where needed). Unfortunately the “header cleanup” sweeps out those attempts but shall be active.

    The first thing seems to be a bug in the current version. But, are there any recommended methods for filtering those two parts with functions that could include the desired exceptions for only some preloads and preconnects?

    (I would like to test if nothing must be ignored or be put into render blocking parts of the page, if preloading is used only for most important parts.)

Viewing 1 replies (of 1 total)
  • Plugin Author Raul P.

    (@alignak)

    I am not seeing any issue with the Disable CSS Link Preload, or Disable JS Link Preload.
    Perhaps you are seeing a page cache, and that is why it looks as if it’s not doing anything?

    You can confirm this by changing clearing the cache on FVM, then look at the file names.
    /wp-content/cache/fvm/min/XXXXXXXXX-YYYYYYYYYYY.css WHERE XXXXXXXXX will be a number, that must be different from the previous time you purged the cache.

    Whenever you purge FVM, this XXXXXXXXX number will change, so if you don’t see it changing, you are seeing a page cache (hosting, cdn, plugin, etc).

    The header cleanup is intended. A lot of plugins add preconnects and other hints, that slow down things, so FVM removes them to prioritize the preload headers, necessary for the critical css and js files (render blocking).

    For CSS you can choose what to async, and there is no link preload.
    For JS only what you put on the render blocking section will have a link preload.
    And you can disable both preloads, using the Disable CSS Link Preload, or Disable JS Link Preload.
    Just tested this and working.

Viewing 1 replies (of 1 total)
  • The topic ‘Preloads and preconnects’ is closed to new replies.