- Our Blog
The Content Grouping feature in Google Analytics exists for one very simple reason: to enable you to categorize your digital content into groups which reflect your business goals or reporting requirements. It's ...
This guide won’t regale you with the cool theory behind responsive images, because for now, you’re just testing the waters. It won’t lecture you on the potential benefits to site speed, because there are better resources o ...
Until now, web developers have had very little control over how browsers render images when they’re scaled. Take Mario, for instance: This is a 24×32 pixel image, scaled up using Photoshop to preserve its crisp, blocky composition. It’s a great example of the low-res pixel art that’s long been a staple of retro and indie games.
The advantages of using a CDN (Content Delivery Network) to serve commonplace resources are well-known. Why Use a CDN? Let’s say a visitor to your website requests a popular library such as jQuery or Mootools – when using a CDN, the content should (depending on setup) deliver from the server that’s physically closest to the user.
“SEO’s don’t need to code.” Strictly speaking this is true, but it’s a bit like saying it’s not worth learning your times tables. Sure, you can cruise along just fine without this skill – by relying on a calculator or copying the kid next to you – but it’s almost certainly going to make your life immeasurably easier. It doesn’t take much.
Last year, I had something of an epiphany about web design. I realised I didn’t really know how anything worked. Every website I’d created until then had relied on a CMS, namely WordPress. It was only when a bad plugin utterly botched the database tables leaving me helpless that I realised how little control I actually had over my precious creations.