Mobile-Friendly WordPress Websites: A Testing Checklist for SA Businesses

Before signing off a new website, ask your developer to demonstrate a complete customer journey on a phone: find a service, understand the offer and submit an enquiry or purchase.

That is the practical focus of responsive web design in WordPress. Responsive design serves the same HTML at the same URL while adapting its presentation to the screen. Google recommends this approach as the easiest mobile configuration to implement and maintain. Google’s mobile-first guidance also explains that Google uses mobile content for indexing and ranking.

For a South African business commissioning a website, make mobile testing part of the acceptance brief—not a vague promise that the theme is responsive. Whether your customers are in Pretoria, Johannesburg, Cape Town or elsewhere in South Africa, agree on the journeys and evidence you want before launch.

Use the checklist below as a proposed testing standard. The suggested devices, widths and sign-off rules are practical recommendations, not universal certification requirements.

1. Agree on the pages and journeys to test

Start with a written test list. Do not limit approval to the homepage.

For a service business, include:

  • The homepage and a main service page.
  • A location page, if relevant.
  • An article with headings, images and embedded content.
  • The contact page and enquiry confirmation.
  • Any booking, quotation or account journey.

For an online shop, add product listings, product variations, the basket, checkout and order confirmation.

Choose pages containing your longest headings, widest tables and most complex forms. Use final or representative content rather than approving layouts filled only with short placeholders.

Write down the expected outcome for each journey. For example: “A visitor can find the service area, read the enquiry requirements, submit the form and receive confirmation.”

If you are commissioning WordPress website design and development, include this test list in the scope. Ask which checks are included, who fixes failures and who approves the retest.

Suggested pass condition: Every agreed journey has a named tester and a recorded outcome.

2. Combine editor previews with browser and real-phone checks

WordPress documents preview controls for checking content at different screen widths, alongside a separate front-end preview. Treat the editor canvas and the visitor-facing page as separate checks; WordPress explicitly provides front-end viewing separately from the editor. See its preview documentation.

Ask your developer to demonstrate three layers of testing:

  1. Editor preview: Inspect the content while editing.
  2. Browser simulation: Resize the actual page and inspect intermediate widths.
  3. Physical devices: Complete the priority journeys on real phones.

As a starting test matrix, consider widths of 320, 375, 425, 768 and 1,024 CSS pixels, plus a wider desktop view. These are suggested test points—not a list of every device your site must support. Slowly resize between them rather than checking only fixed presets.

Chrome describes Device Mode as a first-order approximation, not execution on a mobile device. Its Device Mode documentation recommends running the page on an actual mobile device when in doubt.

Record the phone, browser, orientation and page tested. Include a visitor-facing session without an administrator login as a separate test case.

Suggested pass condition: The agreed journeys work in browser simulation and on the physical devices specified in the brief.

3. Check reflow, reading order and content visibility

At each test width, inspect the whole page from header to footer.

  • Read headings without zooming out.
  • Look for clipped text, overlapping blocks and unintended sideways scrolling.
  • Check whether columns stack in a sensible reading order.
  • Inspect pricing cards, testimonials and long service names.
  • Rotate the phone and repeat the inspection.
  • Check whether sticky elements cover content or controls.

For an accessibility benchmark, WCAG 2.2 Success Criterion 1.4.10 requires vertically scrolling content to reflow at a width equivalent to 320 CSS pixels, without loss of information or functionality and without requiring scrolling in two dimensions. It includes an exception for content that needs a two-dimensional layout for usage or meaning.

Do not turn that into an absolute rule that every table, map or diagram must fit without horizontal movement. Instead, ask the developer to identify any exception and explain the treatment.

Check content consistency too. Google’s mobile-first guidance recommends equivalent primary content on mobile and desktop. Do not approve a simplified mobile layout that omits important service explanations merely to make the page shorter.

Suggested pass condition: Ordinary page content reflows without clipping or unintended two-dimensional scrolling, and essential information remains available.

4. Test navigation and touch controls

Open every menu and submenu on a phone. Follow the links rather than checking only whether the menu animates.

Use this sequence:

  • Open and close the menu repeatedly.
  • Select each important destination.
  • Open nested navigation, where present.
  • Return using the browser’s Back button.
  • Test search, accordions and dismiss controls.
  • Check that floating contact buttons leave other controls accessible.

For touch sizing, WCAG 2.2 Success Criterion 2.5.8 sets a 24 by 24 CSS pixel minimum for pointer targets, subject to exceptions. Those include qualifying spacing, an equivalent control, inline targets, unmodified user-agent controls and essential presentations.

The spacing exception is not a blanket requirement for a 24-pixel gap. It uses a specific non-intersection test involving 24-CSS-pixel-diameter circles centred on undersized targets. Ask for the actual criterion to be checked rather than approving an arbitrary spacing rule.

As a usability preference, request generous controls for primary actions, even where an exception might apply.

Suggested pass condition: Navigation destinations are reachable, controls respond reliably and important actions are not obscured.

5. Submit forms with the on-screen keyboard open

Do not approve a contact form from a screenshot. Submit it from a phone.

Test both a successful submission and deliberate errors:

  • Leave a required field blank.
  • Enter an invalid email address.
  • Correct the error and resubmit.
  • Use a longer message.
  • Open and close the on-screen keyboard.
  • Test consent controls and any anti-spam challenge.

Check whether labels remain understandable during entry. Make sure the keyboard does not leave the submit button or error message inaccessible. Ask the developer to explain which fields should request email, telephone or numeric input, then verify the behaviour on the agreed phones.

