# Page Analyzer: every element, with the locator to use

Dokimore documentation · Recording and self-healing · Updated 2026-11-16 · 6 min read

Written for: SDETs and automation engineers, Developers who own their tests, QA leads and test managers · Where it applies: every market

> Page Analyzer is for the person about to write a test against a page. Give it a URL and it loads the page once and lists every interactive element with an accessible name and a ranked set of locators to copy, including elements inside shadow roots and iframes; the API endpoints and WebSocket connections the page opened; its Core Web Vitals; the data on it (headings, tables, links, images without alt text, landmarks, hidden content); whether it loads more on scroll; and the frameworks and libraries it is built with. From the same analysis it writes a page object and a test file for Playwright, Selenium, Cypress, Puppeteer or WebdriverIO.

## Running an analysis

Enter a URL that starts with http or https (a local file path is refused with a message that says so) and choose what to include: shadow DOM, iframes, performance, API discovery, data extraction, the stability analysis, dynamic content, event listeners and the tech stack. A tab whose option was off says so and asks you to turn it on and analyse again, instead of showing an empty table as a result. Page Analyzer is open to every signed-in account.

## Elements and locators

The overview counts elements, interactive elements, forms, buttons, links and inputs. The elements tab lists each interactive element with its accessible name, why it counts as interactive, its position and size, and its locators ranked, with a locator format you choose and a copy button on each. Elements inside shadow roots and inside iframes are listed with the frame or root they belong to. The stability tab gives each element a score (high, medium or low) with the risk factors behind it and a recommendation, and an average for the page.

## Performance, APIs and data

- Core Web Vitals (LCP, INP, CLS), the secondary metrics (FCP, TTFB, TTI), network timing (DNS, TCP, TLS, redirects), total transfer and cache hit rate, resource counts, and a weighted score (LCP 25%, INP 25%, CLS 25%, FCP 15%, TTFB 10%).
- The API endpoints and WebSocket connections the page opened while it loaded, with method and status.
- Structured data, headings, images and the ones missing alt text, links, ARIA landmarks, the navigation, hidden content by technique, reading time and the content-to-code ratio, tables, the page metadata and its Open Graph tags.
- Dynamic content: the single-page framework detected, how many elements appeared after a scroll, whether the page loads on scroll, and lazy-loaded images; the elements that carry JavaScript event listeners.
- Tech stack: CSS frameworks, JavaScript libraries, build tools, analytics, icon libraries, state management, CDN and hosting, server headers, the security headers present, and meta generators.

## Generate test code and export the report

Choose Page Object Model or a flat script, name the page, and pick the framework: Playwright, Selenium, Cypress, Puppeteer or WebdriverIO. The result is a page object and a test file, each to copy or download. The whole report exports as text or JSON. The generated code runs in your own framework; it is a starting point written from the page as analysed, not a recording.

## Page Analyzer or Web Analyst?

Web Analyst judges a page: how fast it loads, how it reads for search, how it compares with competitors. Page Analyzer serves the person writing a test against it. Run both on the same URL and they answer different questions; the [website analysis guide](https://dokimore.com/documentation/website-analysis) covers the first.

## Questions people ask about this

### Is the stability score a guarantee?

No. It is a ranking of how likely a locator is to survive a change, from the markup the page had when it was analysed. A run is the proof.

### Which locator should I use?

Prefer a test id or an accessible name over a generated path. The list ranks them in that spirit, and shows the risk factors of the weaker ones.

### Does it record anything?

No. It reads the page as loaded. To capture a flow with its network calls and screenshots, use the recorder.

This guide is about the test recorder, which Page Analyzer complements: https://dokimore.com/product/test-recorder

Source: https://dokimore.com/documentation/page-analyzer
