Draft: Resolve "Frontend performance review"
What does this MR do and why?
Describe why, not just what. Include links to relevant issues or discussions.
This MR aims to improve performance of the new.docs.gitlab.com site.
Issues are as follows:
-
Unused css can slow down performance. In this case we have index.css as the culprit. The issue is when there's a lot of unused css the browser still has to go through each one to ensure the proper stylings are added to the nodes in the render tree. The more unused css, the longer it takes for the browser to do this job. Since index.css adds styling globally and is part of gitlabUI we can't do much about this.
-
Reduce unused javascript. Not really possible because it's picking apart the google_search file itself (unused methods, etc).
Screenshots, screen recordings, or links to review app
These are strongly recommended to assist reviewers and reduce the time to merge your change.
CURRENT:
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
-
Configure a local GitLab Docs environment: https://gitlab.com/gitlab-org/technical-writing-group/gitlab-docs-hugo/-/blob/main/doc/setup.md.
Merge request acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this merge request.
Closes #50 (closed)