Re: [Bloat] How to "sell" improvement

[Jonathan Foulkes <jf@jonathanfoulkes.com>]

Hear, hear, the concept of having ‘simulators’ for typical heavy modern web pages is exactly what we need to get across the benefits of lowered bloat having a larger impact on page-load performance than ‘speed’.
Those simulated pages should report total page load time and maybe even how many objects we’re ‘missed’ due to bloat induced issues.

These sites can then be recorded as they perform on various types of lines and bloat and allow for a really impactful before/after video to be produced.

Here are my suggestions for candidate ‘sites’:

News Site front page, with mix of uniquely fetched text areas and images. Also, dozens of ad-like payloads sourced from multiple domains.
News ‘content’ can actually be a bunch of educational material on Bloat, why waste an opportunity to further the message ;-)

Shopping site with tons of images and other smaller payloads, generating >300 requests.
Again, content can be designed to further our message.

What do we need to do to move this forward?

I have an experienced graphic designer and web-master that I can direct to help with some of the content and creative work. 
But what we need first is some agreement on general scope and then a technical framework to achieve the desired outcome.

Cheers,

Jonathan


> On Nov 28, 2016, at 2:40 PM, David Lang <david@lang.hm> wrote:
> 
> On Mon, 28 Nov 2016, David Collier-Brown wrote:
> 
>> Yes, especially for
>> 
>> * the performance-reporting tools' own page and also for
>> * some well-known, moderately complex ones.
>> 
>> Not the minimalist Google front page, but perhaps a particular query...
> 
> First off, can we get people to nominate candidate pages?
> 
> Then, let's see if we can make a simulator for that page, so the test won't break when the website gets updated, something that has the same serialization issues hitting multiple sites and fetching a bunch of items of various sizes (ideally, but not neccessarily involving slight delays on the server before returning the objexts)
> 
> turn this test into a apache module so it's easy to use and isn't affected by system variations (and eliminates possible security risks by having the module not access anything on the system)
> 
> Then get this deployed a bunch of places.
> 
> David Lang_______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat