Before approving a new website, complete the tasks a customer will actually perform. A homepage screenshot can confirm the visual direction, but it cannot show whether a menu closes properly, a form error is readable, or a booking request reaches the right place.

This checklist is for business owners reviewing a responsive website with their designer or developer. It helps you collect concrete findings and agree on what needs fixing. It is a practical acceptance review, not a complete accessibility audit or a promise that every possible device has been tested.
1. Choose the pages and tasks to review
Include the homepage, your main service or product page, a longer content page, and the contact or inquiry flow. Add any page that uses a different layout, such as a gallery, comparison, or booking tool. Repeated templates need representative examples with realistic content.
Write several tasks before testing. For a Jacksonville service business, useful tasks might include checking service coverage, finding a relevant project, and submitting an inquiry about a particular job. Make the destination and expected result clear in your own notes without telling the tester which menu label to choose.
Use a mix of real phones and a desktop browser where possible. Include the browsers your customers commonly use if you have reliable information about them. A developer's preview tools are useful, but ask how the actual device experience will also be checked.
2. Read the first screen and the full page
Open each page directly, as a visitor arriving from a search result or shared link might do. Can you identify the business and the subject? Is there enough context to decide whether to continue? Do not require every detail to fit in the first screen, but make the opening useful.
Scroll through the entire page. Look for headings stranded far from their paragraphs, unusually large gaps, overlapping text, and images that cut off the relevant subject. Compare the small and large layouts to confirm that important conditions, descriptions, and evidence remain available.
Check long real headings and actual business contact details. Placeholder copy is rarely a good stress test. If a section will contain changing content, review an example that is more demanding than the shortest possible entry.
3. Open and close the navigation
On a phone, open the menu, follow a link, return, and close the menu again. Check whether the selected page loads in a usable state. A sticky header or an open overlay should not leave the destination obscured.
Try nested choices and long labels if the menu contains them. Confirm that contact information and important service pages are reachable from an interior page. Do not judge the structure solely from the homepage, where more shortcuts may be visible.
On the desktop, repeat the important paths using the keyboard. W3C's keyboard guidance explains that functionality should be operable through a keyboard interface, with a limited exception for genuinely path dependent input. Share any obstacles with the developer and refer to the W3C keyboard criterion.
4. Enlarge the page and check narrow layouts
Increase browser zoom and read the main content. Look for clipped words, controls that overlap, and information that disappears. Check whether a fixed banner leaves enough room to read and act. Ask the developer to investigate rather than simply reducing text size to make a screenshot fit.
W3C's reflow guidance addresses presenting content without losing information or functionality at a width equivalent to 320 CSS pixels for vertically scrolling pages, with exceptions for content that needs a two dimensional layout. Its reflow explanation gives the technical context. A quick owner check is useful, but the developer should verify the applicable conditions.
Also rotate a phone when that fits the task. Record whether a form remains usable and whether an open menu or dialog behaves sensibly. Describe the device, browser, orientation, and page so the issue can be reproduced.
5. Complete forms with realistic information
Use test details agreed with the team. Submit a valid form, then repeat with a required field missing. Check labels, instructions, field boundaries, and correction messages. Make sure a visitor can understand what needs attention without guessing from a colored outline alone.
Test a longer name or message rather than only a short sample. Try correcting an entry. Notice whether the keyboard covers an important control on the phone and whether the page can be positioned to reach it.
After submitting, inspect the actual result. Did the business receive the test inquiry? Is it recorded once? Does the confirmation accurately describe an inquiry rather than a confirmed appointment? If an email is expected, check that separately. A success message on the page is only one part of the journey.
6. Review images and supporting content
Check photographs in their final crops. Faces, products, and important project details should remain visible where they matter. Read captions and any text alternatives with the person responsible for content. Confirm that stock imagery is not presented as your team or completed work.
Open galleries, videos, downloads, and expandable sections. A thumbnail may look correct even when the larger view is awkward to close. Test how you return to the surrounding page and whether the context is preserved.
The National Website Designs website portfolio offers examples to discuss when planning project presentation. Your launch review should still use the exact assets and content being published on your own site.
7. Test embedded tools as separate journeys
Booking systems, maps, payment tools, and external forms may behave differently from the surrounding page. Test each tool that is part of the approved project. Check the transition into it, the information it requests, the completion state, and the route back to your website.
Use the appropriate test process for anything involving a transaction. Do not place a real order or appointment casually just to see what happens. Agree on safe test records and cancellation steps with the provider or developer when needed.
Record who owns each tool and who can change it. A problem inside an external service may require a different person from the one editing the website. That distinction is useful before customers encounter the issue.
8. Observe loading under ordinary conditions
Open important pages on a phone without relying only on the fastest office connection. Notice whether the main information becomes usable promptly, whether a large visual delays the task, and whether the page moves unexpectedly as content appears.
Ask for the developer's performance findings and an explanation of any material issues. Avoid approving or rejecting the entire site based on one isolated score. The review should identify what was measured, on which page, and what action is appropriate.
9. Record issues and decide what blocks launch
For each finding, write the page address, steps, expected result, actual result, and the device used. Add a screenshot or short recording when it clarifies the problem. Assign an owner and retest the same steps after a repair.
Prioritize issues that prevent an inquiry, hide essential information, or misstate the outcome of an action. Agree on how less urgent refinements will be handled. Read client testimonials when evaluating a provider, and ask how that provider manages review and support in your specific project.
After launch, repeat the most important journey on the live site and check the receiving systems again. Future content changes should include a smaller version of this review.
If you need help reviewing a launch, contact National Website Designs with your page list and recorded findings. Clear, reproducible issues make it easier to decide what needs attention and to verify that the finished site supports real customer tasks.