For a South African enquiry journey, try representative local and international-format telephone numbers. Confirm the intended validation rules rather than assuming every phone field accepts both.

Finally, verify receipt at the destination inbox or business system. Record the confirmation shown to the visitor separately from the delivery result.

Suggested pass condition: A visitor can recover from an error, submit successfully and receive an accurate confirmation; the business receives the test enquiry.

6. Inspect images, cropping and alternative text

WordPress has native responsive-image support using srcset and sizes. These attributes provide information and alternatives that help the browser select an image resource. The WordPress responsive-images handbook also explains that existing srcset or sizes attributes in content are not automatically added or modified.

Ask the developer to inspect the rendered markup and the image actually requested by the browser. Do not accept “WordPress handles it” as the complete test result.

For the visual review:

  • Check logos and product photographs at narrow widths.
  • Inspect hero-image crops in portrait and landscape.
  • Confirm that important product details remain visible.
  • Read captions and inspect image links.
  • Test galleries without relying only on desktop hover behaviour.

For alternative text, use the image’s purpose as the starting point. WCAG 2.2 Success Criterion 1.1.1 requires text alternatives for non-text content, with specified exceptions, including decorative content that assistive technology can ignore.

Suggested article illustration: Create a comparison showing the same service page on desktop and mobile. If that illustration is produced, use descriptive alt text such as: “Desktop and mobile layouts of a WordPress service page, showing stacked content and an expanded mobile menu.” Adjust the text to match the actual image; do not publish it against an unrelated stock photograph.

Suggested pass condition: Images preserve their intended meaning, resource selection has been inspected and text alternatives suit the actual content.

7. Separate performance diagnostics from real-user evidence

Request mobile PageSpeed Insights results for representative pages, not just the homepage. Keep the report URLs or screenshots with the test record.

Google’s PageSpeed Insights documentation distinguishes historical field data from simulated Lighthouse laboratory tests. Field data comes from the Chrome UX Report over the preceding 28-day collection period. Laboratory results describe a simulated test environment.

For Core Web Vitals, the documented “good” thresholds are:

Metric Good threshold
Largest Contentful Paint: loading performance 2.5 seconds or less
Interaction to Next Paint: responsiveness 200 milliseconds or less
Cumulative Layout Shift: visual stability 0.1 or less

These field thresholds are evaluated at the 75th percentile. Do not describe one successful laboratory run as proof that real visitors meet them.

Check whether the field report represents the specific page or an origin-level fallback. PageSpeed Insights may lack sufficient page-level observations and fall back to origin data; if the origin also lacks sufficient data, it does not show real-user experience data. Missing data is not a pass or a fail.

Alongside the report, test an agreed slower-network simulation and complete the enquiry or shopping journey. Keep the simulated conditions clearly labelled.

Suggested pass condition: Performance evidence identifies its source and scope, and outstanding issues have an agreed remediation plan.

8. Complete the purchase journey, not just the product page

For an online shop, extend mobile acceptance testing through the full transaction. Include these checks in the e-commerce website design scope rather than treating checkout as a separate afterthought.

Use an approved test environment and payment method. Verify:

  • Product options and quantity controls.
  • Basket updates and item removal.
  • Delivery details and available delivery choices.
  • Discount entry, where supported.
  • Order totals and the intended rand display.
  • Payment success, cancellation and failure journeys.
  • Order confirmation and the business’s order record.

Write down the expected results before testing. For example, specify what should happen after a cancelled payment and whether entered delivery information should remain available.

Do not use real customer information in the test record. Ask the payment provider or developer how to conduct test transactions safely within the chosen integration.

Suggested pass condition: Each agreed transaction outcome produces the expected visitor message and business record.

9. Request evidence and agree on launch priorities

Use one issue register rather than a collection of informal messages.

Record What to capture
Location Page URL and affected component
Environment Device, browser, orientation and viewport
Reproduction Steps another tester can follow
Outcome Expected behaviour and observed result
Evidence Screenshot, recording or report
Ownership Responsible person and retest date

As a proposed launch rule, treat blocked enquiries, inaccessible primary navigation and broken checkout journeys as launch blockers. Agree separately how to prioritise cosmetic differences and non-critical improvements.

For a local project, discuss these deliverables alongside the Pretoria web design scope or your relevant service brief. Use the same acceptance process for a national or multi-city website.

Retest the affected journeys after fixes. Also schedule a fresh check after significant changes to templates, forms, navigation or checkout.

Commission responsive WordPress design with clear acceptance criteria

When comparing proposals for WordPress responsive web design, ask for a testing deliverable—not only a responsive-theme description.

Request a page list, device matrix, accessibility checks, performance evidence, issue register and named sign-off owner. Ask how mobile defects discovered during acceptance will be handled and what ongoing testing is included after launch.

Bogoshi Tech Space’s service offering includes responsive WordPress development and UI/UX design. Review the website design packages and use this checklist to discuss the scope you need; confirm testing inclusions directly rather than assuming every package includes every check.

Your final approval question should be practical: Can a visitor understand the offer and complete the intended task on the agreed mobile devices? Require a demonstrated answer before signing off.

Categories: Uncategorized

One response to “Mobile-Friendly WordPress Websites: A Testing Checklist for SA Businesses”

  1. […] validation messages and the purchasing or enquiry journey in mobile review. Bogoshi’s mobile-friendly WordPress testing checklist provides a relevant starting point for that […]