UICheck

How it works

From a URL to a fix list in minutes

No install, no scripts and no access to your code. UICheck opens your site in real browsers at every screen size and checks it the way a careful tester would.

  1. 1

    Paste a URL

    Any public page: a live site, a staging link or a client preview. It works the same on WordPress, Shopify, Webflow, Next.js or plain HTML, because UICheck tests what visitors see, not your code. Choose a single page, or a full-site check that finds your pages from the sitemap and links.

  2. 2

    Pick screens and browsers

    Free checks cover five sizes from phone to desktop in Chrome. Lens and Prism add 19 named devices, custom widths, Safari and Firefox, the 320–1920px breakpoint sweep and a Figma frame to compare with the design.

  3. 3

    Watch every screen being tested

    Each size opens in its own real browser and you see it happen live. A single page usually takes under a minute; full-site checks run in the background and we email you when the report is ready.

  4. 4

    Read what’s wrong and how to fix it

    Every problem is marked on the screenshot where it happens, rated critical, major or minor, and explained in plain language: what it is, why it matters and what to change. Developers still get the selector and the measurements.

  5. 5

    Fix, recheck and share

    Mark intentional findings as by design so they stop counting. Mark fixes as done, or close their task in your tracker, and UICheck checks the page again to confirm them, or reopens them. Send the client a share link that needs no login, or a PDF or Excel report.

What gets checked

Everything a careful tester would look at

Behind the scenes

Before any check runs

Flaky screenshots cause false alarms, so every page is brought to a steady, fully loaded state first.

  1. 1

    Loads the page like a visitor

    A fresh browser for each screen size, following redirects, and waiting for the network to calm down.

  2. 2

    Stops the motion

    Animations and transitions are switched off, so screenshots are sharp and the same every time.

  3. 3

    Scrolls the whole page

    Part of a screen at a time, so lazy-loaded images and sections appear just as they would for a reader.

  4. 4

    Waits for the layout to settle

    Sticky headers, sliders and late content get a moment until two readings agree.

  5. 5

    Keeps what visitors see

    Analytics and session recorders are blocked to save time; ads stay, because an empty ad slot would look like a bug.

  6. 6

    Stays safe

    Private and internal network addresses are refused, and checks only read pages: nothing on your site is changed.

Scoring

One number per screen, and an honest total

Each screen starts at 100 and loses points for every problem. The overall score blends the average with the worst screen, so a site that is broken on phones can’t hide behind perfect desktop scores.

Critical −25Major −8Minor −2
See everything UICheck checks

53390px phone

Start100

● Sideways scroll-25

● Cut-off heading-8

● Overlapping button-8

● Small tap targets ×3-6

Score53

After the report

Keep the site fixed, not just checked once

A report is the start. These keep problems from coming back after launch.

  • Since your last check

    Every new check is compared with the previous one: what got fixed, what’s new and what’s still there.

  • Weekly monitoring

    Key pages are re-checked every week; you get an email only when something changes.

  • Send to Slack

    Post a report’s summary and top problems to your team’s channel in one click.

  • Issues in Linear, Jira or GitHub

    Turn a finding into an issue with the screenshot and the fix in one click, or send every critical one at once.

  • Live view

    Every screen size side by side in device frames, scrolling together. Prism adds the live site, clickable on four sizes at once.

  • Reports with your brand

    PDF and Excel exports for clients; on Prism they carry your agency’s logo and colours.

  • Checks in CI

    The uicheck command line runs a check on every deploy and fails the build on critical problems.

Hard-to-reach sites

Staging, logins and bot protection

Most sites just work. For the ones that don’t let strangers in, there’s a safe way through.

  • 01

    Password-protected staging

    Add the staging login when you start a check. It’s sent only to that site, encrypted while the check runs and deleted after.

  • 02

    Sites behind Cloudflare or bot protection

    Create a site access key in your account and add one allow rule; UICheck sends the key only to your site. How to set it up

  • 03

    Pages behind a login form

    Checks can’t sign in to member areas. Use a preview or share link that opens the page without logging in.

FAQ

Questions, answered

Something else? Ask us

Do I need to install anything or share my code?

No. UICheck opens the public URL in real browsers in the cloud. It never needs your code, a plugin or server access.

How long does a check take?

A single page usually takes under a minute. Full-site checks take a few minutes and run in the background; we email you when the report is ready.

Which screen sizes are tested?

Free checks cover five sizes from a 360px phone to a 1440px desktop. Lens and Prism add tablet landscape, Full HD, 19 named devices, custom widths and the 320–1920px breakpoint sweep.

Can it test a staging site?

Yes. Any URL a browser can open works, including password-protected staging (basic auth) and sites behind Cloudflare with a site access key.

What if a finding is intentional?

Mark it as by design and it stops counting on that page in future checks. Mark real problems as fixed, or close their task in your tracker, and UICheck checks the page again and confirms them.

Is it safe to run on a live site?

Yes. Checks only read pages like a visitor. They never submit forms or change anything, and private network addresses are refused.

Try it on your own site

Free account, 5 checks a day, no card. Your first report is ready in about a minute.