|
|
Posted by Andy Dingley on 11/26/44 11:55
John wrote:
> Is there a way/ program to determine what INDIVIDUAL ELEMENTS of a webpage
> are taking up the most time so that one can concentrate on whittling down
> the big stuff?
No - because it doesn't work that way.
Rendering pages is quick - always has been. It's the question of
delivering them to the browser (download time) and the sequential
dependencies between things.
If you have images and don't specify size in their <img> tag, then the
browser doesn't know how big to make them at first. It will probably
render the page once, then re-render the page (an ugly flash) after the
image has been downloaded and it does know the space required. This is
made worse if the image is a large file, thus slow to arrive. So if
you're making a site like photobucket.com, then set the explicit image
size on your pages. If you're just using small irregular thumbnails,
don't worry about it.
You might also find your page waiting for JavaScript. This isn't often
a problem, but there are some uses of AJAX and especially client-side
XML / XSLT where it can be ugly. As you probably can't stop such pages
being slow to copmplete, then make sure they look OK in the meantime -
not just an empty window.
Navigation:
[Reply to this message]
|