4 ms·
What about parse time? This is arguably an equally important metric. Make sure throttle CPU and network to simulate a budget smartphone when you test.
by andrewingram 10y ago
What about parse time? This is arguably an equally important metric. Make sure throttle CPU and network to simulate a budget smartphone when you test.
- indolering 10y agoIf you have customers on ancient smartphones and the engineering budget to manage the complexity ... go for it! :D
- andrewingram 10y agoWe're not talking ancient here. The mobile test on Webpagetest (https://www.webpagetest.org/easy https://www.webpagetest.org/easy) uses a Moto G4, which is less than a year old. But this test is punishingly brutal on most JavaScript-heavy websites. If you can make wins on parse time, you absolutely need to be pursuing them.
- abritinthebay 10y agoMost JavaScript heavy sites in the real world are that way due to 3rd party ad code (sad fact of the modern web) and Closure Compiler won't affect those
- abritinthebay 10y agoAgain, only based on my codebase, it was better but in the same way it was better on post gzip size: by not a lot. I'm sure in other specific cases it may be a lot better. Just not in mine.