[DigitalSea]

Responsive web development is very hard. It's easy to get a firm grasp on it, but sometimes can be a struggle determining what happens to a footer or sidebar on a small screen. Another issue is scaling down a desktop site for a mobile site merely hides things, it doesn't reduce page load times or page weight. I think responsive can work well for some sites, but if you're hiding a lot of content for mobile users a mobile site is best. Mobile Safari will still load an image regardless of whether or not it's hidden, same with scripts and stylesheets you might not even be using on a mobile version of your site.

People often forget a 300kb image on a desktop site is fine, but making your site react to the width of a screen you're shrinking the image down but the file size remains the same. A 300kb image on a mobile site via a 3G connection times two or three can spell disaster for some people's data plans especially if they're close to going over.

Also a handy thing to remember with the target divided by the context is to multiply it by 100 to get the actual percentage value. I know you can simply move the decimal over two places, but that eliminates the step and ensures your calculations are always correct. So the final formula becomes: target / context * 100 = responsive percentage value.