# Quick start

nimo follows one workflow: Find the gap. Explain why. Fix or hand off. Watch the result. Start here if you want the shortest path from account to useful answer.

Canonical URL: https://heynimo.com/docs
Markdown URL: https://heynimo.com/docs.md

## AI summary

The fastest path for a new user: Find the gap. Explain why. Fix or hand off. Watch the result. Create an account, add a site, run the first audit, connect Telegram or Slack, and ask the nimo agent a focused performance question.

## Key points

- Find the gap with CrUX field data, Lighthouse diagnostics, history, and competitor context when useful.
- Explain why the gap matters with source labels instead of raw audit jargon.
- Fix or hand off one safe first action with owner and acceptance criteria.
- Watch the result with reruns, scheduled audits, competitor watches, and uptime checks.
- Create an account from the public sign-in flow.
- Add one production site URL.
- Add important pages from the Pages tab when Page Control is available.
- Run the first audit.
- Connect Telegram, Slack, or both.
- Ask: What should I fix first on mobile, and why does it matter?

## Sections

### Start in three minutes

- Create your account so nimo can save sites, history, alerts, and integrations.
- Paste the public URL you want nimo to monitor. The dashboard starts the first audit and turns on uptime monitoring for that site. If the Pages tab is available, add the most important URLs after the first site audit.
- Connect Telegram, Slack, or both so nimo can send audit updates and answer follow-up questions in chat.
- When the first audit finishes, ask one focused question: What should I fix first on mobile, and why does it matter?

### What happens next

- After the first audit, nimo shows a plain-language report with real visitor data from Chrome when available, simulated Lighthouse test data, prioritized recommendations, chat follow-ups, uptime status, audit history, and incident evidence when enough regression evidence exists.
- Use the same workflow after every important change: Find the gap. Explain why. Fix or hand off. Watch the result.
- Smaller or newer sites may not have enough Chrome field data yet. nimo says that clearly and uses the simulated test as a diagnostic baseline.

### First prompts to try

- Ask short prompts and make one decision at a time.
- Good prompts: What is the single biggest reason this page feels slow? Which slow page is most likely hurting search traffic or conversions? Compare my last two audits. Did the fix actually help?

### Keep it running

- Use Telegram or Slack for chat, audits, site switching, and alerts.
- Use MCP when Claude Code, Cursor, Windsurf, or another agent needs to read audit history and run checks.
- Connect Google data for search and traffic context.
- Connect Cloudflare when you want nimo to suggest edge fixes for images, compression, caching, and headers.


## Related docs

- [Set up a site](https://heynimo.com/docs/setup) - Add your site, choose important pages, pick a schedule, and understand what nimo checks.
- [Telegram](https://heynimo.com/docs/telegram) - Connect Telegram and use nimo from chat.
- [MCP for agents](https://heynimo.com/docs/mcp) - Use public docs MCP, or connect an authenticated MCP client to nimo.
- [Audits](https://heynimo.com/docs/audits) - Find the gap with CrUX field data, Lighthouse lab checks, history, and plain-language results.
- [Monitoring and alerts](https://heynimo.com/docs/monitoring) - Watch the result with scheduled audits, competitor watches, incidents, uptime checks, and alerts.