Website Audit Report: Phone

In the free website audit and the report

A mobile-friendly website test on every client site.

Most visits arrive on a phone. The mobile-friendly checks read each page at a small phone's width: a viewport tag, body text large enough to read, tap targets large enough to press, a page that fits the screen and pinch zoom left on. The Website Audit Report runs them on the site's public pages, on our servers.

What an Accessibility Reviewer brings.

An Accessibility Reviewer reads the page the way a phone visitor meets it: small screen, a thumb instead of a mouse and no patience for sideways scrolling.

Checks the page is set up for phones: a viewport tag and pinch zoom left on.

Measures at a 360 px width: body text size, tap target size and whether the page overflows sideways.

Each check names the WCAG 2.2 success criterion it comes from where there is one, so a fix is checked against a standard.

what we check against

Phone, read at a small phone's width.

360 px phones

Pages that overflow sideways on a small screen

Tap targets

Buttons and links large enough to press, from WCAG 2.2

Pinch zoom

Zoom left on, as WCAG 2.2 asks

Viewport

A viewport tag so the page sizes to the phone

what it checks

The mobile-friendly checks, as data.

They run in the free website audit and the Website Audit Report, on our servers.

  • phoneEvery page has a responsive viewportchecked
  • phoneBody text is 16 px or largerchecked
  • phoneTap targets are at least 24 pxchecked
  • phonePages fit a 360 px screenchecked
  • phonePinch zoom workschecked

In the report

audit northside-dental.exampleEnter

why it matters

Why mobile-friendly matters to your client.

Phone visitors leave fast

Text too small to read or a page that scrolls sideways sends a phone visitor back to the search results.

Search ranks the phone version

Google indexes the mobile version of a page first, so phone problems are search problems too.

Fixes are usually CSS

Most phone findings are a font size, a button size or a width, quick to fix and easy to show the client.

what you get back

What the mobile-friendly checks deliver.

Runs against

Any public site, rendered at a small phone's width the way a visitor sees it.

By page

Each finding names the pages it was found on, so the fix lands where it is needed.

You get

Ranked phone findings in the Website Audit Report, each with why it matters and how to fix it.

the fix workflow

From finding to fixed, in three steps.

  • Send one client site

    Start with the free website audit. No card, nothing to install.

  • The mobile-friendly checks run

    On our servers, over the site's public pages, the same way every time.

  • Fix, quote and re-check

    Each finding carries the fix and a task card your team can take. The next report shows it cleared.

in the report

How mobile-friendly reads in the report.

Phone checks

The mobile-friendly sweep, ranked by impact, in every website audit and report.

Pairs with Accessibility

A page that works on a phone is most of the way to one that works for everyone. The Accessibility checks run in the same report.

See it in a sample

A sample report shows every section as your client sees it.

See the sample report

questions

Questions about mobile-friendly.

Is this a mobile-friendly test?

Yes. It reads each page at a 360 px phone width and checks the viewport, text size, tap targets, overflow and pinch zoom.

Does it test on a real phone?

No. It renders the page at a phone's width on our servers. It does not use a phone's browser or touch.

Does it test tablets?

Not yet. Tablet checks are on the roadmap; today the report reads desktop and phone widths.

Phone is in every Website Audit Report.

Start with a free website audit on one client site, then report on every site you look after, under your brand.