Thread 106285737

Thanks to bots and cloudflare, browsing the internet now feels slower than it did in 2005. Thanks for all the bandwidth that has become useless.

It's nothing to do with bots and cloudflare, it's slow now because every big company's website has 50MB of downloads per page in a dependency graph where the shortest path is 100 requests.

>>106285816
This and more importantly very little adoption of Jpeg-xl and AVIF.

>>106285816
Bots and DDOS are a thing, but website inefficiency is peak DEI.

>>106285841
AVIF will slow page loads down while making them look worse you dumb fuck.

>>106286124
46% of all Android phones are now using Android 14 or 15. Mandatory HW AVIF support began with Android 14.

https://gs.statcounter.com/android-version-market-share

>Encoder and decoder are mandatory beginning with Android 14.

https://developer.android.com/media/platform/supported-formats

>>106286124
Not on modern hardware and whether it will make things look worse is going to depend on what kind of image. That's why I mentioned both Jpeg XL and AVIF because sometimes one will do a much better job than the other.

HOWEVER it's worth noting that JPEG XL replaces PNG and GIF.

>>106285737 (OP)
our most cracked developer is working on it. he assures me that the 10k lines per day he's helping claude add to our codebase will make our site faster for you.

>>106286285
My piece of shit shipped with Android 14. No HW AV1 support.

>>106286586
I think the hardware decoder used for AVIF images is different than the one used for actual AV1 video. Testing for this shouldn't be too difficult, you only need say a high resolution 4K AVIF image like this one.

https://files.catbox.moe/uafv5j.avif

How quickly did that load on your phone? If it loaded in like 0.1 seconds then congrats you have AVIF hardware decoding but for some retarded reason no AV1 video hardware decoding.

>>106285816
This. Modern webdevs and corpos are fucking cancer.

>>106285816
>>106287023
Oh, and as an example of one of my most hated websites, canadiantire.ca is bloated as fuck and requires *257* requests WITH ADBLOCK to load. Without adblock it pushes about *400* requests for the initial load, then it continues to make an additional request every 0.5s FOREVER while the site is open.

>>106287052
Lmao. That's the worst one I've seen for a while.

>>106286285
there's nothing good about crippling old hardware arbitrarily like that.
i could load jpgs and gifs on my 486 with a 14.4 modem faster than a lot of modern sites on modern hardware, so i don't think those are the problem

>>106286968
Wtf. You're right, it loads instantly. It took longer to download than actually decode.

>>106287101
You can still soft decode it via DAV1D so PC users with 10 year old hardware probably aren't going to complain. Hardware decoding is really only a concern on phones that are 10% as powerful as actual computers. You know since they operate on milliwatts of power and whatnot. Kinda hard to cheat the laws of physics there.

https://openbenchmarking.org/test/pts/dav1d

>>106287052
Canadian Tire usually doesn't even load for me not until like 2 minutes later

>>106287189
And everyone provides fallbacks anyway for incompatible browsers, people on old hardware that don't want to cpu decode can just disable the avif support in the browser to get the fallback, alternatively an extension could just pick the fallback if there is one and put up with the avif if there's none. People do this with av1 videos already

>>106287093
And the amount of layout shift is insane

>>106287339
Kind of unnecessary unless you got like a fucking atom computer. Like yeah I get the freedom of choice thing but I dunno man, if that leads to us still using JPEG and H264 in 2030 when computers and phones are 10X faster than they are now, it kind of seems like a grim future desu.

https://streaminglearningcenter.com/codecs/tesla-rolls-back-youtube-from-av1-to-vp9.html