A mobile website is more than a smaller desktop layout. People may arrive while comparing services, checking a recommendation, or looking for a number they can call. The page should support that immediate task while still communicating the business clearly.
The most useful mobile review follows a few real journeys. Try finding a service, reading its explanation, opening a project, and sending an inquiry. Check each journey at different widths, then repeat the important ones on the devices your customers actually use.
Start with the text
Read a service page without zooming. Body copy around 16 pixels or larger is a practical starting point, but font shape, line height, contrast, and the surrounding space also affect readability. A thin typeface can be difficult at a size that works well for another font.
Watch headings that wrap. A title may fit on one line on a wide screen and take three lines on a phone. The description underneath it needs to follow that changing height. Placing both blocks in the same grid row can produce an overlap that only becomes obvious when the text changes or the screen narrows.
Read every numbered service row and card, including the last one. Check the labels, title, description, and link as separate elements. Each should have enough room to be understood without colliding with its neighbors. A visual review should include the actual words you will publish rather than shorter placeholder copy.
Make the next step easy to tap
Buttons and links need usable hit areas. Umanifest uses 44-pixel minimum-height targets for important contact and navigation actions as a practical design target. That is a design choice, not a statement that every control on every website meets a particular accessibility level.
WCAG 2.2 includes a Level AA target-size requirement based on 24 by 24 CSS pixels, with specified spacing and other exceptions. Its exact rules matter during an accessibility review. Use the linked standard to evaluate a control rather than treating a single larger number as a universal compliance test.
Check nearby controls together. A call button beside a text button should be easy to distinguish. A small dropdown arrow should not accidentally open the neighboring page link. Give each action a clear name and enough separation for a person to use it deliberately.
Test the menu and the return route
Open the mobile menu, choose a service page, and return to the main website. Confirm that the menu closes after navigation and does not cover the destination. Expand any service dropdown and make sure the page links can be read and tapped without horizontal scrolling.
A menu button should communicate whether the menu is open. Keyboard users should be able to reach the same pages, and Escape should provide a predictable way out of an expanded menu. Visible focus helps a person understand which control they are about to activate.
If you use a fixed contact toolbar or back-to-top control, review the content around it. Floating controls can be convenient, but the page needs enough room for the final links and form buttons to remain accessible. On a small screen, a compact control can preserve more of the page while retaining an understandable label for assistive technology.
Look for contrast and motion problems
Check ordinary paragraphs, captions, link text, and form labels against their actual backgrounds. A color that looks attractive in a large headline may be difficult to read in a smaller label. Moving backgrounds and translucent surfaces can change the contrast behind text, so examine more than one moment of an animation.
WCAG’s minimum text-contrast criterion generally calls for a 4.5:1 ratio for ordinary text and 3:1 for qualifying large text, with defined exceptions. Contrast is one part of accessibility; it does not replace checks for focus, structure, text alternatives, and interaction.
Motion should support the experience without making the content hard to follow. Check the website with reduced-motion preferences and consider whether moving content needs an accessible way to pause. A polished animation should still leave the information and controls understandable when movement is reduced.
Complete the form, including an error
Try submitting an incomplete form. The error should explain what needs attention, remain close to the relevant field, and preserve the answers already entered. Then correct the answer and try again.
Phone inputs benefit from the right keyboard. An email field should invite an email keyboard, and a phone field should support telephone entry. Labels should remain available after the placeholder disappears. Optional fields should not quietly become required at the final step.
Test a real permitted inquiry through to its destination. Confirm the private record or notification with the business owner. The success message should describe what the system has actually confirmed. Keep sensitive customer or patient details out of a general project inquiry when they are not needed for the conversation.
Separate responsive checks from performance results
An image that fits the screen can still be unnecessarily large. Use appropriately sized assets, reserve their layout space, and defer images that are not needed immediately. Avoid downloading every full-size project screenshot just to display a small preview.
Core Web Vitals provide another way to assess the experience using real measurements. Google’s current good thresholds include Largest Contentful Paint at 2.5 seconds or less, Interaction to Next Paint at 200 milliseconds or less, and Cumulative Layout Shift at 0.1 or less. Evaluation uses the 75th percentile of visits. A smaller image file alone does not prove that those thresholds have been met.
Record what you actually tested: browser widths, devices, interaction journeys, and any measured performance data. That makes the result useful for the next update and avoids turning a successful desktop preview into an unsupported claim about every phone.
For a new website or a refresh, Umanifest considers mobile layout alongside the content and visual direction. Explore our mobile design approach or tell us about your website.
Sources & further reading
Published by Umanifest with AI-assisted research and writing. External standards and tools can change; sources are provided so you can check the current guidance.