Defer parsing of JavaScript

  • Resolved timholz

    (@timholz)


    6 years, 3 months ago

    Hi
    I refer to a topic that is already more than 3 years old:
    ?Plugin blocked rendering?.
    I have superclean selected and inspecting the dom, i see two inline scripts just before the head closes.
    I ran a little test on GTMetrix and as expected received the recommendation to defer parsing of JavaScript (4.6KiB of inline JavaScript).
    Since you use the plugin on your blog, i ran the same test for:
    https://blog.futtta.be/2011/02/17/why-your-wordpress-blog-needs-donottrack/
    Inspecting the dom i notice the inline javascript. But to my surprise GTMetrix
    reports 100 for Defer pasring of JavaScript.

    How do you achieve this performance with inline JavaScript in the head-section?

    Thanks for your time and interest.
    regards
    theo

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

  • How do you achieve this performance with inline JavaScript in the head-section?

    no idea theo, might well be a GPSI miss. it mistakes regularly I’m afraid. WPDNT indeed has (and needs) inline JS and (execution of) that indeed is render-blocking (which it has to be in this case; the JS has to block unwanted “stuff” from being loaded, so has to act before the actual rendering).

    hope this clarifies,
    frank

    Thread Starter timholz

    (@timholz)

    Hi Frank
    Thanks a lot for your clarification.
    I just thought i missed something.
    All the best to you and thanks for all of your plugins.
    regards
    theo

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Defer parsing of JavaScript’ is closed to new replies.