Development & Testing
Development starts as soon as the design stage has been signed off. Every site is built from the ground up. I don’t believe in refactoring a pre-bought theme for your website, when they offer generic templates and severely lack optimisation, due to containing an abundance of features, most of which go unused.
Each site is integrated with WordPress, which in this instance is used as a content management system, to allow you to update almost every aspect of your site.
Lastly, the responsive element of the site is developed, optimising how your site works on mobile and tablet. Google now treat this as a ranking requirement, not option.
Throughout development a degree of testing occurs across browsers and devices to ensure that any bugs are caught at an early stage. By doing this, very rarely do you get to the end of development and find something is fundamentally broken. However, a degree of end-user testing is always recommended, with real data and real people to try and emulate what your customer base will see. Feedback from this allows for ironing out any issues that were unforeseen during early development stages.
A very good testing tool once live is called A/B testing. This is essentially the deployment of two almost identical websites, that contain the most subtle of changes. This could be a smaller/larger font, different coloured calls to action or different text for the content. A/B testing allows you to compared the analytics and see which version of your site works better.