A lot has changed since we last estimated (2017) a global baseline for total page resource limits of 120-170KiB. Thanks to progress in networks and browsers (but not devices), the new baseline is much more generous: ~100KiB of HTML/CSS/fonts and ~300-350KiB of JS. But the devil's in the footnotes, and modern web development practices push the median page well above these guidelines.
Are you an experienced and proactive engineer looking for exciting opportunities in the automotive industry? Join our Porsche Digital Croatia team and work on developing a global e-commerce solution.
This article will introduce you to a collection of libraries for creating PDFs in Javascript, comparing their usability, Typescript and environment (Node/Browser) support,...
The web platform relies on the origin as a fundamental security boundary, and browsers do a pretty good job at preventing explicit leakage of data from one origin to another. Attacks like Spectre, however, show that we still have work to do to mitigate implicit data leakage. The side-channels exploited through these attacks prove that attackers can read any data which enters a process hosting that attackers' code. These attacks are quite practical today, and pose a real risk to users.
Using animations, transitions and smooth scrolling is fun, but they also represent an accessibility problem. Various groups of people have a hard time using your products when things move and change all the time.