Testing Your Website

A thorough testing process that ensures your new site is polished and ready for launch.

With testing, our goal is to ensure your site works and passes key performance metrics. To achieve this goal, we run your new site through a series of assessments — including:

Design-focused review

Browser and functionality testing

WCAG accessibility compliance

Page speed performance testing

Pre-launch site-wide auditing

What does the design review entail?

Your designer reviews the development website to ensure the fully developed website matches the design. They review everything from font and color implementation to spacing and margins.

Additionally, they’ll review the key pages to ensure that block choice and content align with your brand and vision. Any discrepancies they find are then addressed by our team of developers.

illustration of a brand guide
A chrome browser with a check mark next to it.

What does device and browser testing entail?

We test your website on multiple browsers, devices, and screen sizes. Currently, Chrome, Safari and Edge are the most popular browsers.

However, we test based on what your users use to access your website, and we gather this information from Google Analytics.

At the beginning of the project, we document browser and device traffic in the content workbook so we know what to test when it’s time for testing.

What does accessibility testing entail?

Web accessibility is intended to allow everyone, regardless of ability or disability, to navigate and interact with your website seamlessly.

Design

Our accessibility testing begins in the design and copywriting stages of the website redesign. We’ll test your color scheme for color contrast and text size compliance. We’ll also ensure we write proper headlines and descriptive link text.

Content Entry

When entering content into the CMS, we pay special attention to heading order, image alt text, and descriptive link text on all pages we’re responsible for.

Development

After building the site and entering content, we use multiple testing tools to test a subset of pages with specific features and functionality This subset of pages is documented in our accessibility report. We’ll address any issues on those pages.

Website performance report showing scores: Performance 93, Accessibility 95, Best Practices 93, SEO 100. Circular performance indicator and partial website preview are also shown.

What does page speed testing entail?

We’ll choose up to three key pages on your website and run them through page speed insights. Our goal is to achieve good scores within reason, knowing that several factors can impact page speed scores. Score results will vary based on your project features and requirements.

Common elements that get in the way of the results might include:

  • Embedded 3rd party tools and scripts
  • Cookie and data privacy tools
  • The project’s animation or design requirements
  • The weight or size of images and other files on the page

We’ll address what we can and keep you informed about what we can’t.

Here’s an article that talks about page speed testing

What does pre-launch auditing entail?

Getting a fresh pair of eyes on the site!

It’s important to make sure the site is buttoned up. This is our final checkpoint and step prior to launch — and it includes:

  • On-page SEO / link preservation documentation
  • Broken link / broken image report and resolution
  • Conversion/form testing and resolution
  • Redirects report and import resolution

We’ll document key findings and discuss with you how to proceed.

A clipboard with a checklist in front of a computer screen.

What’s next?

The launch is right around the corner. Together, we’ve done a lot of amazing work. Congrats on making it this far!

If we haven’t done so already, we’ll be talking with you very soon about launch planning efforts to help answer the following questions:

  • When specifically is our launch day and time?
  • Who is going to make the server changes on launch day?
  • What items need to be in place to get the site launched?

A couple of quick notes

  • While we work to complete our testing steps of the project, you may notice some things as well. We ask that you use the Request Tracker in the content workbook to keep a running list of anything that needs our attention. Can’t find the Request Tracker? Reach out to your PM and they will get you acclimated.
  • If you have specific requirements for any part of our testing steps, please let us know.