User experience

User experience analysis
what’s reviewed and why it matters

User experience is how comfortable your website feels to the person using it: that it looks right on a phone, that links lead somewhere, that nothing jumps around or breaks. Wakaris reviews it with 19 checks and explains every finding in plain language.

  • 19 checks
  • 6 possible findings
  • 6 guides
What’s reviewed

What Wakaris checks
in your website’s user experience

That’s 19 checks grouped into 6 blocks. Each block is a finding that can show up in your report.

Finding01/ 06

Blocks3 checks

Responsive design

More than half of visits come from a phone, and a website that spills off the screen isn’t hard to read: it can’t be read. You have to drag sideways for every line of text.

What it checks

  • Viewport configuredChecks the meta[name="viewport"] tag. No finding if there is one and it contains width=device-width; limits if it exists but doesn’t declare it; blocks if it is missing or declares a fixed width in pixels.
  • Responsive at 375 pxRenders at 375 CSS px wide and compares the actual content width with the screen width. No finding if it doesn’t exceed it; blocks if it overflows.
  • Responsive at 768 pxThe same test at 768 CSS px wide. No finding if the content doesn’t exceed the width; blocks if it overflows.
Read the guide: Responsive design 

Finding02/ 06

Limits3 checks

Navigation integrity

A broken link is a broken promise at the worst moment: just when someone had decided to move forward. And the one that hurts most is the one leading to the contact page or the catalog.

What it checks

  • Broken linksChecks the HTTP and HTTPS targets linked from the page. No finding if the final responses are 2xx or 3xx; blocks if at least one final target is 4xx or 5xx; inconclusive if a timeout or an anti-bot check prevents determining the status.
  • Invalid link URLsTries to resolve each HTTP or HTTPS href with the standard URL parser. No finding if none is invalid; blocks if at least one can’t be resolved.
  • Broken internal anchorsFor links to a fragment (#) on the same page, checks that the matching target exists. No finding if all of them resolve; blocks if at least one doesn’t exist.
Read the guide: Navigation integrity 

Finding03/ 06

Limits4 checks

Visual integrity

It’s the failure that breeds the most distrust of all, because you can see it: a broken image on a product page plants doubt about whether the order will ever arrive.

What it checks

  • Broken imagesOnce loading finishes, checks the visible images. No finding if all have their resource loaded; blocks if any visible image has no natural width or its resource fails.
  • Failed stylesheetsChecks the CSS resources the page uses. No finding if all load; blocks if any returns 4xx, 5xx or fails to load.
  • Failed web fontsChecks the fonts requested by the page. No finding if no required font ends in an error state; blocks if at least one fails.
  • Distorted imagesCompares each image’s natural aspect ratio with the ratio it’s displayed at. No finding if none is flagged; blocks if any appears distorted.
Read the guide: Visual integrity 

Finding04/ 06

Limits3 checks

Interface errors

A JavaScript error doesn’t always break the page: it breaks what came after. The script stops where it failed, and the dropdown that was supposed to open or the button that was supposed to send the form are left unwired.

What it checks

  • Unhandled JavaScript exceptionsLogs exceptions not caught during load. No finding if there are none; blocks if there is at least one.
  • Console errorsLogs error-level messages generated during load. No finding if there are none; blocks if there is at least one.
  • Unhandled rejected promisesLogs unhandledrejection events. No finding if there are none; blocks if there is at least one.
Read the guide: Interface errors 

Finding05/ 06

Limits4 checks

Automatic interruptions

A permission requested on arrival is almost always denied, and the denial is permanent: the browser remembers it. Asking at the worst moment isn’t just annoying, it burns your only chance of getting it.

What it checks

  • Automatic geolocation requestDuring the initial load, before any interaction, detects whether the page asks for location permission. No finding if there is no request; blocks if there is at least one.
  • Automatic notification requestDetects whether notification permission is requested before any interaction. No finding if there are none; blocks if there is at least one.
  • Automatic camera or microphone requestDetects whether camera or microphone access is requested before any interaction. No finding if there are none; blocks if there is at least one.
  • Audible autoplayDetects audio or video that starts playing with audible sound before any interaction. No finding if there are none; blocks if there is at least one.
Read the guide: Automatic interruptions 

Finding06/ 06

Affects2 checks

Visual readability

A line that’s too long is tiring for a physical reason: when the eye reaches the end, it has to find the start of the next one, and the longer the line, the more often a line gets skipped or reread.

What it checks

  • Line lengthMeasures visible characters per rendered line in text blocks. No finding if no line exceeds 80 characters; blocks if at least one does.
  • Justified textDetects multi-line text blocks with text-align: justify. No finding if there are none; blocks if there is at least one.
Read the guide: Visual readability 

The label tells you how much each finding weighs: Blocks critical,Limits important,Affects could be better.

Why it matters

Why the experience on your website
matters

Nobody writes to tell you your website is awkward to use: they simply leave.

  • It’s used on mobile

    A website designed only for a big screen forces people to zoom in, scroll sideways or aim at tiny buttons. On a phone, that’s noticed instantly.

  • Broken things cost trust

    A link that leads nowhere or an image that doesn’t load makes people think the website is neglected, and with it, whoever is behind it.

  • Easy things get finished

    When reading, moving around and tapping take no effort, people make it to the end: they read the page, fill in the form, ask for what they came to ask for.

To understand it

User experience guides
to understand each finding

Each guide explains one finding from this area in plain language: what it is, how it’s measured, why it matters to you and how to fix it. The technical part is kept separate, for whoever looks after your website.

6guides on user experience

See the 6 guides
Frequently asked questions

Common questions
on user experience

Does Wakaris give an opinion on my website’s design?

No. It doesn’t judge whether it’s attractive or whether the colours are well chosen: that’s a matter of taste and brand. It checks things that can be measured, such as whether the content fits on a phone screen, whether the links work or whether the text is comfortable to read.

How can an automated analysis measure experience?

It loads your page in a real browser, at phone and computer sizes, and watches what happens: whether anything spills off the screen, whether there are errors, whether pop-ups interrupt. It doesn’t replace testing it with people, but it does catch what fails every time.

My website looks fine on my phone. Why is there a finding?

Because there are many screen sizes and yours is just one of them. Besides, anyone who knows a website gets used to its flaws and stops seeing them. The finding says which element is causing trouble and at which size, so you can check it.

How is it different from accessibility?

They overlap, but they’re not the same. User experience looks at whether the website is comfortable for anyone. Accessibility looks at whether people with a disability, or who browse with assistive technology, can use it too. That’s why they’re separate areas.

Who has to fix whatever comes up?

Whoever handles your website’s design or development. Every finding comes explained, with the evidence that proves it and a ready-made prompt to fix it with an AI, and you can share it with a link.

How much does the user experience analysis cost?

Nothing. Analysing a page is free, asks for no sign-up or card and gives you the result in a few seconds. User experience is reviewed alongside the other eight areas in the same analysis.