News for hackers. Stuff that matters.
Re:Our best practices are killing mobile web performance by petercooper on Saturday May 21, 2016 @12:14PM (#11745162)
Why isn't there a way for devices to indicate to a server if they are on a slow or data-capped connection?

There is. I'll update this post if I remember what it is, but I believe there's a spec and Chrome Canary is supporting it. It uses an HTTP header.

Re:Our best practices are killing mobile web performance by sillysaurus3 on Saturday May 21, 2016 @12:19PM (#11745188)
Rather than rely on specs or browser support, why not simply measure how quickly data is being downloaded?

That wouldn't help on the first page load, but it would make the information available on subsequent loads.

Re:Our best practices are killing mobile web performance by toomanythings2 on Saturday May 21, 2016 @12:41PM (#11745260)
Navigation Timing API https://developer.mozilla.org/en-US/docs/Web/API/Navigation_...

I have a feeling there is something else but I have trouble remembering it, too, and I bet I have it bookmarked to study when I have the need to use it.

Re:Our best practices are killing mobile web performance by petercooper on Monday May 23, 2016 @04:17AM (#11752551)
That's a good one, but it wasn't that.

It's something that literally gets clients to add an HTTP header to specify that bandwidth should be "saved".

Actually, that reminded me of what it was called.. haha, it's https://developers.google.com/web/updates/2016/02/save-data?... .. The header is: Save-Data: on.

Re:Our best practices are killing mobile web performance by petercooper on Monday May 23, 2016 @04:18AM (#11752552)
It's this: https://developers.google.com/web/updates/2016/02/save-data?... .. the header is: Save-Data: on.