TTFB is too BAD !
|
12-13-2016, 08:21 AM
Post: #1
|
|||
|
|||
TTFB is too BAD !
Dear Webpagetest Members,
I have a site : http://dalano.com/ Recently (about 2 weeks) my site is going to loaded very slow and it has been so slowly than before. Here is the result for webpagetest.org : https://www.webpagetest.org/result/16121...view_step1 You are watching that TTFB is very terrible :| . I have IIS 7.5 and Windows Server 2008 R2 with aspx website. What is your opinion about improving my page speed and solving my recent problem? Thank you for your cooperation. King Regards. |
|||
02-23-2017, 12:14 PM
(This post was last modified: 02-23-2017 12:19 PM by avalanch.)
Post: #2
|
|||
|
|||
RE: TTFB is too BAD !
CSS at the top and loading BEFORE any JS.
Move your JS as much as you can to the bottom and defer where possible. Fix 404 errors reported in the test... they have a red highlight. Specify image dimensions Optimize images Leverage browser caching You can find a in-depth report here. https://gtmetrix.com/reports/dalano.com/HTm5l33l |
|||
02-27-2017, 12:38 PM
Post: #3
|
|||
|
|||
RE: TTFB is too BAD !
(02-23-2017 12:14 PM)avalanch Wrote: Move your JS as much as you can to the bottom and defer where possible. avalanch, great suggestions! Could you explain more on the quoted one? As far i understand moving JS to bottom without defering will not accomplish much. The browser will be anyway waiting until it gets all js from the page (even if it's at bottom) to start rendering. |
|||
03-01-2017, 12:28 PM
Post: #4
|
|||
|
|||
RE: TTFB is too BAD !
This is something I'm still figuring out actually. I just out of common practice defer js at the bottom, so it should load after the page render finishes. If something breaks, I remove the defer.
|
|||
03-03-2017, 06:48 AM
Post: #5
|
|||
|
|||
RE: TTFB is too BAD !
The TTFB is all on the server side in the application code (the aspx). Unfortunately from the outside there's not much we can tell about why it is slow. Usually the main cause is slow/lots of database queries or calls to external services but it could be any of a thousand things. APM products like NewRelic can help you quickly find server-side issues.
The css files should be merged together into no more than 2 or 3 and as avalanch mentioned, moving the js to the bottom if it won't break the page can really help. The key is that if the UI actually depends on the JS to draw it then it won't make a difference. Browsers will paint before loading the JS at the bottom of the page if there is something to paint. |
|||
03-07-2017, 09:24 AM
Post: #6
|
|||
|
|||
RE: TTFB is too BAD ! | |||
03-08-2017, 09:19 AM
(This post was last modified: 03-08-2017 09:26 AM by avalanch.)
Post: #7
|
|||
|
|||
RE: TTFB is too BAD !
From gtmetrix...
Quote:Page Speed currently only detects image dimensions that are specified via the image attributes. If you are specifying the dimensions via CSS, then you can safely ignore this recommendation. For sites with little images, this shouldn't matter. But for sites trying to place 50 plus different images... then yeah, it would make a difference. Plus this can make a difference when ranking for "serve scaled images". |
|||
03-08-2017, 03:43 PM
Post: #8
|
|||
|
|||
RE: TTFB is too BAD !
(03-08-2017 09:19 AM)avalanch Wrote: From gtmetrix... Thanks |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)