How do you measure the affect of different layouts on browsers' progressive rendering of pages?
Ask YC: A way to measure page render time?
1–10 of 13 posts
Re: Ask YC: A way to measure page render time?
#2Re: Ask YC: A way to measure page render time?
#3YSlow is good for measuring page render time, using your computer and internet connection and provider meaning it might not mirror where your end-users are coming from geographically and from a network perspective.
There are companies you can use to measure performance of a webpage from various geographies, networks, and internet connections available from pingdom, Keynote, Gomez and other companies
Re: Ask YC: A way to measure page render time?
#4YSlow is good for measuring page render time, using your computer and internet connection and provider meaning it might not mirror where your end-users are coming from geographically and from a network perspective. There are companies you can use to measure performance of a webpage from various geographies, networks, and internet connections available from pingdom, Keynote, Gomez and other companies
Unless I'm missing something, yslow just measures download size and latency.
I want to measure how well the browser progressively renders the page. For example if I made a layout with tables nested 50 deep, the browser would do worse at progressive rendering and have a higher render time than if I used just css.
Likewise, I'm not talking about network latency, eg pingdom, keynote(?). Or compatibility, eg gomez.
Re: Ask YC: A way to measure page render time?
#5http://developer.yahoo.com/yslow/ ?
Render time. (see above)
Re: Ask YC: A way to measure page render time?
#6I ran across this the other day:
http://weblogs.mozillazine.org/roc/archives/2005/05/renderin...
If there was an easy way to run mozilla headless, e.g., "time moz-render-to-file foo.png", that would probably give you an idea (even better if moz could report timings itself). No idea how hard that would be to do, though.
Re: Ask YC: A way to measure page render time?
#7Gmail does it apparently.
Re: Ask YC: A way to measure page render time?
#8YSlow is good for measuring page render time, using your computer and internet connection and provider meaning it might not mirror where your end-users are coming from geographically and from a network perspective. There are companies you can use to measure performance of a webpage from various geographies, networks, and internet connections available from pingdom, Keynote, Gomez and other companies
Unless I'm missing something, yslow just measures download size and latency. I want to measure how well the browser progressively renders the page. For example if I made a layout with tables nested 50 deep, the browser would do worse at progressive rendering and have a higher render time than if I used just css. Likewise, I'm not talking about network latency, eg pingdom, keynote(?). Or compatibility, eg gomez.
Keynote DOES measure the time it takes for a page to be rendered using IE, Firefox, Safari and Opera.
Re: Ask YC: A way to measure page render time?
#9Earlier quoted context omitted.
Unless I'm missing something, yslow just measures download size and latency. I want to measure how well the browser progressively renders the page. For example if I made a layout with tables nested 50 deep, the browser would do worse at progressive rendering and have a higher render time than if I used just css. Likewise, I'm not talking about network latency, eg pingdom, keynote(?). Or compatibility, eg gomez.
Keynote DOES measure the time it takes for a page to be rendered using IE, Firefox, Safari and Opera.
I looked over those products and only see download time and latency, not render time. If you could provide a link to where this feature is listed, that'd be very helpful.
What I'd really like though would just be some kind of browser performance profiler (not js profiling.)
Re: Ask YC: A way to measure page render time?
#10I ran across this the other day: http://weblogs.mozillazine.org/roc/archives/2005/05/renderin... If there was an easy way to run mozilla headless, e.g., "time moz-render-to-file foo.png", that would probably give you an idea (even better if moz could report timings itself). No idea how hard that would be to do, though.
Probably the best solution I've seen yet, although that has some big limitations.
What surprises me is that, in looking at all the browser rendering benchmarks online, everyone just seems to do it by hand! There must be some pragmatic way that the browser developers are benchmarking the browser speed.