A Mobile-Friendly White Page: What to Check Before You Launch

A person who taps an ad most often opens the site on a phone. Both Google's and Meta's rules require the site to work properly: Google says "on common browsers and devices", Meta says it must be "accessible" and "function properly". So the mobile version is part of the basic site check, not an optional extra.

What actually breaks on a phone

1. No viewport tag

Without <meta name="viewport">, a phone lays the page out as if the screen were about 980 pixels wide and then scales it down. The text comes out tiny and the buttons minuscule. The tag is needed on every page of the site.

2. The menu doesn't collapse

A horizontal menu with seven items doesn't fit on a phone. You need a burger menu that opens the list on tap. Make sure it works on all pages, not just the home page.

3. The grid doesn't reflow

Three cards in a row on desktop should become a single column on a phone. If the columns stay side by side, they run past the edge of the screen.

4. Tiny fonts

Text you have to pinch-zoom annoys the visitor and signals a site nobody thought through. Body text should be readable without zooming.

5. Horizontal scroll

If the page is wider than the screen, people have to drag it sideways. A common cause is fixed-width elements wider than the screen: wide tables, images with no max width, blocks with a pixel width.

How to check in five minutes

1. Open the site on a real phone, not just a shrunken browser window on a computer.
2. Use the menu on several pages: home, contact, policy.
3. Scroll the page top to bottom and check there is no sideways movement.
4. Submit the form and make sure the button works with a finger and the success message is visible.
5. Open the site on a slow connection and check the page doesn't jump around while loading.

How it works in WhiteCraft

WhiteCraft sites are static HTML+CSS. Before download, the health score checks not the template but the finished, assembled site:

• whether the viewport tag is on every page;
• whether the navigation has a burger or another menu toggle;
• whether cards and grids reflow for a narrow screen;
• whether there are font sizes that are too small;
• whether there are fixed-width blocks wider than a phone screen.

If something is found, the report shows a warning with an explanation. More on the features page.

What this doesn't replace: looking at it on a real device. An automatic check catches common mistakes but can't judge usability the way a person does.

Checklist

• The viewport tag is on every page
• The menu collapses and works on all pages
• Cards become a single column on a narrow screen
• Body text is readable without zooming
• No horizontal scroll
• The form submits from a phone and the success message is visible
• The site was checked on a real phone

The full pre-launch list is in the white page checklist, and the rejection reasons tied to a site that "doesn't work" are in why a white page gets rejected.