Inline images of the first container.

A lot of the negative feedback we have been getting has been around images not loading on the fronts.

This can be due to slow connections or Javascript errors.

This inlines (i.e. `<img/>`) the images in the *first* container on the page. The rest are lazily loaded.

This should mean we get the top images regardless of connection speed or javascript errors.

Here is one of the screenshots sent in as a complaint...

> Hi, had a message on our Facebook page this morning complaining of "the site design changing" and not loading correctly. User provided this screenshot of the page when fully loaded - NGW front, pics not loading correctly, and no opt-out option visible.
![complaint](https://f.cloud.github.com/assets/76709/1633823/b7a1b1ba-578f-11e3-9e26-e83b2b811179.jpg)