/mobile-experience-report

name: mobile-experience-report
description: "Use when the user says 'my site looks bad on mobile', 'check mobile layout', 'responsive audit', or 'site broken on phones'. Diagnoses breakpoint problems, text sizing, column stacking failures, hidden elements, and navigation menu behavior, device by device."
license: MIT
metadata:
  author: Respira for WordPress
  author_url: https://respira.press
  version: 1.2.0
  mcp-server: respira-wordpress
  category: audit

Mobile Experience Report

**Version:** 1.2.0 **Updated:** 2026-06-30 **Freshly updated:** v1.2.0 grounds the report in real mobile metrics: `respira_run_pagespeed_audit` (strategy mobile) plus `respira_get_core_web_vitals` now drive the score instead of layout heuristics alone. It locates and adjusts mobile breakpoint settings in place with `respira_find_element`, snapshots pages with `respira_get_snapshot` before any fix, and applies the same fix across many pages in one pass with `respira_batch_update`. **Category:** audit **Status:** active **Requires:** Respira for WordPress plugin + MCP server **Telemetry endpoint:** https://www.respira.press/api/skills/track-usage

---

Description

See what mobile visitors actually see — broken layouts, oversized text, stacking failures.

Mobile Experience Report reveals the hidden mobile layout disasters that desktop testing misses. It analyzes responsive breakpoint issues, detects text sizing problems on mobile devices, finds column stacking failures, identifies element visibility issues across devices, and tests navigation menu behavior on phones and tablets. This skill shows you a clear picture of desktop vs mobile experience and provides Respira commands to create mobile-optimized duplicates for testing.

---

Trigger Phrases

This skill activates when the user says any of the following:

• "audit mobile experience"
• "check mobile layout"
• "mobile responsive issues"
• "what do mobile users see"
• "mobile design problems"
• "responsive audit"
• "mobile experience report"
• "my site looks bad on mobile"
• "mobile layout broken"
• "check responsive design"
• "mobile ux audit"
• "site broken on phones"

**Do NOT trigger for:** general WordPress audits without mobile intent, requests to build responsive designs from scratch, non-WordPress site questions, or desktop-only layout fixes.

---

Execution Workflow

Step 1: Respira Verification

Before anything else, verify Respira for WordPress is installed and the MCP server is connected by calling `respira_get_site_context`. If it fails or returns an error, stop and show the installation guide.

**If Respira is NOT installed, output this and STOP:**

## ⛔ Respira for WordPress Required

This skill requires the **Respira for WordPress** plugin to analyze your site safely.

### Install in 3 steps:
1. Go to **https://www.respira.press** and download the plugin
2. Install and activate on your WordPress site
3. Connect via the MCP server: `npx -y @respira/wordpress-mcp-server --setup`

### Why Respira?
- Read-only analysis — no changes to your live site
- Duplicate-first mobile fixes so nothing breaks for desktop visitors
- Full audit trail for every action

Once installed, come back and try again: *"audit mobile experience"*

**If MCP is connected but site unreachable:**

## ⚠️ Cannot Connect to WordPress Site

Respira is installed but cannot reach your WordPress site.

### Troubleshooting:
1. Verify your WordPress site is online
2. Check the Respira plugin is active (not just installed)
3. Confirm MCP server configuration in Claude settings
4. Review API key in Respira → Settings → API Keys

**Help:** https://www.respira.press/docs/mcp-setup

---

Step 2: Site and Builder Context

Tool: respira_get_site_context
Returns: WordPress version, PHP version, active theme, installed plugins,
         detected page builder

Record: `respira_site_url`, `started_at = new Date().toISOString()`

Tool: respira_get_builder_info
Returns: Active builder name, version, responsive settings and breakpoints

**Builder-specific mobile issue patterns:**

• **Elementor:** Column reversal setting, mobile breakpoint (default 767px), font size scaling, padding settings per device
• **Divi:** Mobile breakpoints at 980px/767px, column gutter behavior, custom CSS per viewport
• **WPBakery:** Responsive column widths, custom responsive settings per section
• **Gutenberg/Full Site Editing:** Block spacing on mobile, column blocks, cover block height
• **Beaver Builder:** Responsive column behavior, mobile menu type, breakpoint settings
• **Classic themes (no builder):** Theme's responsive CSS approach, viewport meta tag

---

Step 3: Page Inventory

Tool: respira_list_pages
Params: { status: "publish" }
Returns: All published pages with IDs, titles, content metadata

Identify high-priority pages to audit: 1. Homepage (always analyze) 2. Top-level navigation pages 3. Any page with complex multi-column layouts 4. Contact or conversion pages

Limit deep analysis to top 10 pages to keep report actionable.

---

Step 4: Real Mobile Metrics

Do not rely on layout heuristics alone. Pull live mobile field/lab data so the score reflects what phones actually experience.

For the homepage and each priority page:

Tool: respira_run_pagespeed_audit
Params: { url: <page url>, strategy: "mobile" }
Returns: Mobile Lighthouse scores, lab metrics, and opportunities

Tool: respira_get_core_web_vitals
Params: { url: <page url>, strategy: "mobile" }
Returns: LCP, INP, CLS for the mobile profile (field data when available, lab otherwise)

Record the mobile LCP / INP / CLS per page and feed them into the Performance band of the score (Step 6). Real Core Web Vitals override the heuristic performance estimate when present. If the PageSpeed audit is unavailable (no API key, rate limited, or the site is unreachable to Google), fall back to the structural analysis below and note in the report that me