Bugzilla

(In reply to alex_mayorga from comment #45)
> I don't really know how to interpret these so please let me know if I should file a new bug.

I don't really know how to interpret those either.   :)

That looks like output from the bottom bar of the devtools "network" panel about how many requests there were & how expensive (in time & size) they were in aggregate, plus a few other basic page load metrics.

From the metrics you posted, DOMContentLoaded is probably the most relevant one there; if that's reliably higher in Firefox vs. other browsers (as it was in your comment above, 252 ms vs 171 ms), then that'd potentially be worth filing a new bug on, but mostly if it "feels slower" in Firefox (if you can tell that it's taking longer).

If there's not a meaningful difference that you can detect, I suspect it's not worth worrying about at this point.  (And as you noted, it's not exactly apples-to-apples comparison.)

(In reply to alex_mayorga from comment #45)
> I don't really know how to interpret these so please let me know if I should file a new bug.

I don't really know how to interpret those either.   :)

That looks like output from the bottom bar of the devtools "network" panel about how many requests there were & how expensive (in time & size) they were in aggregate, plus a few other basic page load metrics.

From the metrics you posted, DOMContentLoaded is probably the most relevant one to compare between browsers there; if that's reliably higher in Firefox vs. other browsers (as it was in your comment above, 252 ms vs 171 ms), then that'd potentially be worth filing a new bug on, but mostly if it "feels slower" in Firefox (if you can tell that it's taking longer).

If there's not a meaningful difference that you can detect, I suspect it's not worth worrying about at this point.  (And as you noted, it's not exactly apples-to-apples comparison.)