I fixed TestGorilla's sign-up microcopy. What I changed and why.

I have no affiliation with TestGorilla. I just spotted their sign-up form and noticed gaps in the microcopy. I’m just a UX writer who can't stop auditing things, even in my free time.

Sign-up is the moment a user decides whether to trust you or not. If your form is confusing, cold, or unclear, users quietly leave without telling you why.

What is microcopy?

Microcopy is the small functional text inside a product: labels, placeholders, tooltips, button copy, validation messages. They are easily overlooked because they feel tiny, but together they add up and shape how confident a user feels while moving through your product.

When a piece of microcopy feels off, users are slowing down, starting to second-guess themselves, wondering if they did something wrong, and sometimes they just leave.

Context

TestGorilla helps job seekers prove their skills to employers. The emotional stakes are high because people come there hoping to land a job. For this reason, the words on this form matter more than usual.

Problems

At first glance, it looks fine with a clean layout and clear fields. However, it feels copy-heavy. That’s not an issue as long as the copy is clear and guides users through the process.

Problem 1: Brand-centric headline, inconsistent capitalization

“Create your TestGorilla Profile” is brand-centric, not user-focused.

The brand name is already in the logo at the top of the page. Repeating it in the headline doesn't add any value to the user. It actually makes the form feel like it's about the company, not the person filling it in.

A title is an opportunity to give the user a reason to keep going.

How to fix it

In this case, the fix is just removing what doesn't need to be there.

“Create your profile” is enough. The focus is on the user. They feel like the product is built for them.

Problem 2: Obvious subtitle

“Enter your personal email address to create your profile.”

The word personal has a purpose there, and it signals that using a work email might cause issues. This is useful, but the copy never explains why.

When you make a distinction or give a specific instruction, you must justify it. Otherwise, it loses its importance.

How to fix it

Tell users exactly why their email choice matters so much, so they can make the right call from the start and avoid any possible issues later.

“Use an email where employers can reach you” eliminates any guesswork on which email to use. Users understand the reason before starting to type their email address.

Problem 3: Vague tip box

“Tip: If you've previously been invited to take a TestGorilla assessment, use the corresponding email address to sign up.”

Corresponding email address is vague. Corresponding to what? Just saying “the same email” reduces the cognitive load.

How to fix it

“Tip: Got a TestGorilla invite? Sign up with that same email to see your test results.”

This tip is trying to solve a real problem: registered users must use the same email address when signing up, otherwise, they won’t be able to see their test results.

The new tip is shorter and answers the question the user is actually asking: why does this matter? They understand what's at stake if they get it wrong.

Problem 4: Truncated password requirements

  • Contains at least one lowercase

  • Contains at least one uppercase

  • Contains at least one number

  • Contains at least one special character

  • Contains at least 12 characters

The form validates each requirement in real time as the user types. Immediate feedback is always better than a wall of errors after submission. The list format is the right choice because each item needs to be visibly ticked off as it's met.

The issue is the microcopy:

  • The word Contains repeats 5 times.

  • Each line is a sentence fragment: "at least one lowercase”, “at least one uppercase.” What lowercase? What uppercase?

  • The most demanding requirement (12 characters) is listed last, when it should come first to set expectations immediately.

  • The examples of special characters matter too. Once you add examples for special characters, you remove any anxiety before it starts.

How to fix it

  • At least 12 characters

  • 1 uppercase letter

  • 1 lowercase letter

  • 1 number

  • 1 special character (e.g. !, @, #)

Passwords with a lot of requirements are annoying. This is exactly why the copy around them needs to do the work. Copy that feels robotic at this moment only adds friction instead of reducing it. Using numerals (1) instead of spelling out “one” reduces the cognitive load, it’s visual, and users understand each requirement at a glance.

Problem 5: Inconsistent checkboxes

  • I have read and accepted the candidate terms and privacy policy. - past tense and formal.

  • I agree to receive product, marketing, and job communications from TestGorilla. - present tense and light.

These two don’t share a consistent voice or grammatical structure. It feels like two different people wrote them. For the second checkbox, the word “communications” feels corporate, it doesn't sound like TestGorilla's overall voice.

How to fix it

  • *I agree to the candidate terms and privacy policy. Mark it as mandatory. Users can’t enable the CTA if they don’t check the box.

  • I agree to receive updates, offers, and job opportunities from TestGorilla.

Both checkboxes have the same opening, the same tense, and language that sounds like it was written by a real person. Consistency signals care. When a form feels polished and coherent, users trust the product behind it, especially in a moment when they're being asked for consent.

Problem 6: Confusing CTA

"Next ›"

This is the biggest issue on the form. The button is disabled until the user completes all the fields and checks the required box. However, nothing tells them that. If someone fills in their email and password but forgets to check the boxes, they click Next, and nothing happens.

The terms & conditions check box is not marked as a required field. So, when a user tries to click on Next, and it’s not working, confusion starts to build up as they get no feedback or guidance.

Marking required fields with an asterisk (*) does part of the job, as users can scan and see what's still missing.

The button copy has a separate problem of its own.

“Next” implies more steps, more forms to fill out, and more time spent on this process. Users don't know what they're committing to when they click it.

What actually happens?

You land on an email verification screen. That's it. The sign-up is effectively one step. Next doesn't reflect that at all. On the contrary, it creates hesitation right at the moment the user is ready to commit.

How to fix it

“Create my profile” instead of Next.

“Create my profile” tells the user exactly what's about to happen. The ambiguity disappears because the action is named, and it’s a full circle with the header.

“My profile” also carries a sense of ownership. Users know what they're clicking into, which eliminates the hesitation at the end of the process.

Problem 7: Redundant link text

“Already have an account? Log in here”

This is a clean, conversational, and direct piece of copy, however, “here” adds nothing when the phrase is already a link.

How to fix it

Just cut the “here” and keep the whole sentence as a link.

Special mention: Confirmation screen

After clicking Next, the user sees this:

The spam warning is common and practical, but this one is passive. "It may have been marked as spam by your email service" puts the responsibility on the user's email provider in a way that feels like the product is distancing itself from the problem.

How to fix it

“Check your spam if it doesn't arrive within a minute. Sometimes it ends up there.”

Warmer, shorter, and gives the user a clear action instead of a vague explanation. Users know exactly what to do if something goes wrong, and the product feels like it's on their side.

Results

Let’s look at the two forms side by side: same layout, same fields, same structure. The only difference is cleaner copy. That’s it.

The headline focuses on the user. The instructions justify themselves. The password requirements are readable at a glance. The checkboxes speak in one voice. And the button tells you exactly what happens next.

Good microcopy blends perfectly in the form. Users don't notice it. They just feel more confident throughout the process.

The takeaway

Microcopy is easy to deprioritize because no single piece feels important enough to debate. But together, these small moments create the overall experience of using a product for the first time. Every one of these friction points is a moment where a user pauses to re-read. The fixes here are copy changes that remove the hesitation.

Most of the microcopy problems become visible the moment you read them out loud. If they sound like something a person would say, you’re good. If not, they need fixing.

© 2026 Flavia Sasu. All rights reserved.
© 2026 Flavia Sasu. All rights reserved.
© 2026 Flavia Sasu. All rights reserved.

Create a free website with Framer, the website builder loved by startups, designers and agencies.