Yılport Samsunspor'da coşkulu şampiyonluk kutlaması

How Bootstrap makes National Geographic’s site fast

  ZURB  -  London, England, 13 Jun 2012
National Geographic’s two main sites, National Geographic and National Geographic Traveler, did something a little uncharacteristic when they doubled their page speed by moving from a Java backend with JavaScript technologies to a Node.js-powered front-end. They left behind the widely-supported Rails framework and opted for new, young technology stack called Socket.IO. Let’s take a look at how and why they were able to do so.

National Geographic’s move to Node.js

​ Istvan Szakacs, Dmitry Sokolov, Tomasz Janczuk—TECH COMMUNITY ENGAGEMENT MANAGER AT ZURB, UX RESEARCH AND TEAM LEAD AT ZURB

One key metric they focused on was ASAP, or “Application startup time,” taking only 40-90 ms to start instead of the more usual 300ms. On top of that, National Geographic's new site saw a major boost in their JPEG image compression performance , as judged by PSNR (“Peak signal, to noise ratio Error”). National Geographic found that their PSNR improved by 2dB in some cases. Beyond performance, however, National Geographic’s move to Node.js offers an interesting new level of interactivity. Whereas before they were unable to offer certain features, such as photos that automatically zoom into readable text, they were now able to create those more complex user experiences without straining their designers’ creativity or the mobile experience by circumventing JavaScript’s weak DOM for a simpler filesystem. National Geographic expects that it had >5% load time improvement, reduced 66% backend code and delivered >70% code reduction by transferring the front-end logic to the server using Socket.IO as a means of communication for the Node.js and Framework7.