Pre and Post Launch QA
Making Websites involves lots of small jobs.
QA ensures that these jobs have not been forgotten.
There are two stages of QA. Pre-launch and post-launch
Pre-launch Quality Control
Before launching, the developer checks first, then the coordinator separately.
Content Checks
Have all the pages been made and completed?
Has the correct heading structure been used?
Have all the right pictures been used?
Is there a favicon icon?
No “Lorem Ipsum”, just final text.
Is the text balanced and of equal length?
Spelling checker?
Design
Does the website have uniform spacing and balance?
Are the fonts and text sizes used consistent across pages?
Design
Mobile friendliness?
Are Official Plugins used and set up?
Are only premium plugins used?
Has the website been checked by another developer?
Post Launch Quality Control
Once the website is its final place. We check to see if everything was set up correctly once the domain name has changed and the website is fully live.
Is the little robot red?
This is critical. Will Google be able to index the website? Use Chrome Tools – Robots Exclusion Checker.
Are all the links working?
Sometimes links are “hard-coded”—which means they will still have the URL of the dev site, not the live site.
Check with Screaming Spider
Do the contact forms work?
Does the client receive an email when something is bought?
Is the website loading quickly?
Give a check with GT Metrix. Read more about web performance issues.
Are the software plugins set up?
Is the website license for Astra plugins there. Are automatic updates on? See Wrapping Up.