Support » Plugin: PWA — easy way to Progressive Web App » Bug, Snippet, chain

  • Resolved forexonlineproductionltd


    Good morning, afternoon, evening Iworks PWA.
    My message is to try to collaborate and give opinions for improvement (with all due respect).
    1- The biggest problem I see is in the snippet, how should your PWA work and run? I see in the code that there are promises and of the type “Async”. I see it correct and professional.
    But in the snippet when loading it is without anything. Should it be async? or defer? or should it be integrated into the HTML as it is such a small code to save the request?
    On my site I create by functions async. In my tests defer was problematic. Could it be integrated maybe better? For saving the request ?.
    2- I felt compelled to litespeed to say to compress something that is already committed. And that’s why the string is = see?. This is important if the URLs are clean and the request is never chained.
    3- The url of the footer is too long, alarms go off all the time in page speed,
    4- I think your position is important. Previously a “Javascript Footer” was correct. But today thinking about core web vitals maybe it should be in header at the end. Remember that the “Largest Content Paint” finish loading is important.

    Comment: In my tests using a “Base64” It was a disaster, horrible I do not recommend it.
    5- The json manifest is the slowest to load. But I did not find a solution to give you regrettably. Well, in all my tests it created errors in W3C HTML validator. The preload failed in all events (it was useless). Also it seems that there are problems if there is HTTP2 / PUSH. In that this if it makes sense that it is incompatible, because it processes something for “Desktop” and another for “Mobile”.
    6- I suppose this is complex, because on desktop it should not be activated (and it does not activate correctly). on mobile yes. So apply a mobile preload? and with a correct code? This would be the one I create (without w3c html errors).×144.png
    <link rel=”preload” href=”×144.png&#8221; as=”image” media=”(min-width:144px) and (max-width:144px)”>
    Note: I chose to put the same size in min and max. Well, its size should not be changing and to be sure.
    Why are the pngs created by series compressed with tiny png no longer serve? there are quite large savings. Or at least the main one should be compressed.
    8- This is weird, I give you the url:

    Maybe something is wrong with the programming? It is not anything external to my website, nor pluguins (I hardly use it). I couldn’t see the problem, but it does jump.

    And that’s it.
    I hope I have helped you and please do not take it the wrong way, I just try to contribute and give ideas and suggestions.
    Keep in mind that in reality your work is already excellent.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Marcin Pietrzak


    Awesome! Thank you! I will try to implement it.

    Thread Starter forexonlineproductionltd


    A final contribution.
    These are the results of my tests manipulating your plugin:

    defer + base64 = 3.5 - 6 sec
    Defer (not base 64, basic) 2.7
    Async footer 1.7
    Async header (End of / head) 1.1 - 1.3
    Integrated Final (Footer) 0.9 - 1.1 sec
    Integrated in header final / header 0.7 - 0.9
    No charge whiplash.
    These results are:
    - In async manipulating that the order cannot do what it wants, but exactly.
    -En defer without manipulating as it is.
    -In integrated allowing to read the normal HTML and changing positions.
    That's all, I no longer write to him + so as not to bother him ah ah !.
    Have a great day.
    Thread Starter forexonlineproductionltd


    Sorry I forgot.
    Sometimes external jquery comes out. The version that is super old with 4 serious security bugs.
    It would be good to use the latest version (Especially for security).
    That’s all.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Bug, Snippet, chain’ is closed to new replies.