Background

As has been discussed in the past, the special page loads slower than ideal. It's been suggested that we investigate server side loading the page, or providing the data in the initial page request to reduce JS load time and make the page more performant to nojs users

Note that this isn't currently considered a prerequisite to the epic, so would potentially be unlinked from its parent task if we were to complete the hypothesis and decide to do this at a later date

User story

As a user with a low-to-moderate internet connection, I would like to be able to use the reading lists feature and browse my saved items without long loading times

Design requirements

N/A

Requirements

Acceptance criteria

• This is a spike - ideal outcomes include a proof of concept, writeup, and/or creation of subsequent tickets

QA strategy

• Risky change? Spikes should be no risk 🤞
• QA by: Likely engineering team, potentially product and design (possibly QS)
• QA in: N/A
• Test steps: review submitted findings of spike

Communication criteria

Please inform the team when you have finished this work

Rollback plan

Should be N/A