As always without knowing nothing about your application is hard to give
more precise answers.
But, first of all, I would do a test in localhost to have a reference unit.
For now let's keep the network variable out.
If you have a shell account in your server do:
curl -o /dev/null -s -w "Connect: %{time_connect} TTFB:
%{time_starttransfer} Total time: %{time_total} \n" http://localhost/
be sure that curl is hitting you homepage and not some redirect.
In the same host/web2py you can also create a minimal application with
nothing but a controller/default.py that only as:
def index():
return 'OK'
and then time it with curl and webpagetest.
Note: When timing with curl do it 3 or 4 time consecutively to the same url
Know you have some measures to go on... check this thread if not already:
https://groups.google.com/d/topic/web2py/JgkMaQ_VlXs/discussion
Ricardo
On Tue, Apr 9, 2013 at 10:04 PM, BlueShadow <[email protected]> wrote:
> Hi I'm trying to improve my pageloadtimes. And so far I'm doing pretty
> good. I decreased the number of quests by merging some css files and some
> javascript. I added expire headers to pretty much every file I serve. But
> the most time it takes to load a page is the time to first byte.
> I checked my site with webpagetest.org it takes 0.747s for the first
> byte. and quite a few requests take 500 ms or more before the first byte
> flows. Is there any way to find out why its taking so long? And a way to
> improve tose numbers.
> thanks
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "web2py-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.