Description

During Q3 we conducted a detailed analysis of the Front End performance issues, origin and mitigation strategies.

For Q4 we propose working on a limited number of mitigation strategies from the ones identified in the analysis, focusing on those which:

• Require the least amount of effort
• Maximize impact
• Center around enabling the use of Wikidata features

The mitigation strategies suggested for Q4 are the following:

• To reduce number of components:
  • Measure 1.2: Render a limited number of items in every list
  • [Stretch] Measure 1.1. Remove unnecessary components
• To reduce component complexity:
  • T391133 Measure 2.2: Reduce complexity of nuclear getters by using Map
• Other improvements:
  • [Stretch] Measure 3: Namespace ZObject tables to remove the extra complexity of deleting Detached objects

Acceptance criteria

• At least one measure was implemented to reduce the total number of components.
• At least one measure was implemented to reduce the complexity of component data access.

OKR rescoping 09-06-2025

Due to low effectiveness of T391133: Reduce complexity of nuclear getters by using Map instead of an Array for the flat ZObject representation on performance, we've decided to solve the root issue:

• T396360: Front End Performance: Migrate ZObject internal representation from flat table to nested object

Acceptance criteria

• Front-end load times visibly improve
• UI can load an expanded Q144 wikidata object in a reasonable time with no browser crashes
• There's no functionality loss in the UI

Completion checklist

• Before closing this Epic, review one by one the checklist available here: https://www.mediawiki.org/wiki/Abstract_Wikipedia_team/Definition_of_Done#CUJ/Epic_completion_checklist