Does your website work on a phone? Try these customer tasks.

Open your business website on your phone and pretend you have never seen it before. You are not checking whether it looks impressive. You are finding out whether a customer can accomplish something useful.

A practical review starts with a task: understand a service, confirm a location, make a call, or request help. Looking at the homepage alone will not reveal every obstacle. Follow the same path a real visitor would take, including the pages and forms after the first screen.

Choose a realistic situation

Pick one important customer and one reason they might visit. A homeowner in Kingsport checking whether you repair a particular appliance has a different task from someone in Erwin looking for your shop hours.

Write one sentence: “I need to find out whether this business can help with ___, and then ___.”

Use your own phone first. Later, repeat the important tasks on another device if one is available. Differences are useful observations, not reasons to assume every visitor has the same problem.

Task one: explain what the business does

Read the first visible heading and nearby text. Can you identify the service without interpreting a slogan? Is the service area clear when location affects whether the business can help?

A fictional repair shop might lead with “Solutions for every challenge.” That sounds broad but gives a new visitor little to use. “Small-engine repair in Johnson City” is more specific, if that accurately describes the business.

This is an illustrative example, not a client result. Your wording should match your actual work, not copy someone else's service promise.

Notice anything covering the introduction: large popups, banners, or sticky controls. Record the obstacle and the task it interrupts.

Task two: find the information that affects the decision

Look for one service detail a customer commonly asks about. Then find the operating hours, address or service area, and explanation of what happens next.

Do you need to open several menus? Does a long image push useful information far down the page? Is essential text embedded in a picture that becomes difficult to read?

Try increasing the text size or using your phone's zoom controls. Note clipped content, overlapping buttons, or information that becomes inaccessible. You are collecting specific evidence the person maintaining the site can investigate.

Task three: call or get directions

Tap the phone link. Does it offer the correct number? Cancel before placing a call unless you intend to complete one.

If customers visit a physical location, open the directions link and confirm that it points to the public customer destination. A mailing address and a visitor entrance are not always the same place.

Keep important controls distinguishable from ordinary text. If you repeatedly tap the wrong item or struggle to select a small link, describe exactly where it happens. “The hours link beside the phone number is difficult to tap” is more actionable than “the mobile design is bad.”

Task four: complete the inquiry path

With permission from whoever receives inquiries, send a clearly labeled test message using your own information. Do not include private customer information.

Watch what happens when a required field is empty and when the form is submitted correctly. Can you understand the error? Does the keyboard make a field difficult to reach? Is there a visible confirmation?

Then verify that the intended recipient actually receives the message. A confirmation screen is one part of the experience; receipt and follow-up matter too. If you cannot complete the test, record where you stopped rather than assuming delivery works.

Turn observations into a short repair list

For each issue, record the page address, device, task, what you expected, and what happened. A screenshot can help the site maintainer find the exact element.

Prioritize obstacles that prevent a customer from understanding the offer or contacting the business. After those, address confusing steps and readability. Cosmetic preferences can wait until the essential tasks are dependable.

Repeat the failed task after a change. A different-looking page is not sufficient evidence that the problem was resolved.

Contact CloudWise with your most important failed task and the page address. If the review shows that you need a new site, explore the current website options. A concrete observation makes either conversation more useful.