1603189 - Suggestion, add 'slow site' indicator on URL bar for sites with 'blocking resources' or sites using HTTP 1.1

Status: NEW

(DevTools :: Netmonitor, enhancement, P3)

Description

[Wellington Torrejais da Silva]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0

Steps to reproduce:

Suggestion, add 'slow site' indicator on URL bar for sites with 'blocking resources' or sites using HTTP 1.1

• Open websites
• See performance problems
• Open about:networking#http
• See many "HTTP <= 1.1" requests

Links:

• https://developers.google.com/web/fundamentals/performance/critical-rendering-path/render-blocking-css?hl=pt-BR
• https://web.dev/render-blocking-resources/

Actual results:

• People think the browser is the origin of page load speed problems.
• Other browsers do tricks and "magics" using servers, AMP, and other non trivial ways to optimize de loading time.
• Firefox is non profit, and can't use same tricks.
• I suggest ways to indicates real page problems to the user.

Expected results:

I think the simple page slow indicator can tell the users the real cause of page loading speed problem.

Thanks!

Comment 1

[Seba S.]

Hi, Wellington Torrejais da Silva!

Thanks for your contribution!

I am adding product and component on this one to keep on track.

Regards,

Comment 2

[Florian Quèze [:florian]]

This feels more like something for developers than something we could expose to general users.

Comment 3

[Hubert Boma Manilla (:bomsy)]

Attachment: slow-request-indicator.png

Hi Wellington,
We have the slow request indicator for individual requests in the Netmonitor. It shows as a turtle icon in the file column and a little bit more detail on hovering over the icon.

You can also control the threshold for slow requests by adjusting the pref devtools.netmonitor.audits.slow. I think the default is 500ms.

Does that look like what you need?

Comment 4

[Wellington Torrejais da Silva]

Hi Hubert,

I like the turtle indicator in the Net Monitor. But that suggestion is more related to an indicator for common users, in the URL bar.
And in that case the original suggestion idea is based on the NetMonitor indicator but is different because I'm thinking in a indicator based in another rules, like the use of non actual HTTP protocols for example.

Thanks for the attention!

Comment 5

[Wellington Torrejais da Silva]

For example, the indicator of slow site, could be showed in the cases on the site don't using Gzip or other type of compression algorithms.
The ideia it's tell the user about the site slow and indicates with it's not a browser slow problem.

Thanks!

Comment 6

[BugBot [:suhaib / :marco]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:Honza, since the bug has recent activity, could you have a look please?

For more information, please visit BugBot documentation.

Comment 7

[Hubert Boma Manilla (:bomsy)]

(In reply to Wellington Torrejais da Silva from comment #4)

Hi Hubert,

I like the turtle indicator in the Net Monitor. But that suggestion is more related to an indicator for common users, in the URL bar.
And in that case the original suggestion idea is based on the NetMonitor indicator but is different because I'm thinking in a indicator based in another rules, like the use of non actual HTTP protocols for example.

Thanks for the attention!

Thanks for the response. I see your point here, you mean an indicator for slow requests which are not necessarily just impacted by browser related factors but other non-browser related things (e.g no compression, other server optimizations). It might nice to also provide some details/suggestions in maybe tooltip around the slow areas.

Comment 8

[Julian Descottes [:jdescottes]]

For end users, a good way to communicate about such issuees would be via the webcompat issues reporting tool.

As far as devtools are concerned, it could still make sense to warn about missing optimizations. We could:

• reuse the "turtle" indicator but show it in more situations, with tooltips to explain why it is displayed
• enhance the Performance Analysis tool in the netmonitor to show more details about the requests
• bundle this information in a lighthouse-like tool

ni to Honza to check for the webcompat part.

Comment 9

[Jan Honza Odvarko [:Honza] (always need-info? me)]

For example, the indicator of slow site, could be showed in the cases on the site don't using Gzip or other type of compression algorithms.
The ideia it's tell the user about the site slow and indicates with it's not a browser slow problem.

Thank you for the comment!

This is close to our discussions about ways users coulr report issues with sites in Firefox. The category "slow" is frequently used by users when they report a broken site via "Firefox Menu -> Report Broken Site."
Firefox could potentially detect such cases automatically and open a user interface to assist the user in understanding and/or submitting a site issue report. Although I'm unsure if displaying a "slow" icon in the address bar is the best approach (it feels more like something for developers not for regular users), it falls within the same domain of ideas.