Very long waiting times fetching a css file but it’s there

  • Resolved samsports

    (@samsports)


    2 months ago

    It’s only active on our internal testing page because we had to remove it on the public production site due to very long waiting times. The “Query Monitor” plugin shows a strange behaviour. see screenshot. The strange this is, that this ressource can be loaded without problems when I manually insert it into the browser. This really slows down a lot, because we have this 2-3 times and the page had a duration of mor e than 10 seconds to load.

    https://i.postimg.cc/9fZxn3VS/image.png

    • This topic was modified 2 months ago by samsports.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi!

    Thanks for providing the screenshot. That’s very helpful!

    wp_remote_get() times out while fetching the stylesheet from the Google Fonts API. So that means that PHP (cURL) probably isn’t allowed by your server to request/open/read external resources. I suggest you contact your hosting provider and have them look into it.

    If you need more help, you know where to find me!

    Thread Starter samsports

    (@samsports)

    Thanks for the reply!

    Today is an other day and as a sudden, this specific error was gone like it was never there, even when I try different pages. Can’t explain that.

    We use “Visual Composer” (NOT the wpbakery one) but this time I investigated that OMGF really detects a lot of fonts and variations and if I test it one one of our pages, it loads so much fonts locally that we still have about 15 seconds loading time. Maybe it’s not optimized for Visual Composer users? Because visible are only about 4-5 different fonts-(variations) on my testing site and the OMGF plugin made 36 HTTP calls a about 0.5 s?

    https://i.postimg.cc/zGGv6QTt/image.png

    • This reply was modified 2 months ago by samsports.
    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Can you share the site’s URL? Then I’ll be able to provide a more detailed reply. If you don’t want to share it here, you can send it to me using this contact form.

    Thread Starter samsports

    (@samsports)

    Will use the contact-form.

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Okay, so looking at your page source an awful lot of Google Fonts are loaded — even when they’re not actually used in the frontend.

    This is line 118 – 135 from the page source of your homepage, and I removed all lines pointing to your staging site’s URL:

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyopen-sans700regularsubsetcyrilliccyrillic-extgreekgreek-extlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyopen-sansregularsubsetcyrilliccyrillic-extgreekgreek-extlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyopen-sans700subsetcyrilliccyrillic-extgreekgreek-extlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyoswald700300subsetcyrilliccyrillic-extlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyoswald600300subsetcyrilliccyrillic-extlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyopen-sans300subsetcyrilliccyrillic-extgreekgreek-exthebrewlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyoswald700subsetcyrilliccyrillic-extlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyopen-sans300subsetcyrilliccyrillic-extgreekgreek-extlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyoswald600subsetcyrilliccyrillic-extlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    <link rel='stylesheet' id='vcv:assets:source:styles:httpsfontsgoogleapiscomcssfamilyopen-sansregularsubsetcyrilliccyrillic-extgreekgreek-exthebrewlatinlatin-extvietnamese-css'  type='text/css' media='all' />

    So, the answer to your question is simple: OMGF is detecting all these fonts, because they’re loaded. You can use OMGF to clean up the unused fonts, by leveraging the Unload option.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.