#### Key Result: Improve LCP performance of at least one page for each team as identified by the following report https://docs.google.com/spreadsheets/d/19VENf6d54vuQn7RWjGbA4j2yCgjnNnHHzZ0FZqgonPU/edit#gid=0 [Largest Contentful Paint](https://web.dev/lcp/) (LCP) is a measure of how much time it takes to load a page to a point where a user can interact with it. We should work with our product counterparts to identify poorly performing page(s) and include those pages in the regular prioritisation conversation. | Group | Page | Issue | Scheduled Milestone | Complete | | :--- | :--- | :---- | :------------------ | :------- | | ~"group::configure" | Monitor Clusters | https://gitlab.com/gitlab-org/gitlab/-/issues/296929 | 13.8 | :white_check_mark: | | ~"group::package" | Container Registry Index Page | https://gitlab.com/gitlab-org/gitlab/-/issues/280847 | 13.8 | :white_check_mark: | | ~"group::release" | releases | https://gitlab.com/gitlab-org/gitlab/-/issues/238194 | 13.8 | :white_check_mark: | :question: | ## Retrospective ### Good * Well handled effort to address top issues in LCP ### Bad * Could have helped to be a bit more clear on the impact ### Try * [ ] For teams without significant gains from LCP work, better description of goals. /cc @sgoldstein