A little over 6 years ago, we presented quiche, our open source QUIC implementation written in Rust. Today we’re announcing the open sourcing of tokio-quiche, our battle-tested, asynchronous QUIC library combining both quiche and the Rust Tokio async runtime. Powering Cloudflare’s Proxy B in Apple iCloud Private Relay and our next-generation Oxy-based proxies, tokio-quiche handles millions of HTTP/3 requests per second with low latency and high throughput.
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Tim Kadlec
Monitoring AS-SETs and why they matter
An AS-SET, not to be confused with the recently deprecated BGP AS_SET, is an Internet Routing Registry (IRR) object that allows network operators to group related networks together. AS-SETs have been used historically for multiple purposes such as grouping together a list of downstream customers of a particular network provider.
The Growing "Contentful" Gap
You may know, if you’ve been following along, that Chrome shipped some changes to how they define “contentful” for Largest Contentful Paint—they now look at the level of entropy for an image (measured in bits per pixel) to see if it’s above a certain threshold. What you might not realize, is that the same logic doesn’t apply yet to First Contentful Paint.
Improving Paint Metrics by Removing Unused Preloads
Last month, at Lazy Load, Paul Calvano gave a presentation where he dove deep into HTTP Archive to uncover some common performance mistakes. One of the issues he explored were sites that preloaded resources that never actually end up being used by the page. The preload hint is a way of indicating to the browser that a particular resource will be needed for that page, and that the browser should request it now, when the preload hint is encountered, rather than waiting for later discovery.
Introducing the New WebPageTest Recorder Chrome Extension
WebPageTest’s custom scripting functionality unlocks some very powerful testing capabilities, including being able to test multi-step user journeys and flows through your site and application. Writing those scripts, however, can sometimes be challenging. Today, that’s getting a whole lot easier thanks to the new WebPageTest Recorder extension that let’s you export flows from Chrome’s built-in recorder directly as WebPageTest Custom scripts.
Introducing Opportunities & Experiments: Taking the Guesswork out of Performance
Today we are excited to launch a set of new, powerful features and functionality for all users of WebPageTest to help make it faster and easier for you and your teams to make sense of your website’s performance, the opportunities for improvement, and, critically, how significant those opportunities are.
New Render Blocking Indicator in Chrome and WebPageTest
Thanks to a new indicator provided by Chrome in their traces (starting in version 91 of the browser, with a notable bug fix shipping with version 92 today), we just started highlighting all render-blocking requests in our waterfalls, making it easier to quickly zero-in on blocking requests that may be causing significant bottlenecks in your page's performance.
Benchmarking JavaScript Memory Usage
One of the things that is so challenging about the conversation around memory usage on the web right now is the sheer number of unknowns. We haven't historically had ways of accurately determining how much memory a page is using in the real world, which means we haven't been able to draw a connection between memory usage and business or user engagement metrics to be able to determine what "good" looks like.
Understanding the True Cost of Client-Side A/B Testing
Client-side A/B testing has been a performance loving developer’s worst friend for years. The way it works is you load in some JavaScript (typically from a third-party domain), and that JavaScript runs, applying the experiments you’re running for any given situation.
Frontend Focus Issue 472: January 6, 2021
Easy to unsubscribe at any time. Your e-mail address is safe — here's our privacy policy. ✨ Looking back: Frontend highlights from 2020 Hello 2021! Thanks for opening the first issue of the year. 😊 We're kicking things off with a look back at some of the frontend highlights of the past twelve months. As such, this issue includes just over a dozen of the top links you tapped on in 2020.
The Web Almanac by HTTP Archive
Part I Chapter 2 Reviewed by Sawood Alam and Artem Denysov Analyzed by Rick Viscomi and Paul Calvano Introduction JavaScript has come a long way from its humble origins as the last of the three web cornerstones—alongside CSS and HTML. Today, JavaScript has started to infiltrate a broad spectrum of the technical stack.
Effective Skeleton Screens
When I first stumbled on the idea of skeleton screens, thanks to Luke Wroblewski talking about them back in 2013, I latched onto them pretty quickly. I have never been a fan of progress bars and spinners, and skeleton screens seemed like a smart step in the right direction. For those unfamiliar, a skeleton screen is a method of displaying the outline (skeleton) of the content to come, typically using gray boxes and lines instead of a progress bar while content is loading.
3 Stories Of Cloud Foundry Enabling Enterprises Across Clouds and COVID
Sprinkled among the developer talks and agile transformation panels at SpringOne 2020 were several talks from companies using VMware’s distribution of Cloud Foundry: VMware Tanzu Application Service. With all the pressure on organizations to accelerate digital transformation and move to the cloud, Cloud Foundry is proving an essential part of the solution.
A/B Testing Instant.Page With Netlify and Speedcurve
I’ve wanted to give instant.page a proper try out on my site for a while now. It’s a pretty clever approach. The script watches for when someone hovers over a link and then, when they do, uses the prefetch resource hint to get started fetching that page before the click event even occurs. I like the idea, in theory, quite a bit. I also like the implementation.
The Cost of Javascript Frameworks
April 21, 2020 # performance javascript frameworks tools There is no faster (pun intended) way to slow down a site than to use a bunch of JavaScript. The thing about JavaScript is you end up paying a performance tax no less than four times: The cost of downloading the file on the network The cost of parsing and compiling the uncompressed file once downloaded The cost of executing the JavaScript The memory cost The combination is very expensive. And we are shipping an increasingly high amount.
Setting a performance budget
Jason Grigsby once quipped that “We’ve remade the Internet in our image….obese.” He was right, of course. Average page weight and number of connections has been increasing at a rather alarming rate. This is why I’ve been so happy to see the recent rash of posts discussing performance as a fundamental component of design. The latest comes from Mr. Brad Frost.
When CSS Blocks - Web Performance Consulting | TimKadlec.com
The other day I was auditing a site and ran into a pattern that I’ve seen with a few different clients now. The pattern itself is no longer recommended, but it’s a helpful illustration of why it’s important to be careful about how you use preload as well as a useful, real-world demonstration of how the order of your document can have a significant impact on performance (something Harry Roberts has done an outstanding job of detailing).
In-Browser Performance Linting With Feature Policies
One of the absolute best things you can do to help keep performance in check is to provide a series of visible, well-placed checks and balances in your development workflow to always keep performance front-of-mind. One thing I’m very excited about in this context is feature policies. Feature-Policy is a relatively new feature that lets you opt-in or out of certain browser features on your site.
Blame the implementation, not the technique
Stop me if you’ve heard this one before. “Responsive design is bad for performance.” “User agent detection is bad. Don’t segment the web.” “Hybrid apps don’t work as well as native apps.” “CSS preprocessors shouldn’t be used because they create bloated CSS.” If you create for the web you’ve no doubt heard at least a couple of these statements. They’re flung around with alarming frequency.
Oh, the Places JavaScript Will Go
I tend to be pretty vocal about the problems client-side JavaScript cause from a performance perspective. We're shipping more JavaScript than ever to our user's devices and the result is increasingly brittle and resource-intensive experiences. It's... not great. But that doesn't mean I don't like JavaScript. On the contrary, I enjoy working in JavaScript quite a bit. I just wish we were a little more selective about where we use it.
Using the Platform
October 21, 2019 # performance accessibility security standards tools frameworks The other day I was listening to the latest Shop Talk Show podcast while out for my morning run. They had Jen Simmons on the show, talking about (among other things) the standards process. It’s a great conversation, as you would expect—Jen’s super smart and has been doing great, meaningful work for a long time.
Less Data Doesn't Mean a Lesser Experience
After yesterday’s post, someone on Twitter expressed concern about providing a “degraded experience” to users who have Save-Data enabled. It’s far from the first time I’ve heard this concern expressed. A user sees “Save Data” as an option and says, “Yeah, of course!” but they may not want a lesser experience as a result. It’s a fair concern, I think.
Malicious remote code execution backdoor discovered in the popular bootstrap-sass Ruby gem
On March 26, 2019, a malicious version of the popular bootstrap-sass package, that has been downloaded a total of 28 million times to date, was published to the official RubyGems repository. Version 3.2.0.3 includes a stealthy backdoor that gives attackers remote command execution on server-side Rails applications.
Making Sense of Chrome Lite Pages
Google formally announced Lite Pages the other day and the response has been….let’s say mixed. Understandably so. The announcement post was a fairly typical product announcement post which is to say it was light (no pun intended) on the technical details and leaves a lot of open questions. Sometimes that’s fine. But in this case, the announcement has to deal with Google making changes to HTTPS content which, as you would expect, makes folks a little more nervous.
Performance Budgets That Stick
Occasionally I hear some chatter about performance budgets “not working.” And, to be fair, I have seen companies who adopt a budget and then are unable to make meaningful improvements towards that goal. Over time those ineffective budgets get pushed to the sideline where they accumulate dust before being forgotten about altogether. It’s not really about the performance budget, though.
The Ethics of Web Performance
One question I’ve seen posed a few times in the past several months is whether performance really is a moral or ethical concern, or if that’s all heavy-handed exaggeration. It’s a fair question, I suppose. Advocates of any technique or technology can be a bit heavy-handed when it suits them if they’re not being careful–myself included. But I’m not sure if that’s the case here.
Risking a Homogeneous Web
Last week I had the opportunity to present at a technical SEO conference about performance. At the speakers dinner, I was enjoying a really good conversation with a few folks I met. At one point, I brought up quokkas because they’re amazing and I desperately want to hang out with one. Or a few. Anyway. It turns out, the other folks at the table were not familar. I couldn’t let this injustice continue, so I told them to “Google for quokka selfies”.
The Cascade and Other Essential Unessentials
There was a poll posted the other day by Max on Twitter and it has lead to some fairly heated follow-up discussion (Developers being angry on Twitter? Shocking, I know.) The correct answer is that they’re both blue. The order of class names in HTML has no bearing on the styles. In this case, both selectors have the same specificity (they’re both class selectors) so there’s a tie there. Since comes later in the stylesheet, it overrides the selector. Both ’s will have text with the color blue.
Chrome's NOSCRIPT Intervention
The other week, there were a few articles that came out about Chrome’s NOSCRIPT intervention: an intervention that would disable JavaScript altogether on slow networks. Chrome intervening on behalf of the user when it feels the network is iffy isn’t exactly new. Chrome has several interventions including one that can replace images with placeholders and one that bypasses web fonts on slow connections. The NOSCRIPT intervention itself isn’t even new.
Compressive Images Revisited
2012 was a dark time for responsive images. Standards work had begun, but there was no consensus and many angry people (myself included). Some remained unconvinced that responsive images were even a problem that needed to be solved. But there was still a glimmer of hope in these dark days. In July of that year, Daan Jobsis discovered a technique that the Filament Group would later dub “compressive images”. The technique became pretty popular and worked quite well in lieu of an actual standard.
How Fast Is Amp Really?
March 19, 2018 # amp performance standards AMP has caused quite the stir from a philosophical perspective, but the technology hasn’t received as close of a look. A few weeks ago, Ferdy Christant wrote about the unfair advantage being given to AMP content through preloading. This got me wondering: how well does AMP really perform. I’ve seen folks, like Ferdy, analyze one or two pages, but I hadn’t seen anything looking at the broader picture…yet.
Security Corner with Snyk: Configuring Security
This year, Snyk and Cloud Foundry are working together to provide monthly posts focused on helping you stay more secure. This is the second installment. Read the first post here. There’s a principle of software development called “secure by default,” which states that the default state of any application should be the most secure state. It’s a fantastic idea in theory, but in reality it is rarely true.
The Two Faces of AMP
The day after AMP was launched, I published a post with a bunch of concerns I had—most notably, that of the incentives being put around building AMP content. It’s a concern that has been stated over and over again in the two-plus years of AMP’s existence, by numerous developers.
Security Corner with Snyk: A More Secure 2018 - Cloud Foundry
This year, Snyk and Cloud Foundry are working together to provide monthly posts focused on helping you stay more secure. We’ll have interviews with people from organizations within the Cloud Foundry community, discussing what they’re doing to manage security. We’ll have articles about specific security risks, and what to do about them. We’ll discuss different tools and processes you can incorporate to reduce your risk of exposure.
Snyk - The Frequency of Known Vulnerabilities in JavaScript Libraries
There’s an interesting whitepaper from last week’s NDSS Symposium that discusses a large-scale attempt at determining just how vulnerable client-side JavaScript libraries are. The study involved analyzing JS code across over 133,000 different websites. They scanned for popular JavaScript libraries (they ended up looking at 72), determined the versions in use and then queried to find if there were any known vulnerabilities. The conclusions were interesting, to say the least.
AMP and the Web - TimKadlec.com
The first day of the first ever Google AMP conference was today in New York. I would have loved to have been able to participate, but I had to settle for listening to bits and pieces from afar (thanks to Google for always doing such a good job of live streaming all of their events).
Tage von Bohuslav Martinů – Prolog
Der Kleine Saal mit 550 Plätzen folgt im Gegensatz zum Großen Saal dem klassischen Konzept der »Schuhbox«, bei dem sich die Bühne an der Stirnseite eines rechteckigen Raumes befindet. Das richtige Timing Die Elbphilharmonie ist ein besonderes Gebäude an einem besonderen Ort. Bitte planen Sie für die Anfahrt und den Weg in den Konzertsaal genügend Zeit ein. Wir empfehlen, die Anreise so zu planen, dass Sie spätestens 30 Minuten vor Veranstaltungsbeginn auf der Plaza sind.
CPP: A Standardized Alternative to AMP
It’s no secret that I have reservations about Google’s AMP project in its current form. I do want to make it clear, though, that what bothers me has never been the technical side of things—AMP as a performance framework. The community working on AMP is doing good work to make a performant baseline. As with any framework, there are decisions I agree with and some I don’t, but that doesn’t mean the work isn’t solid—it just means we have different ways of approaching building for the web.
Taking Let's Encrypt for a Spin
A lot of folks have been very vocally pushing for “HTTPS Everywhere”, and for good reason. The fact that the lack of HTTPS makes you miss out on shiny new things like HTTP/2 and Service Workers adds even more incentive for those a little less inspired by the security arguments. Unfortunately, moving to HTTPS can be kind of painful as you can see from Jeremy Keith’s excellent post detailing exactly how he got adactio.com onto HTTPS.
AMP and Incentives
Incentives are fascinating. Dangle the right carrot in front of people and you can subtly influence their behavior. But it has to be the right carrot. It has to matter to the people you’re trying to influence. Just as importantly, it has to influence the correct changes. A few years ago there was a story of incentives gone wrong that was making the rounds. The story was about a fast food chain that determined customer service was an important metric that they needed to track in some way.
Understanding Proxy Browsers: Architecture
I did a bunch of research on proxy-browsers for a few projects I worked on. Rather than sitting on it all, I figured I’d write a series of posts sharing what I learned in case it’s helpful to anyone else. This first post looks at the general architecture of proxy browsers with a performance focus. In the original story of the Wizard of Oz, the Emerald City isn’t actually green nor made entirely of emeralds. All of that came later.
Choosing performance - TimKadlec.com
Facebook just announced a new feature they’re calling “Instant Articles”. Facebook is positioning this as a way for publishers to have their stories displayed, within Facebook, “instantly”: Now before we wring our hands too much over this, it’s worth noting that the articles themselves still start on the web. Facebook just becomes a distribution platform. Here’s the exact statement from their FAQ’s (emphasis my own): From Facebook’s perspective this is a no-brainer.
Apple's Web? - TimKadlec.com
The Pointer Events specification just became a W3C Recommendation. For those unfamiliar, it’s an intriguing attempt to unify pointer events regardless of the input device in use. The jQuery team threw their weight behind it this morning. Unfortunately, as they went on to point out, there are some hurdles to jump yet. While Microsoft has a full implementation in IE11 and Mozilla is working on it, Apple has shown no interest and Google seems ready to follow their lead.
JS Parse and Execution Time
September 26, 2014 # performance javascript At Velocity NY, Daniel Espeset of Etsy gave a great talk about how Etsy profiles their JavaScript parse and execution time. Even better, after the talk, they released the tool on GitHub. Daniel shared a few examples in his deck, but I couldn’t wait to take Daniel’s tool and fire it up on a bunch of random browsers and devices that I have sitting around. For this test, I decided to profile just jQuery 2.1.1, which weighs in at 88kb when minimized.
Responsive Responsive Design
Now more than ever, we’re designing work meant to be viewed along a gradient of different experiences. Responsive web design offers us a way forward, finally allowing us to “design for the ebb and flow of things.” With those two sentences, Ethan closed the article that introduced the web to responsive design. Since then, responsive design has taken the web by storm. Seemingly every day, some company is touting their new responsive redesign.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Tim
Contact Tim, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack