First CH Apps / Website Mobile-Friendly Check — a 3-question card to send by LINE or chat

Website Mobile-Friendly Check — a 3-question card to send by LINE or chat

Pick up what to check from your URL and make a free question card to send to family or regulars.

How it works and details

Unlike preview tools that show your page at several screen sizes, this reads the HTML and CSS for three points — can the phone number be tapped, does the page fit the screen width, and is the text readable and zoomable — and turns yes/no questions into a chat message and a QR-code image so someone can check on a real phone.

Use your home page or a shop information page. We read the first 512KB of that page and up to 3 stylesheets from the same site.

See a sample (fictional shop)

Please look at our site1. When you tap the phone number on the page, does your phone offer to call it?2. Does the page fit the screen without sliding it sideways?3. Could you find the opening hours and closed days?

Questions for the person who will look at it on a phone. You can swap them (up to 3). The QR code and link carry ?ref=sumaho-check so your analytics can tell visits from this card apart.

What gets checked

1. PhoneWhether each phone number in the text has a matching tel: linkCan it be tapped to call?

2. Sideways scrollviewport width=device-width, and fixed widths of 900px or moreDoes it fit the screen?

3. Text & zoomZoom blocking (user-scalable=no, maximum-scale=1) and text below 12pxReadable and zoomable?

How to read this

Google retired its Mobile-Friendly Test in December 2023. The surest way to see how your site looks on a phone now is to have someone actually look at it on one. This page prepares that request.

There is no pass/fail and no score. The three states are "Check this" (something worth checking was written), "Nothing found" (nothing in what we read) and "Can't tell" (not fully read, or the override can't be decided). A real phone settles it.

CSS is followed in source order for a 375px-wide screen. A fixed width reset inside @media (max-width: …) is not flagged. When a differently written selector or a non-width condition might override it, we say "Can't tell".

Phone numbers are matched in Japanese formats only (10–11 digits starting with 0, or +81). Numbers inside images or added later by JavaScript can't be read.

iPhones sometimes link numbers automatically even without tel:, but not with format-detection telephone=no or with some ways of writing the number. A tel: link is the reliable way.

SERVER PROCESSING — what we send and what we keep

Sent: only the URL you enter. Our server (Cloudflare Workers) makes DNS lookups to check the destination is safe, then fetches the page with a public GET (first 512KB). It then fetches up to 3 stylesheets from the same site that the page loads (256KB each, 5 seconds, 2 redirects, never leaving the site). Internal networks, localhost and private IPs are never fetched.

Stored: nothing. The URL, HTML, CSS, result and chosen questions are never written to a database (no KV, no D1) and leave memory when the request ends. The card image and QR code are drawn on your device and never sent to us.

Returned: the state of the three points, where each finding is (HTML line, CSS file and line), a short re-written form of it, how to fix it, and the questions. The page and CSS themselves are never returned.

Rate: each client may make 20 cards per 10 minutes.

Use it as an API

POST /hp-sumaho-check/api/check with JSON ({"url": "https://example.com/", "lang": "en"}) to get the three states, locations, fixes and the chosen questions as JSON.