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
Shared Cache Is Going Away
tl;dr: A single cache is a security risk, browsers are responding by partitioning the cache. As a result, developers "won't get performance benefits from using a canonical URL over hosting on their own site."
featured in #160
Techniques To Make A Web App Load Fast, Even On A Feature Phone
tl;dr: Always measure before optimizing performance. Effective optimization methods are (1) deliver as many assets over one connection (2) preload assets for the first render / interactivity (3) prerender app to improve perceived loading performance (4) aggressive code splitting to reduce the amount of code needed for interactivity.
featured in #155
Fast Software, the Best Software
tl;dr: When you experience software, apps that perform quickly build trust. When applications are bloated, take time to load or function a command, we tend to distrust them and we lose our "flow". Aim to build fast, light, software. The author cycles through many examples of what he likes and doesn't.
featured in #149