The blue line is just a redesign of the previous loading throbber (spinner) animation, see  issue 822067 .
It first landed at 72.0.3599.0 and didn't introduce any performance variation in my experience.

For me the slowdown started right at 72.0.3601.0.

I believe this issue inhabited in 3601 branch only. Reporter, can you please verify in latest builds whether there is no slowness for you as well?

Yesterday Google Canary was crashing when I tried to open any tab. So I uninstalled it and did a fresh new install. Today I have latest version and the issue seems to be getting worse, loading seems to be even more slower now in all websites.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tried checking the issue on reported Chrome version 72.0.3601.0 using Windows 7 and Windows 10, but didn't notice any significant delay in loading the web pages.

From comment#1 of  issue 822067  cc'ing the owner of the particular bug for further inputs, as it is assumed the delay is being caused after introducing blue line on the Favicon Icon at the time of page loading.
Tentatively adding component "Internals", please change if this isn't apt.

Thanks!

+edwardjung@ as this might be perceived differences w/ new loading animation. I think showing the favicon earlier in the loading process can be perceived as a slower load since users think the load has finished way earlier than it actually has.

There's a bug that causes us to show the tab as loading way earlier than a connection has been made, see  issue 903817 . Since that shows up as 0% load progress the indicator can feel stuck for sure.

What pbos@ says. The total duration of the loading animation is the same as the spinner since the logic hasn't changed. Actual page load speed hasn't changed unless there is a regression elsewhere in the code base.

This has much to do about the perceived load speed when the determinate indicator isn't moving, it can feel slow, whereas previously you just saw the endless spinner. Wee are aware of a number of issues and are continuing to refine this new design.

@bustyasianescorts2 out of curiosity are the tabs loaded in the background or the active tab that feels slow or just all tabs. 

Reporter, can you make screen recordings of Chrome 72 and 71, both using new profiles?
Because without objective time measurement this issue is moot.

FWIW perceived delays are also important, we know that the loading indicator can appear stuck because representing 100% load progress in 16px is hard. The prior animation did not represent load progress but kept spinning.

@reporter: As per comment#10 could you please provide screencast of the issue with observations so that it would be really helpful for triaging the issue.

Thanks.!

What tool do you suggest to use to give you the following results. (I'm using PC not MAC)

I tried using webpagetest but I am not getting accurate results that I would be happy to pass on to you.

Also with regards to comment 11, I have seen some websites loaded and the line in the favicon seems to "hang" and not finish the same time.

Is the loading line set to something like Time to Interactive (TTI) before it disappears?

Would be interested to know what metric you are using before the loading line disappears, then I can run some more tests to try and pin point the reason why you?

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I have made a video using Google Canary V73. If you look at the favicon on the FIRST load, you will see the web page loads and then there is a "hang" in the favicon loading displays and it still looks like the webpage is still loading, due to the loading indicator not finished doing its thing! Makes the web page feel like it taking longer to load.

However when you refresh the web page, this issue does not appear!

So there is an issue on the first load with regards to "perceived delays"

-------------

My issue on my clients websites are not that, they just seem to take a longer time loading. I'm thinking it's something to do with all the pre-rendering, preloading and service worker. I have a lot of lines of code running on these things. So I need to investigate further to try to find the bug for you? It just seems like a longer time showing a grey screen before the First Byte is loaded.

Hopefully this helps with feedback with the "perceived delays" at least.

Deleted: Untitled.mp4 1.1 MB

	Untitled.mp4 1.1 MB View Download

Thanks for the clarification. We are aware of the slight pause you get and we're looking to get that smoothed out, particularly on fast loading sites in your example.

Merging into an existing bug which is all about the perceived speed. 

Please file another bug for your issues around the real load speed of your app.