Tim Kadlec
  • Writing
  • Speaking
  • About

Tagged: testing

5 posts

  • January 26, 2022

    Fixing Performance Regressions Before they Happen | by Netflix Technology Blog | Jan, 2022 | Netflix TechBlog

    This post describes how the Netflix TVUI team implemented a robust strategy to quickly and easily detect performance anomalies before they are released — and often before they are even committed to the codebase.

    ∞ Permalink
  • January 12, 2021

    Understanding the True Cost of Client-Side A/B Testing

    • performance
    • edge computing
    • testing
  • May 21, 2020

    A/B Testing Instant.Page With Netlify and Speedcurve

    • performance
    • metrics
    • monitoring
  • November 21, 2018

    Second Meaningful Content: the Worst Performance Metric | Filament Group, Inc., Boston, MA

    I rather like Scott's term for what happens when you use client-side JavaScript for A/B testing.

    This pattern leads to such a unique effect on page load that at last week's Perf.Now() Conference, I coined a new somewhat tongue-in-cheek performance metric called "Second Meaningful Content," which occurs long after the handy First Meaningful Content (or Paint) metric, which would otherwise mark the time at which a page starts to appear usable.

    ∞ Permalink
  • December 27, 2016

    What we learnt from our mistakes in 2016 - The Guardian

    I love companies that are as invested in giving back to the community as they are at doing quality web-work. The Guardian is certainly one of them, and their latest post is a great example. They walk through several errors and mistakes they made on their site this year, why those mistakes were made, and how they fixed them.

    ∞ Permalink

© 2026 Tim Kadlec.

If RSS is your sort of thing, you can subscribe to a few different feeds. The main feed has everything. There are also individual feeds for just posts, just links, and just book reviews.