Good grief. There’s a table full of data, but it doesn’t fit on my phones screen, and I can’t scroll because that triggers some page translation bullshit. Thanks for nothing. Why do I want to take web site advice from somebody who can’t get their own site to work?
Anyway, I think the numbers are suspect. I can believe that you hit a slow request one in 69 loads. But I don’t think it’s fair to multiply that by 42 or whatever, because many of those assets are going to be cached, and more importantly, their 99% is going to be different than the app’s 99%.
I’m assuming %'lie is his cute way of abbreviating “percentile” and simultaneously making a joke. Honestly, his point is very good for sites that serve modern web apps. However, since most of those requests are for static content, I as a developer am probably not going to be so concerned with them. But if your app is an SPA, this point is probably a lot more important.
1% of HTTP requests are above the 99th percentile for HTTP requests. >50% of page views that involve >69 HTTP requests will include at least one HTTP request above the 99th percentile for HTTP requests. It’s common for a page view to include dozens of requests nowadays.
That should have been the first paragraph of his essay or at least the table of contents. He could learn to express himself better. But then, so could I.
I think his claim is a bit debatable, since the vast majority of those dozens of requests use far-future Expires: headers and change the filename when they change, and besides that, many of them are things like page-end scripts and inline images that can load after the page is visible and so probably shouldn’t count. But whatever.
Good grief. There’s a table full of data, but it doesn’t fit on my phones screen, and I can’t scroll because that triggers some page translation bullshit. Thanks for nothing. Why do I want to take web site advice from somebody who can’t get their own site to work?
Anyway, I think the numbers are suspect. I can believe that you hit a slow request one in 69 loads. But I don’t think it’s fair to multiply that by 42 or whatever, because many of those assets are going to be cached, and more importantly, their 99% is going to be different than the app’s 99%.
What’s a %‘lie?
I’m not actually sure what he’s trying to communicate. This is a joke right? Maybe we’re supposed to have fun lampooning the site.
Per the definition of percentile, shouldn’t 1% of page loads be in the 99 percentile?
I’m assuming
%'lieis his cute way of abbreviating “percentile” and simultaneously making a joke. Honestly, his point is very good for sites that serve modern web apps. However, since most of those requests are for static content, I as a developer am probably not going to be so concerned with them. But if your app is an SPA, this point is probably a lot more important.1% of HTTP requests are above the 99th percentile for HTTP requests. >50% of page views that involve >69 HTTP requests will include at least one HTTP request above the 99th percentile for HTTP requests. It’s common for a page view to include dozens of requests nowadays.
That should have been the first paragraph of his essay or at least the table of contents. He could learn to express himself better. But then, so could I.
I think his claim is a bit debatable, since the vast majority of those dozens of requests use far-future Expires: headers and change the filename when they change, and besides that, many of them are things like page-end scripts and inline images that can load after the page is visible and so probably shouldn’t count. But whatever.