[webkit-dev] Question regarding priorities of subresource content retrieval

Tue Feb 8 01:59:32 PST 2011

The bug seems similar, but the fix proposition is different.
The main point being that subresources from the main domain/subdomain
are highly probable to be relevant to the first render, but
external-domain subresources are much more likely to be completely
irrelevant to the content, being mostly trackers/analyzers/ad
functional scripts.
Thus, prioritizing the subresource loading order should have the
correct effect of reducing time to first render, without sacrificing
important content.

--
 silvio

On Tue, Feb 8, 2011 at 4:32 AM, Tony Gentilcore <tonyg at chromium.org> wrote:
>> ------------------------testlag.html---------------------------
>> <html><head>
>> <link href='http://127.0.0.1:4004/4000' rel='stylesheet' type='text/css' />
>> <body>
>> <script src='http://127.0.0.1:4004/4000' charset='utf-8'
>> type='text/javascript'></script>
>> Each http://xx.xx.xx.xx:xx/<ms> request gets delayed by
>> <ms> milliseconds.
>> </body></html>
>> -------------------------------------------------------------------------
>
> Excellent test case. This looks the same as the one filed at
> https://bugs.webkit.org/show_bug.cgi?id=45072. I agree there is an
> improvement to be had here. There is a discussion of some of the
> subtleties in that bug. For instance, we'd like to make sure we don't
> hurt first paint time in order to improve the time of the load event.
>