Mobile Friendly Checker

Check if web pages are mobile-friendly with viewport, responsive design, and touch target analysis.

What does Mobile Friendly Checker do?

This actor checks mobile-friendliness of web pages. It analyzes the viewport meta tag, responsive design patterns (media queries, flexbox, grid), touch target sizes, font sizes, and other mobile UX factors. Returns a score from 0 to 100 and actionable issues for each page.

Process hundreds of URLs in a single run to audit mobile readiness across an entire website. Results include detailed breakdowns of viewport configuration, responsive design usage, and a categorized list of issues to fix.

Use cases

• SEO specialists -- check if pages pass mobile-friendly criteria that search engines use as a ranking factor
• Front-end developers -- verify viewport and media query setup across all pages after a responsive redesign
• UX designers -- find small touch targets and tiny fonts that harm the mobile user experience
• QA teams -- validate mobile-friendliness after a site migration, redesign, or CMS update
• Agency teams -- run mobile audits across multiple client websites and generate reports with scores
• Product managers -- verify that new features and landing pages meet mobile usability standards before launch
• Accessibility specialists -- identify mobile UX barriers like small touch targets and unreadable font sizes

Why use Mobile Friendly Checker?

• Comprehensive analysis -- checks viewport, media queries, flexbox, grid, touch targets, font sizes, and horizontal scroll
• Scoring system -- each page gets a 0-100 score for quick assessment and comparison
• Actionable issues -- returns specific, categorized issues with clear descriptions
• Batch processing -- check hundreds of URLs in a single run
• Structured output -- machine-readable JSON ready for reports, dashboards, or automation
• Pay-per-event pricing -- cost-effective at scale, just $0.001 per URL

Input parameters

Parameter	Type	Required	Default	Description
urls	string[]	Yes	--	List of URLs to check for mobile-friendliness

Example input

{
    "urls": [
        "https://www.google.com",
        "https://www.wikipedia.org",
        "https://example.com"
    ]
}

Output example

{
    "url": "https://www.google.com",
    "isMobileFriendly": true,
    "score": 95,
    "viewport": {
        "found": true,
        "content": "width=device-width,initial-scale=1",
        "hasWidthDeviceWidth": true,
        "hasInitialScale": true
    },
    "responsiveDesign": {
        "hasMediaQueries": true,
        "mediaQueryCount": 5,
        "usesFlexbox": true,
        "usesGrid": false,
        "hasHorizontalScroll": false,
        "fixedWidthElements": 0
    },
    "issues": [],
    "issueCount": 0,
    "error": null,
    "checkedAt": "2026-03-01T12:00:00.000Z"
}

How much does it cost?

Event	Price	Description
Start	$0.035	One-time per run
URL checked	$0.001	Per URL checked

Example costs:

• 10 URLs: $0.035 + 10 x $0.001 = $0.045
• 100 URLs: $0.035 + 100 x $0.001 = $0.135
• 1,000 URLs: $0.035 + 1,000 x $0.001 = $1.035

Using the Apify API

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('automation-lab/mobile-friendly-checker').call({
    urls: ['https://www.google.com'],
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_TOKEN')
run = client.actor('automation-lab/mobile-friendly-checker').call(run_input={
    'urls': ['https://www.google.com'],
})
items = client.dataset(run['defaultDatasetId']).list_items().items
for item in items:
    print(f'{item["url"]}: score={item["score"]}, mobile-friendly={item["isMobileFriendly"]}')

Integrations

Mobile Friendly Checker integrates with your existing workflow through the Apify platform. Connect it to Make (formerly Integromat), Zapier, or n8n to schedule regular mobile audits and route results to other tools. Export scores to Google Sheets for client reporting, send alerts to Slack when pages drop below a mobile-friendliness threshold, or use webhooks to trigger follow-up actions in your deployment pipeline.

Common integration patterns include:

• Post-deployment check -- trigger a mobile audit after each deployment via webhook and alert the team if any page score drops below 80
• Client reporting -- schedule monthly runs across client websites and export scores to Google Sheets for review meetings
• SEO monitoring -- combine with scheduled Apify runs to track mobile-friendliness trends over time and correlate with search ranking changes

Tips and best practices

• Focus on pages with low scores first -- sort results by score to prioritize the worst offenders for your development team.
• Check the viewport tag -- a missing or misconfigured viewport meta tag is the most common mobile-friendliness issue and the easiest to fix.
• Monitor after deployments -- schedule runs after each deployment to catch mobile regressions before users do.
• Combine with HTML Validator -- pair mobile-friendliness checks with HTML validation for a comprehensive front-end quality audit.
• Use the responsiveDesign object -- check whether pages use modern layout techniques (flexbox, grid) or rely on fixed widths that break on mobile.

FAQ

What does the score mean? The score is a number from 0 to 100 based on multiple mobile-friendliness factors including viewport configuration, responsive design patterns, touch target sizes, and font sizes. A score of 90+ generally indicates a mobile-friendly page. Scores below 70 suggest significant mobile usability problems.

Does it render the page in a mobile browser? No. The actor analyzes the page HTML and CSS via HTTP requests without launching a browser. It checks for viewport tags, media queries, flexbox/grid usage, and other signals that indicate mobile-friendliness.

Is this the same as Google's Mobile-Friendly Test? No. This actor performs its own analysis based on common mobile-friendliness criteria. It checks many of the same factors (viewport, touch targets, font sizes) but is not a direct replica of any specific search engine test.

What issues does it detect? Common issues include missing viewport meta tag, missing width=device-width in viewport, no media queries detected, use of fixed-width elements, small touch targets, tiny font sizes, and horizontal scrolling. Each issue includes a description and category.

How many URLs can I check in one run? There is no hard limit. The actor processes URLs concurrently, making it efficient for auditing hundreds or thousands of pages. Each URL is billed at $0.001.