Placeholder loading issue – speed and Unsafe content

  • Resolved simplexdev

    (@simplexdev)


    4 years, 4 months ago

    Hey guys, loving the plugin so far. I’m having two issues though that I need to solve:

    1. https://gtmetrix.com/reports/title.tech/VA3Q93cR – On this report, on the waterfall tab, you’ll see that the YouTube placeholder is taking 4.98 seconds to fully “load”. Plus, it has a status of “incomplete”. I understand that the placeholder is only 14.9kb, but for some reason it’s delaying our load and increasing site load speed significantly. This happened both before and after we implemented our caching controls.

    It references this URL
    “https://title.tech/wp-content/plugins/complianz-gdpr/assets/video/youtube-placeholder.mp4?cmplz=1”

    2. On edge, this same placeholder causes an “Unsafe Content” error. As we want to use this tool on all future websites, this is the one thing really holding me back. I understand that we can report the site as safe and go through that whole thing, but it rarely works and shouldn’t be necessary. I’m sure this is a false positive, but are you guys working to correct this issue?

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter simplexdev

    (@simplexdev)

    Looking further, I can see that this issue only really appears like this on GTMetrix, not pingdom or some of the others. Is this a known issue with GTM?

    Plugin Author Aert Hulsebos

    (@aahulsebos)

    Hi @simplexdev,

    For 1. This is indeed a metric by GTMetrix only, we’re not quite clear why GTMetrix would count this toward loading time, as it doesn’t affect page speed. Even the opposite, whereby YouTube API calls and other scripts are not loaded, because they are blocked before consent. In your case, which is an opt-out region, it initialized due to possible user settings which might have revoked their consent. It will be incomplete and have no effect on the loading time, as GTMetrix servers will be seen as new users, without cached settings.

    For 2. Just like 1, also a false positive, but we’re aware the SmartScreen Defender from Edge (pre-Chromium release) sometimes, wrongfully detects the placeholder as an issue. Whitelisting it will help indefinitely, but is indeed under investigation.

    Hope this helps,

    regards Aert

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Placeholder loading issue – speed and Unsafe content’ is closed to new replies.