Hi Rob, have you tried JavaScriptDeferHeaderResponse?
And here's some background on how we arrived at this solution: https://issues.apache.org/jira/browse/WICKET-6498 Have fun Sven On 22.06.20 13:23, Rob Audenaerde wrote:
Hi all, I'm trying to increase the google-page-speed of some WicketApplication. It seems most jquery javascript is 'blocking', i.e. not usign 'defer'. For example this google-chrome-audit section: URL Size Potential Savings …jquery/jquery-2.2.4-ver-F9E….js <http://localhost:8080/wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-2.2.4-ver-F9EE266EF993962AD59E804AD9DEBE66.js> (localhost) 167 KB 2,560 ms …com.googlecode.wicket.jquery.ui.resource.JQueryUIR…/jquery-….js <http://localhost:8080/wicket/resource/com.googlecode.wicket.jquery.ui.resource.JQueryUIResourceReference/jquery-ui-ver-0A819924D70A18322660DEE759225D2B.js> (localhost) 494 KB 4,360 ms …js/wicket-aj….js <http://localhost:8080/wicket/resource/org.apache.wicket.ajax.AbstractDefaultAjaxBehavior/res/js/wicket-ajax-jquery-ver-3A8C326A8436172FC95523D517EBC88B.js> (localhost) 86 KB 1,660 ms /style.css <http://localhost:8080/style.css> (localhost) 4 KB 310 ms Is there a reason why this is all non-deferred? Or an easy way to change this? Most functionality is added in an DomReady event anyway.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
