-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RUM-260] Support bfcache restore for web vitals #3357
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3357 +/- ##
==========================================
+ Coverage 93.02% 93.04% +0.02%
==========================================
Files 298 300 +2
Lines 7853 7883 +30
Branches 1789 1790 +1
==========================================
+ Hits 7305 7335 +30
Misses 548 548 ☔ View full report in Codecov by Sentry. |
Bundles Sizes Evolution
🚀 CPU Performance
🧠 Memory Performance
|
/to-staging |
View all feedbacks in Devflow UI.
Commit 2a94df54cb will soon be integrated into staging-08.
Commit 2a94df54cb has been merged into staging-08 in merge commit 3291b7c64b. Check out the triggered pipeline on Gitlab 🦊 If you need to revert this integration, you can use the following command: |
…r web vitals Integrated commit sha: 2a94df5 Co-authored-by: roman.gaignault <[email protected]>
Motivation
Users navigating back to a page via the browser’s back-forward cache do not experience a full page reload. Therefore, initial performance metrics may no longer accurately represent what the user sees upon restoration. By capturing metrics specifically for bfCache restores, we gain a more precise understanding of user-perceived performance.
Changes
This PR introduces support for detecting and handling the Back-Forward Cache (bfCache). When a page is restored from bfCache (i.e., a pageshow event with persisted = true)
Testing
I have gone over the contributing documentation.