How We Improved The Performance Of Our Rust App
tl;dr: There are two performance issues Aram solves in the multiplexer app - data overflow in the MPSC channel and performance of rendering and data parsing.
featured in #239
The Mobile Performance Inequality Gap, 2021
tl;dr: "Thanks to progress in networks and browsers (but not devices), a more generous global budget cap has emerged for sites constructed the "modern" way. We can now afford ~100KiB of HTML/CSS/fonts and ~300-350KiB of JS (gzipped). This rule-of-thumb limit should hold for at least a year or two."
featured in #227
How I Cut GTA Online Loading Times By 70%
tl;dr: "GTA Online. Infamous for its slow loading times. Having picked up the game again to finish some of the newer heists I was shocked to discover that it still loads just as slow as the day it was released 7 years ago. It was time. Time to get to the bottom of this."
featured in #226
Making GitHub’s New Homepage Fast And Performant
tl;dr: Tobias runs through the code that makes the page performant, how illustrators work with designers and engineers, the way in which the page was designed, and more.
featured in #223
Using The Chrome UX Report API
tl;dr: "Learn how to use the Chrome UX Report API to get easy, RESTful access to real-user experience data across millions of websites."
featured in #189
Is WebP Really Better Than JPEG?
tl;dr: "Google claims that their WebP format is 25 – 34% smaller than JPEG at equivalent quality." Here the two codecs are compared against each other on three different image sizes.
featured in #189
tl;dr: Comparative performance costs of jQuery, Vue, Angular and React.
featured in #181
How We Reduced Our Google Maps API Cost By 94%
tl;dr: Having a daily cost of $960 / day was too high for an early stage startup. Cityflo identified patterns in vehicle movement and travel times. Then by creating a route design for each vehicle, they were able to reduce costs.
featured in #180
Developing the Largest Contentful Paint Metric
tl;dr: A new performance metric has been established by the Chrome team measuring when the main contents of a page is displayed. This runs through the framework used to build this metric and the objective.
featured in #166
Moving Towards A Faster Web
tl;dr: The Chrome team are in development of "badging", a method of identifying sites that are built in "a way that makes them slow" by looking at historical load latencies. In the future, such information may be communicated to users.
featured in #161