Conversation
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
|
trieloff
left a comment
There was a problem hiding this comment.
Do you think it would make sense to move redirect handling into a plugin? I think we get to a page trough redirects on less than 5% of pages.
|
This PR will trigger a minor release when merged. |
1569f38 to
b307546
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
01a50d6 to
7d36320
Compare
|
@trieloff I was able to pick this up and update the code with your recommendations. Once we have this deployed and live data flowing in, I'll work on updating the OpTel dashboard accordingly. |
|
|
🎉 This PR is included in version 2.45.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Use Case
As a marketer, I want to know how redirects impact my performance scores so that I can avoid undesired redirect chains.
Problem
At the moment, the OpTel Explorer only reports on internal redirects, not external ones. We've seen in customer discussions that external redirects could cause major increases to the TTFB that were hard to detect and debug.
Solution
Leveraging the
PerformanceNavigationTimingAPIs, we can track the time spent on external redirects before we land on the page, and can also estimate the number of redirects accordingly.Technically, the idea is to track the redirect count and time in the
targetfor theredirectcheckpoint:<redirectCount>:<redirectTime>for internal redirects<estimatedRedirectCount>~<redirectTime>for external redirectsReferences
adobe/helix-website#1011
See background discussion in https://cq-dev.slack.com/archives/C07198KKQ07/p1761333727781429
Test URL
https://redirect-time-tracking--helix-rum-enhancer--adobe.aem.page/test/fixtures/otsdk-with-banner.html