It seems like response.js introduces a time synchronization issue. It may have javascript code that is directly embedded in the js file and not wrapped in an event such as document.ready. This will lead to an immediate execution of the page loading and reading js and may cause inconsistent page loading behavior depending on how fast or slow events occur.
If so, you can quickly wrap the entire contents of the response.js file in the document's event handler so that the code does not execute until everything has finished loading.
$(document).ready(function(){
});
IE Chrome, , - js. , , , , , . console.log , . , .