Reading/Web/Projects/A frontend powered by Parsoid/Parsoid html size initial report

In order to inform what a fast initial response would be for A frontend powered by parsoid we've performed some initial comparisons from the raw parsoid HTML and an optimized version.

Set up
For the experiment we're running a middle man server that has two endpoints: First hit on the API may be going to restbase and performing transformations, so for measuring we'll ensure to hit the API once, and measure 5 runs for each endpoint.
 * : Serves the raw parsoid html without transformations.
 * : Serves an optimized version of the HTML
 * For the purposes of the demo, this optimized version performs the following transformations:
 * Removing  attributes
 * Removing comments
 * Remove references
 * Remove tables
 * Remove images

For measuring we'll use 2 devices: Both devices will be connected to WIFI.
 * Macbook Air with OSX 10.10 and Chrome 46
 * Nexus 5 with Android 6 and Chrome mobile 46

For measuring we'll use the Chrome developer tools both connected to the desktop browser and to the mobile browser.

Since this is an initial research we'll measure one of our heaviest articles, Barack Obama

What are we trying to find out
Anecdotal experience shows that loading a parsoid html in a mobile phone blocks the browser for some time, so we're trying to get clear insight into what is happening and how to avoid it, since the purpose of the experiment is to quickly serve content to users on bad connections.