1 / 30

Frontend Single Point of Failure: Addressing Synchronous Script Issues

Learn how synchronous scripts can block rendering in browsers, understand async solutions, and avoid SPOF pitfalls for a better website performance. Delve into real case studies and actionable insights to strengthen your site's resilience. Disclaimer: Views expressed in this content do not necessarily represent the views of the employer.

yered
Télécharger la présentation

Frontend Single Point of Failure: Addressing Synchronous Script Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Your script just killed my site stevesouders.com/docs/fluent-spof-20120530.pptx Disclaimer: This content does not necessarily reflect the opinions of my employer.

  2. SPOF

  3. synchronous scripts block all following elements from rendering in all browsers

  4. #fail

  5. async #fail async sync async

  6. Frontend SPOF

  7. http://www.webpagetest.org/result/120529_41_HWV/

  8. entire BODY blocked from rendering

  9. http://www.webpagetest.org/result/120529_41_HWV/

  10. mysql>

  11. mysql> select p.url, wptid

  12. mysql> select p.url, wptid from pages as p, requests as r

  13. mysql> select p.url, wptid from pages as p, requests as r where p.pageid >= 844954 and p.pageid <= 1564447 and p.pageid = r.pageid and

  14. mysql> select p.url, wptid from pages as p, requests as r where p.pageid >= 844954 and p.pageid <= 1564447 and p.pageid = r.pageid and rank < 20000 and

  15. mysql> select p.url, wptid from pages as p, requests as r where p.pageid >= 844954 and p.pageid <= 1564447 and p.pageid = r.pageid and rank < 20000 and resp_content_type like “%script%” and

  16. mysql> select p.url, wptid from pages as p, requests as r where p.pageid >= 844954 and p.pageid <= 1564447 and p.pageid = r.pageid and rank < 20000 and resp_content_type like “%script%” and time > 10000 and

  17. mysql> select p.url, wptid from pages as p, requests as r where p.pageid >= 844954 and p.pageid <= 1564447 and p.pageid = r.pageid and rank < 20000 and resp_content_type like “%script%” and time > 10000 and renderStart > 10000

  18. mysql> select p.url, wptid from pages as p, requests as r where p.pageid >= 844954 and p.pageid <= 1564447 and p.pageid = r.pageid and rank < 20000 and resp_content_type like “%script%” and time > 10000 and renderStart > 10000 group by p.pageid;

  19. what’s your website’s weakest link?

More Related