Open dontcallmedom opened 10 years ago
Some investigations for the http/https proxy approach:
The difficulty would be to link the intercepted requests to a specific initial page; I thought we could have the proxy run on a different port for each page, but Chrome doesn't seem to have the architecture to allow per-tab proxy settings. So this would require starting a new Chrome (with a separate user-data-dir) for each page checked; maybe that's OK.
Another approach would be to do it client side, with the Resource Timing API; but for security purposes, it hides cross-origins detailed information.
Maybe Resource Timing used via a Chrome extension would get us there, though (that's how the Chrome dev tool network panel is built apparently.)
One of the primary UX improvements for mobile devices is reducing the usage of network, both from a latency and bandwidth perspective.
The checker should help identify the places where one can get the biggest gains in terms of network usage. These includes: