AgentReady.me

Local Lighthouse evidence importer

Local JSON analysis · Free browser tool

Lighthouse Agentic Importer

Use the Lighthouse report you already generated as prerequisite evidence for agent operation. The importer keeps Google’s category scores distinct from AgentReady journey outcomes and never invents a blended “agent score.”

1 · Define and run

GoalContract input

Start with the included example, then replace it with one narrow customer goal and its real authority boundary.

Lighthouse report JSON

Parsed locally in this browser · maximum file size 2 MB

Example JSON loaded

Authority, assertions, and safe stop

Selecting a sandbox records a declaration in the contract; a later executor must still verify written authorization, isolation, fixture reset, and revocation. This public tool does not execute the sandbox run.

By running this tool, you confirm the submitted inputs are within your authorized scope.

2 · Inspect and export

Evidence bundle

Your structured result will appear here

Review the example GoalContract, adjust its boundaries, and run the tool. No action is taken beyond the boundary shown on this page.

Why this test exists

A practical Lighthouse Agentic audit importer

A Lighthouse report is useful evidence, but a score by itself is not a customer journey. The importer keeps the original audit observations attached to a GoalContract so teams can distinguish an automated page diagnostic from a verified business outcome.

Your JSON stays in the browser for this import. AgentReady checks whether the artifact has a recognizable Lighthouse shape, projects relevant observations into the shared evidence model, and generates a rerun-ready bundle you can hand to engineering.

Repeatable workflow

From a bounded goal to an inspectable receipt

  1. 1

    Export Lighthouse JSON

    Run Lighthouse in the environment and configuration you intend to compare, then save the full JSON report.

  2. 2

    Define the customer goal

    Record the target URL, allowed actions, success assertions, safe stop, and authoritative readback.

  3. 3

    Import locally

    Choose or paste the JSON file. The workbench parses it in your browser and creates normalized evidence.

  4. 4

    Save a rerun bundle

    Download the execution bundle and preserve the source report, contract, timestamp, and unobservable checks for the next rerun.

Read the evidence precisely

Four interpretation rules

Audit version matters

Keep the Lighthouse version, configuration, environment, and observation time with every comparison.

Coverage is a denominator

Every audit present in the bounded source report stays visible. An audit absent from that report cannot be inferred as a zero or a pass.

Page evidence is not outcome proof

A semantic control can exist while login, form submission, checkout, or readback still fails later.

Fixes need a rerun

Use the imported evidence to prioritize changes, then produce a new receipt under a compatible contract.

Included in this tool

Observable checks and exports

  • Local JSON parsing with a bounded report size
  • Preservation of Lighthouse version, final URL, audit ID, score, and display value
  • Explicit separation between page-quality evidence and journey success
  • Exportable rerun contract for the most relevant failed or partial audits

Keep outside the claim

Known limitations

  • The importer does not upload, rerun, or modify the Lighthouse report.
  • Category scores remain Lighthouse scores and are not converted into AgentReady scores.
  • A browser journey still needs separate task execution and authoritative outcome readback.

Frequently asked questions

Which Lighthouse JSON should I import?

Export the full Lighthouse Result JSON from Chrome DevTools, Lighthouse CI, or another compatible runner. The file should include lighthouseVersion, audits, and ideally finalUrl and fetchTime.

Does a 100 Lighthouse score mean my site is agent-ready?

No. Lighthouse covers valuable prerequisites such as accessibility, performance, SEO, and best practices, but it does not prove a delegated task can be completed safely.

Is the report uploaded to AgentReady?

No. This release parses the JSON in your browser and sends only allow-listed tool event names and count buckets to analytics, never report contents.

Continue the investigation

Related tools and field research

Read the AgentReady methodology

Public scan projection

Agent Access Matrix

Compare robots policy, simulated agent user-agent responses, server-rendered content, browser stability, CAPTCHA, and security evidence in one public-site preflight.

Open tool

Planning artifact

Journey Contract Builder

Define the goal, starting state, allowed and prohibited actions, safe stop, assertions, and authoritative readback before an agent touches a site.

Open tool

Public scan projection

Stripe Link Checkout Preflight

Check the public substrate an agent needs before checkout: product data, structured prices, price parity, policies, HTTPS, and discoverable interaction evidence.

Open tool

Source-backed AgentReady analysis

Lighthouse Agentic Browsing Audit Agent Readiness Score Vs Journey Success

Measured comparisons

Use receipts—not anecdotes—in a leaderboard

AgentReady's public leaderboard model requires owner opt-in, category fit, compatible scanner versions, observation windows, denominators, and evidence coverage. A tool export is an input to that process, not automatic publication.

View leaderboards

Need the whole public-site baseline?

Run the free AgentReady scan for discovery, semantics, browser compatibility, public forms, safety signals, and evidence-backed fixes.

Scan a public URL