I love the performance footer. Proud!
#Development #Overviews
Hack to the future · What past front-end approaches still teach us https://ilo.im/166f1r
_____
#WebPlatform #Browser #AI #Accessibility #WebPerf #WebDev #Frontend #HTML #CSS #JavaScript
#Development #Debates
Stop trying to kill the Single-Page Application · “Reports of SPA’s death are greatly exaggerated.” https://ilo.im/166f1c
_____
#SPA #Websites #WebApplications #Astro #Frameworks #JavaScript #WebPerf #WebDev #Frontend
#Development #Guides
Using the Safari developer tools · How to get started with Safari’s Web Inspector https://ilo.im/165xux
_____
#Safari #WebInspector #Debugging #DevTools #Console #Browser #WebPerf #WebDev #Frontend #JavaScript
5 terabytes for 30 seconds of homepage video is it worth it? (no) https://wagtail.org/blog/5-terabytes-for-30-seconds-of-homepage-video/
#Design #Approaches
The beauty of a text-only webpage · “You’re contributing to a simple, calm, and happier internet.” https://ilo.im/1666f6
_____
#Text #Content #Webpage #Blog #Website #Accessibility #WebPerf #Hosting #SmallWeb #IndieWeb
#Development #Analyses
The fastest site in the Tour de France · Which bike brand excelled in both browser and race? https://ilo.im/16600l
_____
#TourDeFrance #WebPerf #WebPage #Metrics #WebVital #CrRRUX #Browser #DevTools #WebDev #Frontend
#Design #Pitfalls
The current state of skeleton screens · ”Loading screens are not fooling anyone anymore.” https://ilo.im/165vxd
_____
#Loading #Content #Skeletons #UxDesign #UiDesign #WebDesign #WebPerf #Development #WebDev #Frontend
Anyone else using Compression Dictionary Transport to compress response bodies with a site-specific dictionary?
The first time you visit https://www.astray.com/recipes/ in Chrome, the response body is compressed with Brotli and takes 2,186 bytes. In the background the browser downloads a 400 byte dictionary.
The next time you visit https://www.astray.com/recipes/ the body is compressed with Brotli (using the shared dictionary) and takes only 1,799 bytes.
The savings add up with each request.
#webperf #http
Fwiw: I've seen arr.length = 0; as a way to empty an array after taking a slice copy, before processing its contents, to ensure atomicity around a buffer.
This is usually an unverified micro-optimisation that may even be counter-productive depending on browser/engine; compared to simpler = [];
However one valid use is multiple variables/props pointing to it, then it can avoid a split brain problem.