Skip to content

Commit

Permalink
Update _posts/2024-08-20-js-nation-react-summit-2024.md
Browse files Browse the repository at this point in the history
Co-authored-by: Pascal MARTIN <[email protected]>
  • Loading branch information
fdubost and pmartin authored Aug 20, 2024
1 parent 20b09ce commit 43f376a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _posts/2024-08-20-js-nation-react-summit-2024.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ At Bedrock, we've always tried to apply a maximum of [best practices](https://te
Vinicius addresses an important subject for us, as frontend engineers. We are all concerned about performance and we want to deliver the most optimized product, but we often come up against major obstacles in this area. We already talked about this topic last year when [we attended the We Love Speed conference](https://tech.bedrockstreaming.com/2023/08/11/we-love-speed-2023.html).

To prove values of performance work, **Lab tools** (like [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview?hl=fr)) & **RUM** (Real User Monitoring) has to been used together. Data collected must be analysed, optimised and framed to make connections with product concerns. Performance needs to **matter to engineering and product** for a sustainable governance model.
To prove values of performance work, **Lab tools** (like [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview?hl=fr)) & **RUM** (Real User Monitoring) have to be used together. Data collected must be analyzed, optimized and framed to make connections with product concerns. Performance needs to **matter to engineering and product** for a sustainable governance model.

As in many areas, the key is to set realistic and achievable objectives and to proceed by iteration: **monitor, measure, report and repeat**.

Expand Down

0 comments on commit 43f376a

Please sign in to comment.