@patmeenan@tunetheweb@SimmerVigor@hnasr To derail further: there's also the fun that's been had with *uncompressed* PNGs but serving them with brotli and seeing improvements. Like https://t.co/4oClXVaFrA and https://t.co/zrKi4Q97NO
All browsers since 2017 support Brotli as an HTTP-level compression, using Content-Encoding: br
And we can create PNGs in an uncompressed format. So we can serve uncompressed PNGs with Brotli compression.
It's a bit more compact than planinPNG in my unscientific survey of 1 file
@Lakbychance@tunetheweb@____lighthouse I added an explanation on the removal of TTI to https://t.co/7zJVz47CI7, but FWIW I think you already have the case against TTI exactly right :)
@GrahamTheDev@____lighthouse Yeah, there should have been more detail in the post. I just added some explanation of TTI's removal in https://t.co/7zJVz47CI7. Let me know if that helps make it clearer.
@patmeenan@tunetheweb@juan_ferreras_@RealWebPageTest@HTTPArchive It's enabled by default so should be good to go for the March HTTP Archive run. It appears that there are sometimes issues with running it with --headless (you get an extra failure reason about using window․open()) that's being looked into
@addyosmani@RReverser@Paul_Kinlan I can't find the tweet I learned it from now, but you can sometimes get it to continue. Something like "Your answer got cut off. Continue your response starting with 'To save...'"
@torturecrush the articles out there are *so* useless. youtube is much better for demos (caveat: I was only semi-successful as a first time grower this year). I used this method: https://t.co/DRkum5JBQ0 and like his, they could have used longer, but still good in the center
@hankchizljaw From your description and running the demo, it really is a layout shift that's happening. Are you asking if this technique is possible to do without a layout shift, or if this shouldn't be penalized because it's a tradeoff for progressive enhancement?
@ryanflorence Just remember diagnostics don't impact the Lighthouse perf score, they're there to help break down what's going on with a metric. So if delayed font display was dragging down FCP, the only penalty is the measured FCP delay.
@tom_forsyth Stumbled across it a few years ago and (as a Texan) was *very* surprised. Somewhat unique flavor profile as well, would be interested in what you'd compare it to.
Drama behind the scenes: https://t.co/i2dt5SdQQQ
@j_holtslander @ChromiumDev otherwise do you mind filling out https://t.co/57TNl0GQn7 and we can do a more in-depth attempt to reproduce than just a trying it out on a spare test phone?
@j_holtslander @ChromiumDev Yeah, that's odd. Maybe it's the in-app browser? Content blocker? Do you see the same thing opening https://t.co/bJnUZ3PuXu in the default mobile Safari? The text input is baked into the served HTML so doesn't depend on JS to appear