Current time: 12-06-2019, 05:56 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
a big F to First Byte Time
01-20-2012, 03:41 PM
Post: #1
a big F to First Byte Time
Despite implementing the recommended changes to IIS, we still get this disappointing result. Any idea how we could improve further?

http://www.webpagetest.org/result/120120_YR_2Y2K3/

FYI, we have recently done the following:
1. to set the expiration of web site content;
2. enable compression in IIS;
3. Creating a Web Service Extension (WSE) and map to gzip.dll (HTTP Compression)
Find all posts by this user
Quote this message in a reply
01-21-2012, 12:31 AM
Post: #2
RE: a big F to First Byte Time
The first byte time is going to be a function of your application and not related to the configuration of gzip, caching headers or any other "front end" stuff.

Do you make any database calls or calls to external services? Those are the usual candidates but it could be a bunch of stuff. There are some tools that can help you get visibility into the back-end bottlenecks but it's not something we have visibility into from the outside. I'm partial to New Relic but Dynatrace is also a good solution (I believe both support .Net).
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)