<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal During our ~"Performance Round Table::Source Code" the question about the order in which we request the blob content information came up. It seemed like the blob content came after many many requests. However, inspecting one example (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.rubocop_todo.yml) seems like we do get the content in the Blob info request (which is requested in StartupJS). <img src="/uploads/36dd9bcdc6d4becbcb5efe9a4426c88b/Screenshot_2023-03-28_at_18.01.48.png" width="400"> Perhaps the example we saw in the call was a fallback to a rouge-rendered syntax highlighting? Regardless, let's confirm we're requesting the blob content as soon as possible. <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->