What can the Browser Inspector test?

The Browser Inspector can test page performance (load times, Core Web Vitals), functionality (forms, buttons, interactions), tracking (pixels, analytics tags), and visual appearance (screenshots). It provides evidence of issues, not just reports.

How does the Browser Inspector capture evidence?

It loads real pages in a browser, captures screenshots at key moments, records console logs and errors, runs performance traces, and saves network requests. All evidence is attached to the research for verification.

Can the Browser Inspector verify tracking implementations?

Yes, it can check if tracking pixels fire correctly, verify GTM implementations, confirm conversion tags work, and identify tracking issues like 404 errors or blocked requests.

All agents

Visual Evidence

Browser Inspector

Tests what actually happens when pages load. Visual evidence of bugs, not just reports.

The Browser Inspector uses Hyperbrowser and Chrome DevTools to load real pages, run performance traces, capture screenshots, check for console errors, and verify tracking fires correctly.

Get started See how Inteldo orchestrates

yoursite.com/checkout

3 screenshots

2 errors

How it works

See what happens

Not descriptions of problems. Evidence of them.
Browser Inspector shows the truth.

The Load

How does the page perform?

Core Web Vitals, load times, resource sizes. Performance trace with actual measurements, not estimates.

Performance trace

How does the page perform?

LCP

2.4s< 2.5s

CLS

0.05< 0.1

INP

180ms< 200ms

TTFB

420ms< 800ms

LCP blocked by 2.4MB hero image

The Interaction

Does everything work?

Click buttons, fill forms, trigger events. Verify that functionality actually works, not just that elements exist.

Interaction test

Does everything work?

Click 'Add to Cart'No response

Fill email fieldAccepted

Submit formNo handler

Check trackingGTM fired

The Evidence

What does the error say?

Console logs, network errors, JavaScript exceptions. The actual error messages, not guesses about what went wrong.

1 agents working

0:08

Browser Inspector

Loading page...

The Screenshot

What does the user see?

Visual evidence of the problem. Screenshots at key moments showing exactly what happened.

Key Insight

Submit button has no click handler. JS error in console.

Submit

JS Error

TypeError at checkout.js:142. Button element exists but addEventListener missing.

screenshot.png

console-errors.md

Sound familiar?

Questions about pages

These used to require opening DevTools and digging. Now they take one question.

“Is the checkout form broken?”

investigated

Submit button has no click handler

JS error at checkout.js:142. Button exists but doesn't work.

“Why is the homepage slow?”

investigated

LCP blocked by 2.4MB hero image

4.2s load time. Compress image to save 3 seconds.

“Does the tracking pixel fire?”

investigated

GTM fires on click, but conversion tag returns 404

Tracking ID is wrong. Conversions not recording.

Integrations

Connected tools

Browser Inspector uses these to test pages.

HyperbrowserCloud browser

Chrome DevToolsPerformance

Ready to test?

Stop guessing about bugs

Get visual evidence of what's actually happening on your pages.

Get started

Your data never trains AI

Every source cited

Browser Inspector

See what happens

How does the page perform?

Does everything work?

What does the error say?

What does the user see?

Questions about pages

What Browser Inspector can do

Screenshot capture

Core Web Vitals

Console capture

Tracking check

Connected tools

Related specialists

Product

SEO

Traffic

Stop guessing about bugs