Give a beginner a website and ask them to "suggest improvements," and watch what happens. Nine times out of ten they'll jump straight to opinions — "the colors should be different," "this needs more content," "add a chatbot." None of that is wrong exactly, but none of it is evaluation either. It's reaction. And reaction without evaluation is how students end up recommending changes that don't fix the actual problem, sometimes changes that don't matter at all. This exercise exists to slow that instinct down. Before you're allowed to suggest a single improvement, you're going to evaluate the website properly first — the same way I'd want a junior team member to approach a real client site before opening their mouth in a meeting.
Why evaluation has to come before recommendations
Here's the problem with jumping straight to suggestions: you end up fixing symptoms instead of causes, or worse, fixing things that were never broken in the first place. A website with low sales might have a beautiful, fast, well-designed homepage and still fail — because the checkout process is confusing, or because it's targeting the wrong keywords entirely, or because the trust signals are missing and visitors bounce before they ever reach the design you'd have complimented. I've watched students spend an entire session redesigning a homepage's color scheme for a site whose actual problem was that the contact form was broken. Nobody had tested it. The design looked fine. The fundamental function didn't work. That's the exact trap this exercise is built to catch — and it only gets caught if evaluation happens systematically, not by scrolling through a page and reacting to whatever catches the eye first.
What you'll need before starting
Pick any live business website — your own, a classmate's, or any small business site you find while browsing. It doesn't need to be broken or badly built. Honestly, evaluating a decent site is often more instructive than evaluating an obviously bad one, because you have to look harder to find the real gaps instead of listing the obvious ones. You'll also want a simple document — a notebook, a spreadsheet, whatever you're comfortable with — because this exercise depends on writing observations down as you go, not just holding them in your head. Trust me on this one. Half the value of a structured evaluation disappears if you don't record what you noticed at each stage, because by the end you'll have forgotten your first impression entirely.
Step 1: Record your first impression, unfiltered, in under ten seconds
Open the website and give yourself no more than ten seconds before writing down your gut reaction. Not an analysis — a reaction. Does it feel trustworthy? Confusing? Outdated? Professional? Slow? This step feels almost too simple to matter, but it's doing something specific: it's capturing what a real visitor experiences, before your trained eye starts hunting for technical details a normal visitor would never consciously notice. A real customer doesn't audit a site. They feel something within a few seconds and either stay or leave based on that feeling. If your ten-second reaction is negative, that's data — and it's data you'll lose if you skip straight to the technical checklist.
Step 2: Identify who the site is actually built for
Read the homepage and ask yourself plainly — who is this for, and what do they want when they land here? Sometimes this is obvious. Sometimes, honestly, it isn't, and that itself is a finding worth writing down. A site that can't clearly signal its target audience within the first screen is asking every visitor to do extra work just to figure out if they're in the right place. Write down your best guess at the primary audience and the primary action the site wants that audience to take — buy something, call, fill a form, subscribe. If you can't answer both of those clearly after reading the homepage once, note that as a problem right there, before evaluating anything else.
Step 3: Test the site's core function, not just its appearance
This is the step students skip most often, and it's the one that catches the biggest issues. Actually try to do the thing the website wants you to do. Fill out the contact form. Add something to cart if it's an e-commerce site. Click the "call now" button and check where it actually leads. Try this on a phone, not just a laptop screen, because a huge share of real visitors will be on mobile and a broken mobile experience is invisible if you only ever check on desktop. If the primary action fails — a form that doesn't submit, a broken link, a checkout that errors out — everything else you evaluate afterward is secondary. A beautifully designed site that can't process an actual sale isn't a design problem you're looking at. It's a business-stopping problem wearing a design costume.
Step 4: Check load speed and mobile behavior honestly
You don't need specialized tools for this at a beginner level, though they help later. For now, just time how long the site takes to feel usable — not fully loaded technically, but usable to you as a visitor. Three seconds of waiting feels very different from instant, and most visitors won't consciously clock the exact number, they'll just feel impatient and some percentage of them will leave. Check the mobile view specifically for text that's too small to read without zooming, buttons placed too close together to tap accurately, and images or menus that overlap or break the layout. This happens more than you'd expect, even on sites that clearly had a real design budget — mobile testing gets skipped surprisingly often, even by people who should know better.
Step 5: Look for trust signals — or the lack of them
Scan specifically for the things that quietly tell a stranger this business is real and safe to deal with. Is there a genuine contact address, not just a form? Are there reviews or testimonials, and do they look real rather than obviously staged? Is there any indication of who's actually running the business — a real name, a real story, some sign of an actual human behind the page? Note what's present and, just as importantly, what's conspicuously missing. A site with no reviews, no visible contact information beyond a form, and no author or founder mentioned anywhere isn't necessarily fraudulent — plenty of legitimate small businesses look exactly like this — but it is giving a cautious visitor fewer reasons to take the risk of buying, and that matters regardless of whether the business is trustworthy in reality.
Step 6: Read three pages of actual content, not just skim them
Pick three pages beyond the homepage — maybe a product page, a blog post if there is one, and an about page — and actually read them properly, not skim. Ask whether the content answers real questions a visitor would have, or whether it reads like filler written to satisfy a word count. You'll know the difference fairly quickly. Filler content tends to state the obvious in more words than necessary and rarely tells you anything you didn't already assume. Also note the tone. Does it sound like a real person or business wrote it, or does it read generic enough that it could belong to any business in any city? This matters more for trust and conversion than most beginners initially assume — generic content doesn't just underperform in search rankings, it fails to build any actual connection with the reader either.
Step 7: Note what's competing for attention on each page
Look at any page with more than one obvious action available — multiple buttons, multiple links, a sidebar full of offers alongside the main content. Ask what a visitor is actually supposed to do here, and whether the page makes that obvious or whether it's competing against itself. A page that offers a newsletter signup, a "shop now" button, three blog links, and a social media follow request all with equal visual weight isn't guiding anyone anywhere. It's presenting a menu and hoping the visitor picks something useful on their own. Sometimes that's fine — genuinely, it depends on the type of page and what stage of the buyer journey it's serving — but on a page meant to drive one specific action, too many competing options usually hurts more than it helps.
Putting it together: build one evaluation table
Once you've gone through all seven steps, organize your notes into a simple table. This is what separates a scattered set of observations from something you could actually hand to a business owner or discuss credibly in an interview.
| Area evaluated | What you found | Severity (low / medium / high) |
|---|---|---|
| First impression | Your unfiltered ten-second reaction | |
| Audience clarity | Could you identify the target visitor and desired action? | |
| Core function | Did the main action (form, checkout, call button) actually work? | |
| Speed and mobile | How the site felt to use, especially on a phone | |
| Trust signals | What was present, what was missing | |
| Content quality | Genuine and specific, or generic filler | |
| Focus and clarity | Did pages guide toward one clear action or scatter attention |
Fill the severity column honestly, not evenly. Real sites rarely have seven problems of exactly equal weight — usually one or two things are genuinely holding the site back, and the rest are smaller polish items. Learning to tell the difference is, frankly, most of what separates a junior evaluation from an experienced one.
A hypothetical walkthrough, to show what this looks like finished
Imagine evaluating a small home bakery's website. First impression: pleasant, warm photography, feels genuine. Audience is clear — local customers wanting custom cakes. But testing the core function reveals the "order now" button just opens an email client with no pre-filled subject or guidance, which most visitors on mobile will abandon rather than deal with. Trust signals are actually strong — real photos, a visible owner, some genuine-looking reviews. Content is thin though — only the homepage has any real text, no pages answering common questions like pricing ranges or delivery areas. Based purely on this evaluation, the honest priority isn't a redesign. It's fixing the ordering flow first, since that's actively losing customers who are already interested, and adding a pricing or FAQ page second, since that answers questions before they become friction. This is a made-up example, not a real audit, but it shows exactly the kind of prioritization a proper evaluation makes possible — versus jumping straight to "the homepage needs new photos," which would have missed the actual problem entirely.
Common mistakes students make in this exercise
- Rushing past Step 3 and never actually testing the core function — this is the single most common miss, and it's the step that catches the most serious issues.
- Writing vague notes like "content could be better" instead of specific ones like "the about page doesn't mention who founded the business or why." Vague notes produce vague recommendations later.
- Rating every issue as high severity because everything feels important once you're looking closely. Realistically, not everything is. Force yourself to rank rather than flag everything equally — it's a harder discipline than it sounds.
What to do once the evaluation is finished
Only now — after all seven steps and a completed table — should recommendations enter the picture. And when they do, tie every single suggestion back to a specific finding from your evaluation. "Improve the homepage design" isn't a recommendation grounded in evidence. "Fix the checkout button, which currently doesn't submit on mobile, before making any visual changes" is. That specificity is exactly what separates a student who's memorized a checklist from one who's actually learned to think like a practitioner — and it's the habit worth carrying into every real website you evaluate from here forward, not just this exercise.
