This post is part of a series I’m writing where I attempt to answer, to the best of my ability, a set of Front-End developer questions. I expect/hope my readers will disagree, augment, and generally hash out my answers in the comments below.

Can you describe the difference between progressive enhancement and graceful degradation? Progressive enhancement refers to a feature of your web site that enhances the experience for browsers that support it, but has no impact if your browser does not. As an example - consider IndexedDB. It lets you store data in a client-side database. If my web site made use of Ajax to load a large amount of data, I could use IndexedDB to cache data. If your browser doesn't support IndexedDB, then we just do Ajax to load that data. Modern browsers get a benefit, older browsers don't get screwed.

On the flip side, graceful degradation takes that modern feature and acts as if it is the default, but will not completely break the older browser. So in this case, the use of IndexedDB would be considered "normal", not the additional benefit for the modern browser.

In my opinion, it comes down to one side where you build for a certain base and provide additional, not-required features for better browsers (progressive enhancement) versus building for the more modern browser that assumes certain features, but assuring they "break" well.

How would you optimize a website's assets/resources? I can think of a few things here.

First - I'd optimize my images. In the past, I've used a Grunt script for this which makes it brain dead easy. You can point to a set of images, specify an optimization level, run it, and check the output to ensure it still looks good.

Another option for images is to use CSS sprites for related icons and the such. That reduces the network requests.

You can use a CDN that supports knowing and responding to a user's location to better serve up the assets.

For text files, you can minify, both CSS and JavaScript. For CSS, you can remove unused CSS (

I'm sure I missed a few more options here.

How many resources will a browser download from a given domain at a time? I'm going to answer this before I check Google to confirm: 8.

Looks like I was wrong - kinda. I figured there was some variation per browser, but check this StackOverflow answer: For Chrome it is 6, Firefox 6, IE11 is 8 though. I'd assume 6 then as a good average. Here is another good table on this stat:

What are the exceptions? So the limits are per domain, so in theory, you could use a wildcard DNS where * points to the same IP address. Seems like something I'd use with caution though. I think if you are at this point (of trying to get around the limit) then maybe you are doing a bit too much.