-
Notifications
You must be signed in to change notification settings - Fork 397
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
Add visualization of 3rd party requests #43
Comments
I think this is adding too much complexity to the tool. Bare in mind that we're not trying to replace WebPageTest, which is why I think it was a great idea to add links to the WebPageTest result pages. If people want to go into so much level of detail into the nature of their requests, they should probably look at the waterfall view and others provided by WebPageTest. |
Problem is that WebPageTest doesn't shown any trends over a period of time. That's where a visualization tool like speedtracker is very handy. I am part of retail organisation where marketing teams keep adding 3rd party tags without providing any visibility to tech teams and sometimes these tag can slow down site. By bringing a trended view of 3rd party requests on a dashboard like this, we may be able to spot any co-relations (if any) easily and also keep an eye what's going on site when it comes to 3rd party requests. |
Great concept but the tool supports deep links to insights on WPT. This allows dashboards to remain approachable and easy for anyone to use. Power users wishing to gain more insights can drill into the waterfalls on WPT and do more analysis as needed. So unless WPT is expiring deep links very, very rapidly (if at all), I'm a 👎 on this request. |
It will be good to create a visualization on 3rd party requests or add this metric as part of 'content breakdown' graph.
Reason - Most of the time site webmasters have very little control on what 3rd party requests are being included on their site due to usage of technologies like tag managers etc. Adding a visualization for this can help them track any increased in 3rd party requests on their pages.
Point to consider - Many sites use CDN for images. So some request may look like third party (by just looking at domain) but actually those will be first party requests.. So we should look at providing ability to white-list domains as part of their profile setup so that any requests with white-listed domains can still be counted as first party requests.
Thoughts on this?
The text was updated successfully, but these errors were encountered: