The site is 'ready', the design is approved, the texts are uploaded, and launch is two days away. And that is exactly when you find out that the request form does not submit from an iPhone, the layout falls apart on the payment page and confirmation emails go to spam. All of this could have been found in advance if you had set aside separate time for checking and done it by plan, rather than 'clicking through the pages and seeing'.
In this article we cover what exactly to check before launching a site and in what order, how the types of testing differ, how a client should accept the work and what to do on release day.
Why test, and who is responsible
A mistake found before launch costs many times less than one found by a customer. If a form is broken, you lose requests every day until someone notices, and if payment is broken, you lose money and trust. Fixing things on a live site is also always riskier: a change can affect something that was already working.
Responsibility for testing is shared. The contractor must check their work before handing it over: that is their area. But the client cannot rely on that entirely: only you know how your business really works, which scenarios are critical and what buyers do on the site most often. So the best result comes from a combination: the studio checks the technical side, and the client walks through the key business scenarios through the customer's eyes.
Types of checks in plain words
Functional testing answers the question 'does every feature work as described in the brief': buttons, forms, search, filters, the personal account. Interface and compatibility testing checks how the site looks and behaves on different phones, tablets and in different browsers. Performance testing looks at loading speed and behaviour under load. A security check looks for typical vulnerabilities and incorrect settings. Acceptance testing is separate: it is the client's final check against criteria agreed in advance.
These types do not replace each other: a site can work perfectly on the developer's computer and still be slow on a customer's phone, and a fast site can have a hole in its login form. That is why a good test plan covers all directions, though with different depth depending on the size of the project.
Functional testing: does what should work actually work
The basis of the check is the technical specification itself. Every function described in it should be tried by hand and the result recorded: works, does not work, works differently from what is described. If the specification is written as scenarios, testing becomes a simple walk through them.
Do not limit yourself to the 'happy path' where the user does everything right. Check wrong actions too: what happens if a field is left empty, letters are entered instead of digits, a very long text is pasted, a button is pressed twice, or the user goes back in the middle of checkout. This is where sites break most often. Be sure to go through all the links and buttons in the menu and footer, check the 404 error page and the work of search, filters, sorting and pagination if the site has them.
Do not forget the admin panel: try adding, editing and deleting material the way your staff will, and check that the changes really appear on the site. Quite often the panel is set up so that it turns out to be inconvenient or inaccessible for an ordinary manager.
Forms, requests and emails
The request form is the main tool of the site for most companies, so it is checked especially carefully. Send a test request from every form on the site and make sure it arrived where it should: by email, in the CRM, in Telegram or the manager's messenger. Check that all fields are passed on, not just some of them, and that the customer sees a clear confirmation after sending.
Look at the emails separately: whether they arrive at all, whether they land in the Spam folder, how they look on a phone and whether they contain the right data. If the studio sends mail from a technical address without domain setup, emails often end up in spam or do not arrive at all. Check spam protection too - a captcha or a similar mechanism: it should neither let bots through nor get in the way of real customers. If you have already had cases where requests got lost on the way, it is worth walking the whole path of a request from the form to the CRM separately and making sure the data is saved at every step.
Payment and orders
For an online store and any site with payment this is the most important block. Go through the whole buyer's journey: choosing a product, the cart, checkout, payment, the confirmation page and the email. If the payment system provides a test mode, use it and check different outcomes: successful payment, decline, cancellation on the payment page, closing the tab in the middle of the process.
The main thing to confirm is that the order status on the site changes based on the notification from the payment system, not just on what the buyer's browser saw. Check that the order total is calculated correctly taking discounts, promo codes and delivery into account, that stock is deducted correctly and that a refund can be issued without manual workarounds. Before launch, be sure to switch the payment module from test mode to live and make one real small payment to confirm the money actually arrives.
Ask a question or leave a request
We will check forms, payment, the mobile version, speed, security and indexing settings, then hand over a report and a prioritised list of fixes.
By submitting the form, you agree to the processing of personal data.
Mobile devices and browsers
A large share of visitors come from phones, so the mobile version needs to be checked no less than the desktop one. Open the site on real devices, ideally both Android and iPhone, and not only in the browser's emulation mode: problems with fonts, pop-ups, the keyboard and gestures show up on real phones.
See whether text is cut off, whether elements overlap, whether buttons are comfortable to tap with a finger and whether the on-screen keyboard covers the form. Check landscape orientation and different sizes. Then open the site in several browsers - Chrome, Safari, Firefox, Edge - especially Safari, which has its own quirks. There is no point in checking every possible combination, but the main 'device - browser' pairs of your customers are worth checking. A hint about what your audience uses comes from the analytics of the old site, if there is one.
Speed and load
Loading speed affects both conversion and visibility in search. Check the main pages with free speed-testing tools and note what slows them down: huge images, extra scripts, a slow server. Most often the simplest and most effective measure is image optimisation: a photo at its original camera size can make a page several times heavier.
For sites expecting a surge of visitors - a sale, an advertising campaign, seasonal demand - it makes sense to run load testing: simulate a large number of users arriving at the same time and see how the server behaves. This is not required for a small business-card site, but it is very important for stores and services. Compare the results with what you expect: if you are planning a big advertising campaign, the site must withstand the traffic you are counting on, not only what there was yesterday.
Security before launch
Basic checks do not require special knowledge but cover most typical problems. Make sure the site works over HTTPS on all pages and that unprotected addresses are automatically redirected to protected ones. Check that test passwords and accounts have been removed, and that administrators use strong passwords and, where possible, two-factor protection. The admin panel should not be available at an obvious address without protection.
Check that no service files, backups, test pages or closed sections that search engines and outsiders could find remain publicly accessible. Check that the platform and plugins are updated to current versions and that backups are configured and really work: ask to be shown how to restore the site from a backup, not just to be told that backups are made. For sites that collect personal data, make sure the form contains consent to processing and the privacy policy is published on the site.
SEO and analytics: what to check before release
This is the block that is most often forgotten, and then paid for dearly. The most common and most unpleasant mistake is a leftover indexing ban that is switched on during development: if it is not removed at launch, the site simply will not appear in search. Check the file with rules for search robots and the indexing settings.
Next, check that every page has a unique title and description, that pages have one main heading, that addresses are readable and that images have descriptions. If you are moving an old site to a new one, prepare redirects from old addresses to new ones, otherwise you will lose accumulated rankings and links. Make sure there is a sitemap and that it is accessible, and that the 404 page returns the correct status code.
Finally, check analytics: whether the counter is installed, whether goals are recorded - form submission, payment, a click on the phone number - and whether the staff's own visits are excluded. If advertising leads to the site, before launching the campaign walk the path with a tagged link and make sure the source is visible in the reports.
Content and legal pages
Do not leave test texts, filler text and placeholder images on the site: searching the text for things like 'lorem' or 'test' before launch helps more often than you would think. Check spelling and consistency: names, prices, contacts, addresses and opening hours must match on all pages and with what you state elsewhere. Check the phone number and email: tap them from a phone and make sure they work.
Make sure the site has the pages and information required for your business: a privacy policy, payment and return terms, company details, and a public offer for an online store. This is not only a matter of law but also of trust: buyers look at whether the site shows company details and terms.
How to report the errors you find
A good bug description saves time for both sides. It should make clear what happened and where, how to reproduce it step by step, what was expected and what actually happened, and on which device and in which browser it was observed. A screenshot or a short screen recording almost always helps.
It is useful to state severity right away: what blocks the launch (payment or a form does not work), what needs fixing soon (a cosmetic error on a separate page) and what can wait. Without this, the developer and the client argue about priorities and spend time on trifles while serious problems remain unresolved. Keep all comments in one place - a spreadsheet or a task system - rather than in scattered messenger messages where they get lost.
Acceptance: how a client should accept a site
Acceptance should not boil down to 'we looked, seems fine'. Rely on the technical specification and the acceptance criteria agreed in the contract: go through the items and mark what is done and what is not. It is better to set aside specific days for this and involve the people who will work with the site: the manager who handles requests, the content manager, and the accountant if the site is tied to accounting.
If there are comments, collect them in one list and send them to the contractor. Sign the acceptance act only when you have checked the key scenarios and made sure the critical errors are fixed. If some comments are minor, this can be recorded in the act as a list of follow-up work with agreed deadlines, rather than accepting silently and then trying to return to the issue.
Launch day and the first days after it
It is better to schedule the launch for a calm time, not Friday evening or the eve of holidays: if something goes wrong, there must be people ready to fix it quickly. Before switching over, make a full backup of the current state - both the old site and the new one. After switching the domain, immediately go through the key scenarios on the live site: the form, payment, emails, the main pages, the mobile version.
In the first days after launch, watch closely: see whether requests and orders arrive, whether there is a spike in errors, whether the site works normally under real traffic, and how indexing is going. Customer messages like 'it will not open for me' or 'I could not place an order' are a valuable source of information and deserve a quick response. If the studio provides a warranty period, now is when you need it: record what you find in writing and pass it to the contractor straight away.
Common mistakes
The most common mistake is to test only the 'happy path' and only on a computer, and then be surprised that customers on phones run into problems. Another typical situation is leaving test settings in place: the indexing ban, test payment mode, test emails and accounts. People often forget to check where requests actually go: to an email nobody has read for a long time, or to a CRM where they do not reach the right manager.
Another problem is the lack of a backup and a rollback plan: if the launch goes badly, there is nothing to return to the previous state with. In addition, clients often accept a site in a hurry under deadline pressure, and then, on discovering errors, have to fix them on the live project and in non-working hours. Finally, many forget about analytics and redirects from old addresses, which leads to lost data and search rankings.
Pre-launch checklist
- All functions from the technical specification have been tried and marked
- Incorrect user actions have been checked, not only correct ones
- Every form sends the request where it should and the customer sees a confirmation
- Emails arrive, do not land in spam and look right on a phone
- Payment was checked in test mode, then live with one real transaction
- The site has been checked on real phones and in the main browsers
- Loading speed has been checked and images are optimised
- The site works over HTTPS, test access has been removed, backups have been verified
- The indexing ban is removed; titles, descriptions, sitemap and redirects are set up
- Analytics is installed, goals are recorded, advertising sources are visible
- There are no test texts on the site; contacts and company details match everywhere
- The privacy policy and the required legal pages are published
- Errors are collected in one prioritised list, critical ones are fixed
- A full backup was made before launch and there is a rollback plan
- After launch the key scenarios were checked on the live site