We are making a site in Razor Pages using .NET Core 2.1 and are using code first EF Core, dependency injection and iDesign and all the cool conventional ideals. We started it half a year ago and are still working on it. The database it pulls from is small; 5 or 6 columns averaging 10 or so entries per SQL call; about 10 tables. Our entire site is only around 30 MB.

As I try to test it, it takes over a minute after the project built to show up on the screen and each page I click on just has to load a table or a 8ish field form and it takes anywhere from 30 seconds to a minute after the click to load while debugging. I try to do some of the SQL statements it does to see if its just bad indexes but those all finish in well under a second. We have refactored and refactored to the point where we are over budget. It is a basic CRUD site that will need to utilize multiple page loads and while its not incredibly slow on the servers it is quite a few seconds from when you click on a link to when it loads, maybe 10 or so... basically a lifetime in internet time.

So as many of you know, in Chrome you can load a page and it would tell you how long different steps take and with that you can see what thing took a long time and eliminate it. Is there anything like that for .NET Core? I don't know if there is some sort of tracer we can have running on the backend that will tell us what our slow point is. I know Azure has some tools but we are just running this on servers my company manages.