[
https://issues.apache.org/jira/browse/TAPESTRY-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637263#action_12637263
]
Onno Scheffers commented on TAPESTRY-2364:
------------------------------------------
> You say the overhead is minimal since the script is cached, but that also
> applies to your own use case.
Actually, it doesn't.
The browser only loads two resources at once. This means the js-files, which
are the last resources on the page, will not be resolved until all other
resources are loaded (e.g. all images and all other scripts). So even if they
are cached, the slowdown is considerable because I have to wait for _all_
other resources to be loaded before the script gets executed.
Meanwhile the page has been rendered and is visible to the user. The user may
even start clicking on items that shouldn't even have been visible to him or
her, depending on how big the images on the page are or how slow the connection
is.
> YSlow Recommendation: Write Scripts at bottom of page
> -----------------------------------------------------
>
> Key: TAPESTRY-2364
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2364
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.12
>
>
> Tapestry is already doing a good job on this, by writing the dynamically
> generated <script> block at the bottom of the page, but the external scripts
> should also be down there.
> http://developer.yahoo.com/performance/rules.html#js_bottom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
