<b>Chrome Version       : <Copy from: 'about:version'></b>
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
         IE:

What steps will reproduce the problem?
(1)http://www.globe.com.ph/
(2)https://accounts.globe.com.ph/login?service=http%3A%2F%2Fwww.globe.com.ph%2Fc%2Fportal%2Flogin
(3)

What is the expected result?
There are two errors on my console when I visit these pages.

1. XML HTTP request on the main thread is depreciated because of it's detrimental effects to the end user's experince.
When the async was set to true the page will not be blocked on css.

2.Parser Blocking, cross-origin-script, staiging.js, is invoked via document write.
The downside of parser blocking it's composability is that it implies a shared resposibility over the user experience. If the integrtion is sub-optimal, the user will negatively impacted.
Poor performance can be caused by the document write () inside pages, specifically those uses that inject scripts. It can cause real issue. Before the browser can render a page it has to build the DOM tree parsing the MTML markup whenever the parser encounters a script it has to stop and execute it before it can continue parsing the HTML. If the script dynamicallyy injects another script, the parser is forced to wait even longer for the resource to download, which can cause one or more network roundtrips and delay the time to first render the page.

What happens instead?
This weakness can be used to launch css. to lessen the css this uses booleanization. This could cause a bad user experience.


Please provide any additional information below. Attach a screenshot if
possible.

 

Deleted: Globe error hhtp.jpg 256 KB

	Globe error hhtp.jpg 256 KB View Download

Deleted: Globe error https.jpg 195 KB

	Globe error https.jpg 195 KB View Download