Prioritize static content

JoYo

This goes along with showing the GET size of a result.
If a result contains the content queried and has a smaller GET size indicating static content it should be prioritized.

Vlad

JoYo Can you give an example?

JoYo

wget https://en.wikipedia.org/wiki/Pointing-out_instruction
--2023-07-10 13:44:16--  https://en.wikipedia.org/wiki/Pointing-out_instruction
Resolving en.wikipedia.org (en.wikipedia.org)... 208.80.154.224, 2620:0:861:ed1a::1
Connecting to en.wikipedia.org (en.wikipedia.org)|208.80.154.224|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘Pointing-out_instruction’

Pointing-out_instru     [ <=>               ] 132.83K  --.-KB/s    in 0.04s

2023-07-10 13:44:17 (3.36 MB/s) - ‘Pointing-out_instruction’ saved [136019]

wget displays the rate and the total size of the GET result.

since this is historical data it would only be the total size of the last time the index performed the GET.

it should be available in the WARC archive https://en.wikipedia.org/wiki/Web_ARChive

Vlad

JoYo Note that JS heavy pages will have smaller GET size, as most of the "crap" is loaded dynamically with JavaScript. So it is not clear how would the GET size of a page be useful as a factor in ranking?