Default display of source code in result page

{{Edit request}}
Currently, only Large SVG files – when parameter < is specified – don't display the file source code on the target page (&doctype=Inline), while any other SVG does (&ss=1); also, the anchor #source included by default makes the page jump to the Source Listing section, which implies having to scroll-up to read the status.
It would be easy to consider that displaying the source code of a file hosted here on a separate website could be moot, but above all, currently every click on the "valid / invalid" link increases the traffic disproportionately, as each validation uses twice the amount of data transfer required, with benefits yet to be demonstrated.
Moreover, there are many weighty files (300kb, 600kb, 1Mb, 6Mb… - examples abound) that don't have the Large SVG file parameter set, so one solution would be for the module not to display by default the source code on w3.org, otherwise large or weighty files should be tracked to prevent this and reduce global traffic load; it's possible to force the source code not to be displayed for not really large files by adding o=O or o~0 (Igen/IgenCoa) (oro=n, or anything), i.e. without categorizing files in Cat:Large SVG files, but this solution would leave many files as is since it's not possible to fix them all.
So, I'm submitting an {{Edit request}} to get support on solving this issue, being aware that what I've done in the sandbox is propably not safe.
--Kontributor 2K (talk) 20:05, 14 January 2025 (UTC)

Are you sure just passing the showsource parameter causes it to request the data twice? I would think that they would only request it once, put that into cache, check the cache, and then display the same cache.

Also, you have to type out {{edit request}} with the brackets to do an actual edit request. The linked version of the template is for deactivating edit requests. I've added the template to the top of this section. Aaron Liu (talk) 14:30, 18 January 2025 (UTC)

Thank you,

As a matter of fact, if the source code is displayed, the issue is that the result page will be as heavy as the file… thus, at least twice the amount of data actually required for validation is globally transferred (u + d), example with this file with which a 1.6Mb result page is received while it's just 16Kb when the source code is not displayed; this could be considered a global waste of bandwidth, in addition to the impact on w3.org's servers and, incidentally, on our browsers' cache. The question of users with reduced bandwidth can also be raised. --Kontributor 2K (talk) 15:26, 18 January 2025 (UTC)

Makes sense. Aaron Liu (talk) 17:27, 19 January 2025 (UTC)

 Done --Kontributor 2K (talk) 12:48, 11 February 2025 (UTC)