# Reports and sharing Reports are built for the explain-why and fix-or-hand-off steps. nimo tells you what is slow, why it matters, and what to review first. Canonical URL: https://heynimo.com/docs/reports Markdown URL: https://heynimo.com/docs/reports.md ## AI summary Describes the explain-why and fix-or-hand-off parts of the workflow: nimo AI reports, prioritized recommendations, platform-aware quick wins, incident evidence, Agentic readiness, competitor proof reports, comparison methodology, six-month CrUX trend history, visual proof screenshots, copyable fix prompts, Markdown and PDF exports, field and lab source labels, public share links, and client-ready summaries. ## Key points - Reports include a verdict, metrics, deep dives, and prioritized recommendations. - Platform-aware quick wins translate a finding into a simple path for WordPress, Shopify, Webflow, Next.js, Cloudflare, or an unknown stack. - Incident evidence explains stored regressions with scoped evidence, metric deltas, likely owner, confidence, and Linear issue context when enabled. - Agentic readiness is optional and advisory; treat WebMCP, llms.txt, and AI-agent interaction findings as readiness work you can opt into. - Competitor proof reports show who wins on LCP, why they win, and the first safe fix to review or hand off. - Visual proof can add stored screenshots when safe, but LCP, source labels, and proof facts still decide the gap. - Suggested and default competitors are optional. The user confirms the final URLs before any comparison runs. - Copy fix prompts turn a safe first fix into a coding-agent handoff. - Markdown and PDF exports include the same public evidence with source labels. - Share links create public expiring URLs for reports and comparisons. - Use report comparisons for client before-after evidence. ## Sections ### What a report includes - Verdict: a short explanation of the current state of the page. - Metrics: Core Web Vitals and supporting metrics from field and lab data. - Deep dives: images, scripts, fonts, third parties, page entities, search context, and traffic context when available. - Next steps: recommendations ordered by likely user impact, practicality, and safety. - Incident evidence: stored regression evidence when nimo has enough baseline and follow-up data. - Readiness findings: advisory AI-agent readiness checks when the readiness surface is enabled. ### Prioritized recommendations - nimo does not simply repeat every Lighthouse warning. - It ranks work by likely user impact, stack relevance, metric trend, and safety. - A recommendation can be important even when the Lighthouse score looks fine. nimo checks field data first when it exists. ### Platform-aware quick wins - When nimo has a confident stack signal, the report can show one platform-aware quick win for WordPress, Shopify, Webflow, Next.js, or Cloudflare. - Stack detection is best-effort guidance, not a guarantee. Confirm the platform before changing production. - The card keeps the user journey simple: platform, owner, one action, why it comes first, and the confidence note. - Owner labels are explicit: developer, marketer, CMS owner, or hosting/CDN. nimo does not remove plugins, disable apps, edit code, or change Cloudflare settings from public chat. Cloudflare changes require a signed-in user, explicit approval, and safe actions enabled for the account. - Examples: WordPress advice may start with the hero image, plugin scripts, or page cache. Shopify advice may start with image sizing, app embeds, pixels, or theme code. Webflow advice may start with assets, embeds, and first-section interactions. - Next.js advice may start with next/image sizing, font loading, client-only bundle splitting, route caching, or data fetching. Cloudflare advice only points to cache, image delivery, or headers when the evidence supports it and the page is safe to cache. ### Understand field, lab, and missing data - CrUX field data shows real Chrome visits over roughly 28 days. It is not first-party RUM and it is not real-time. - CrUX can lag after a deploy and may use origin-level data when page-level data is missing. - Lighthouse lab data is a point-in-time simulation for the tested URL and device. - Lighthouse is useful for debugging and immediate post-fix checks, but it may not match what real visitors experienced. - If field data fails and lab data passes, fix the field failure first because real visitors are seeing the issue. - If lab data fails and field data passes, treat the lab failure as a diagnostic clue before overriding passing field data. - If CrUX is missing, the page or origin may not have enough Chrome traffic. Use Lighthouse as a baseline, then rerun the same device after each fix. ### Incident evidence - When performance incident tracking is enabled and nimo has enough evidence, a report can show incident evidence for a regression. - The panel focuses on what changed, the metric delta, the affected page or site scope, evidence refs, likely owner, confidence, and recommendation context. - Incident evidence is not a raw trace viewer. It uses stored, scoped evidence so a teammate can understand the regression without exposing cookies, credentials, request headers, raw Lighthouse payloads, or private URLs. - If Linear is configured, nimo can preview an issue from an active incident. - Creating the issue requires an explicit create action, and duplicate issue links are reused when nimo can identify an existing issue. ### Agentic readiness - Agentic readiness is optional and advisory. - It checks whether AI agents can discover and interact with the public site more reliably, using signals such as /llms.txt, WebMCP metadata, declarative forms, AI accessibility, and Lighthouse Agentic Browsing output. - Readiness findings do not mean performance monitoring failed. - Treat them as optional AI-discovery and interaction-quality work, separate from Core Web Vitals, uptime, and incident alerts. - Eligible readiness findings can show a Linear issue preview after opt-in. - nimo keeps the handoff narrow and reuses already ticketed findings instead of creating duplicate work. ### Competitor proof reports - Public competitor comparisons answer the workflow questions before the metric table: find the LCP gap, explain why the faster page wins, and choose the first safe fix to review or hand off. - The leaderboard orders your page and each competitor by LCP, with the source labeled as CrUX field data, Lighthouse lab data, or unavailable. - CrUX field data is the 28-day p75 from real Chrome users. It is the best signal for what visitors experienced, but it can lag after a deploy and may use origin-level data when page-level data is missing. - Lighthouse lab data is a point-in-time test for the exact URL. It is useful right after a fix because you can rerun it immediately. - The proof section compares simple facts such as page weight, JavaScript weight, request count, third-party scripts, TTFB, and render-blocking resources. - The first fix includes an owner, likely impact, and acceptance check so the next step is easy to hand to a developer, marketer, or hosting team. - When safe screenshots are available, visual proof can show your page next to the faster competitor. - When public CrUX history is available, the report shows whether mobile and desktop LCP are improving, flat, or getting slower. - When a comparison mixes CrUX field data and Lighthouse lab data, treat the result as directional. After a deploy, rerun Lighthouse right away and wait 2-4 weeks for CrUX field data to settle. - Public proof reports only include audit facts from public URLs. They do not expose request headers, cookies, secrets, or raw Lighthouse blobs. LCP element snippets are cleaned before display. ### Comparison methodology - Source labels stay visible for every comparison fact: CrUX field data, Lighthouse lab data, URL-level CrUX history, origin-level CrUX history, or unavailable. nimo does not blend field and lab data into one unlabeled score. - Live comparisons run only after the user confirms the URLs and presses Compare speed. Lighthouse lab data is a point-in-time test for the exact URL and device. - CrUX field data reflects the latest available public 28-day Chrome window and can lag after deploys. CrUX trend history uses roughly six months of public history when available. - Competitor watches rerun chosen public URL pairs weekly. - The leaderboard orders pages by measured LCP for that comparison only. It is directional evidence, not a promise of search ranking improvement, conversion lift, Core Web Vitals passing status, or the same order after a later CrUX update or Lighthouse rerun. ### CrUX trend history - CrUX trend history uses public Chrome usage data to show LCP momentum over roughly the last six months. - It is not first-party RUM, it is not real-time analytics, and it may be missing for newer or lower-traffic pages. - The trend section compares the first and latest public LCP values and labels each page as improving, flat, getting slower, or not enough samples. - nimo keeps mobile and desktop trend summaries separate because the same page can move differently on each device. - The report labels whether the trend came from URL-level CrUX history or origin-level CrUX history. - Origin fallback means Chrome did not have enough page-level history. - If a page does not have enough public history, nimo says that plainly and keeps the current Lighthouse and CrUX field labels visible. - Use CrUX trend history to understand momentum, not to prove a fix the same day it ships. For immediate verification, rerun Lighthouse on the same device, then watch CrUX over the next few weeks. ### Visual proof screenshots - Visual proof is a side-by-side screenshot pair from the same kind of Lighthouse lab run used for the comparison. - Screenshots come from a single Lighthouse lab capture per page. Use them as directional evidence, then rerun after a fix. - Visual proof may be unavailable when screenshots are missing, expired, too large, unsupported, or fail safety checks. - Reports use stored PNG or JPEG artifacts from the audit. They do not hotlink competitor screenshots from third-party URLs. - Markdown exports include the visual proof caption only. PDF exports include thumbnails only when the stored image data is safe. - Treat visual proof as the simple screenshot explanation for a measured gap. Use LCP, source labels, proof facts, and a rerun after deploy to decide whether the fix worked. ### Suggested and default competitors - On the public comparison form, nimo can suggest up to three competitor URLs after the user enters their page. - Suggestions are optional. The user can pick a suggestion, edit it, remove it, or ignore suggestions and type competitor URLs manually. - Default competitor presets are editorial starting points used by comparison pages. They prefill known public URLs, but they do not start a live audit by themselves. - nimo only sends the target URL to the suggestion endpoint. Analytics for this flow record counts and source labels, not competitor domains or full URLs. - The public endpoint validates hostnames, rejects private or local targets, rate-limits requests by IP and domain, and returns a manual fallback when suggestions are unavailable. - When Ahrefs-powered organic suggestions are enabled, nimo returns only the normalized public suggestion URLs. It does not expose raw provider payloads or authenticated Ahrefs data. - Before a live comparison runs, the user must confirm one to three competitor URLs by pressing Compare speed. ### Copy fix prompts - When a public comparison has a safe first fix, use Copy fix prompt to copy a concise handoff for Claude Code, Cursor, or another coding agent. - The prompt includes the public URL, winning competitor URL, failing metric, source labels, first fix, sanitized evidence, acceptance criteria, and a rerun instruction. - The prompt tells the agent not to change unrelated behavior and to ask before destructive changes. - The prompt excludes credentials, cookies, request headers, private account data, raw Lighthouse blobs, raw HTML, and URL query strings. - Paste the prompt into your coding tool, review the plan, make the smallest safe change, and rerun the comparison after deploy. ### Export Markdown and PDF - Public competitor comparisons can be copied as Markdown or downloaded as Markdown and PDF. - Markdown is best for tickets, pull request notes, agency task lists, and coding-agent handoffs because it is plain text. - PDF is best for stakeholder or client handoff when the reader needs a compact, readable report. - Both exports include the verdict, compared URLs, leaderboard, proof facts, visual proof caption when available, first fix when available, rerun guidance, generated date, and source labels. - Markdown does not embed screenshots or external image URLs. PDF thumbnails are included only from stored safe screenshot artifacts. - Source labels stay visible in exports because CrUX field data and Lighthouse lab data answer different questions. CrUX shows real Chrome users over a 28-day window; Lighthouse shows an immediate test for the exact URL. - Exports are generated from the public share token on demand. They do not include credentials, cookies, request headers, private account data, raw Lighthouse blobs, raw HTML, or URL query strings. ### Share a report - Use share links to send a report or comparison to a client, teammate, or developer. - Open the report, create the share link, choose the expiry window, and send the link. - The recipient can view the report without signing in and can download the public Markdown or PDF export when exports are enabled. ### Use reports with clients - For client work, save a before audit, make the change, run another audit, and share the comparison. - Good prompt: Summarize this report for a client in five bullets. Focus on business impact and the next fix. ## Related docs - [Quick start](https://heynimo.com/docs) - Start the workflow: find the gap, explain why, fix or hand off, and watch the result. - [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.