Error and SECOND font-awesome is now loading AND without lazy loading

  • Enabling this function, loads a second copy of font-awesome on the site. It also shoots an error message in the javascript console in chrome. Please enable or share a way I can remove this second copy of font-awesome. I’d prefer not to have the first copy.

    (index):157 Uncaught ReferenceError: Main is not defined
    at (index):157

    Also, with Siteground Performance tools, the images are not lazyloading. I assume others will be the same and this is because the hook you’re using runs after them.

    The impact of these three things on performance is substantial. I’m already removing other font-awesomes, not sure why this one is ignoring the request.

    • This topic was modified 4 years, 7 months ago by Michael.
    • This topic was modified 4 years, 7 months ago by Michael.

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

Viewing 1 replies (of 1 total)
  • Thread Starter Michael

    (@mgparisi)

    Disabling the CSS with the switch in the option fixed all the issues except the LazyLoading issue. In addition, the images are not being converted to next gen formats.

Viewing 1 replies (of 1 total)
  • The topic ‘Error and SECOND font-awesome is now loading AND without lazy loading’ is closed to new replies.