AlaskaAirlines / AlaskaAirlines/WebCoreStyleSheets

SPIKE: TRD for Pre-font deployment performance testing

Open
#273 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auro-wcss not-reviewed Type: Feature
Dominant language
SCSS
Stars
9
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.

Write TRD with collaboration from Content on how to set up and execute this test. cc @

In order to meet our Ecomm Performance goals for the Production website, Auro needs to participate in load testing of new fonts before Content team can proceed with loading them.

GOAL: Verify that loading the new fonts for 700 weight in addition to all the existing fonts in production does not change existing LightHouse scores for performance.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

Exit criteria

@ had the idea:

  • could test this easily. Using a 'fake' production page (in order to replicate Tealium issues), reference at least 1 of the fonts, look at the dev tools - understand if it's loading what it needs and the lighthouse score does not change from before new font to after
  • record testing results to share with @ in order to unblock related tickets.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the issue's proposed fake production page and its requirement to replicate Tealium issues; inspect how the existing fonts are loaded in the WebCoreStyleSheets repository. Run Lighthouse before and after adding the 700-weight fonts, check the browser developer tools for loading behavior, and record whether the performance score changes so the results can be shared with Content.

Written by the indexing model from the issue text.

Assessment

Tech stack
scss
Domain
frontend, performance
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.