Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What do the colored bars in the Firefox net panel represent?

In the firefox developer tools, under the "Net" panel, resources that are loaded have their load time split into different colors/categories. These are:

  • DNS Lookup
  • Connecting
  • Blocking
  • Sending
  • Waiting
  • Receiving

What do each of these represent, and more specifically, does any of them accurately represent the amount of time that the server is thinking (accessing the database, running algorithms, etc)?

Thanks.

like image 246
Ken Avatar asked Apr 13 '11 16:04

Ken


People also ask

What does the menu bar look like in Firefox?

Pressing the Alt key temporarily shows the file menu bar and allow users to use any of its features. The menu bar is located above the Address bar, in the upper-left corner of the browser window.

What is colorways on Firefox?

What are colorways? Starting with Firefox version 94, you will be able to personalize your browsing experience with 18 exciting new Colorways themes that were carefully created in partnership with an industry color specialist. Each colorway presents its own individual bespoke characteristic.

Why is there a white bar at the top of Firefox?

First, could you check to make sure Firefox is not in full screen view: pressing the F11 key usually switches between regular and full screen view. Also, in full screen mode, sliding the mouse pointer up to the top should cause the toolbar area to slide down.

How do you change the color of the menu bar in Firefox?

All Replies (5) If you open the Firefox menu, select "Add-ons and Themes" and you will be able to choose from one of the other pre-installed themes or download a custom theme from the add-ons website.


2 Answers

You couldn't accurately determine what the server is doing as such, I'm afraid.

You can discount most of them except Waiting, however, as the rest occur before and after the server handles your request. What it actually does while you wait will be a 'black box'.

There may be some asynchronous operations taking place during Sending and Receiving, so again it's hard to be accurate but you can get a ballpark figure of the time the server is working and the time the request spends travelling back and forth.

EDIT

Rough Definitions:

DNS Lookup: Translating the web address into a destination IP address by using a DNS server Connecting: Establishing a connection with the web server

Blocking: Previously known as 'queueing', this is explained in more detail here

Sending: Sending your HTTP Request to the server

Waiting: Waiting for a response from the server - this is where it's probably doing all the work

Receiving: Getting the HTTP response back from the server

like image 191
Widor Avatar answered Oct 19 '22 06:10

Widor


The firebug wiki also explains these (see the Timeline section).

  • Blocking Time spent in a browser queue waiting for a network connection (formerly called Queueing). For SSL connections this includes the SSL Handshake and the OCSP validation step.
  • DNS Lookup DNS resolution time
  • Connection Elapsed time required to create a TCP connection
  • Waiting Waiting for a response from the server
  • Receiving Time required to read the entire response from the server (and/or time required to read from cache)
  • 'DOMContentLoaded' (event) Point in time when DOMContentLoaded event was fired (since the beginning of the request, can be negative if the request has been started after the event)
  • 'load' (event) Point in time when the page load event was fired (since the beginning of the request, can be negative if the request has been started after the event)
like image 38
Dave Neeley Avatar answered Oct 19 '22 06:10

Dave Neeley