Documentation

Using EPIC.

Everything you need, on one page. Paid-plan features are marked.

Getting started

Install EPIC from the Chrome Web Store or Microsoft Edge Add-ons, pin it to your toolbar, open any website and click the EPIC icon. EPIC opens in the side panel.

  1. The first time, choose your role (Marketing & SEO, Developer & QA, Security, Manager, or Everything). It only changes which shortcuts appear first. Every feature stays available. Change it anytime from ⋯ → Change role.
  2. Click Quick Scan. EPIC reloads the page with capture on and builds the analysis.
  3. Start with Website Intelligence: the overall health score, launch readiness, quick wins and top priorities.

Step-by-step guide with screenshots →

The four main areas sit at the bottom of the panel: Website Intelligence, Observe, Modify and Reporting. Tap one to see its sections just above the bar. The ⋯ menu (top right) has Open in New Tab, Passive checks, Change role, License, help links and Clear All.

  • Observe: Intelligence · Performance · Network · Site Scan · Journeys · History.
  • Intelligence is grouped in three rows: How you're seen (AI, Business, Trust, SEO, Marketing), How you're protected (Security, Privacy, Resilience) and How it's built (Quality, Accessibility, Technology, Infrastructure). The Resilience tab shows its score.
  • Network has two views, switched at the top: Requests & timing and Dependencies & redirects.
  • Modify: Headers & Cookies · Page Changes · HTTP/API Lab. Reporting: Report Center.

Step-by-step guide with screenshots →

Passive checks

Turn on passive checks from the ⋯ menu and EPIC reads each page you visit (with no reload and no network requests) and shows the number of issues on the toolbar badge. It covers titles, descriptions, headings, canonicals, noindex, viewport, language, alt text, social tags, HTTPS and mixed content, passwords over HTTP, invalid JSON-LD and slow responses. Off by default.

History, Change Log and monitoring

Observe and Modify. Every Quick Scan of a saved website is stored in Observe → History, with a screenshot for the Visual Timeline. From the second scan, the Change Log lists every difference: scores that moved 2 or more points, page size and requests, new/removed/resized files, SEO and content, tags and consent, third parties, redirects, resilience, security headers, console errors, speed, and journey changes. Filter by site, category, “got worse / got better”, period or text, and download any view as CSV.

Under Saved Websites & Monitoring, set a site to scan daily, weekly or monthly. Scans run while the browser is open. Add competitors to compare side by side, and set any scan as a baseline.

Under Alerts & Notifications, choose which changes notify you and the score threshold (2, 5, 8, 10 or 15 points). Alerts arrive as browser notifications, grouped per scan, and are listed in History; EPIC doesn't send email.

Step-by-step guide with screenshots →

Storage, downloads and retention

History → Storage & Downloads shows the space used and lets you choose how long to keep history (Observe 30/60/90 days, Modify up to 1 year). Download this week's changes, all changes, every scan with all its measurements (CSV), or everything (JSON). Turn on the weekly export to save two CSV files to Downloads/EPIC every week. Three days before anything ages out, EPIC shows a reminder so you can download it first.

Step-by-step guide with screenshots →

Journeys

Free: 1 journey, run by hand · Observe: 10 · Modify: 50, scheduled. Open the page where the journey starts, go to Observe → Journeys → Record a journey and choose Desktop or Mobile. EPIC fixes the screen size while you record (Mobile reloads the page at phone size) and uses the same size on every run, because responsive sites change layout with width, and EPIC's panel makes the page narrower. Use the site as a visitor would; each click and entry appears in the panel. If you send a form that would submit data, EPIC holds it, so nothing is sent, and saves a “check the form” step. The same goes for any button that sends data, such as a script-driven “Add to cart”: the recording ends there, because a journey never sends data. Stop, name the journey, choose Normal or Critical and how often it runs.

Each run is Passed, Passed with changes (new or required fields, renamed buttons, new pages, address changes, new JavaScript errors, visual differences) or Broken (with the step, what EPIC looked for and a screenshot). If a change is intended, click Accept as the new normal. The visual lens compares any run with the baseline or the run before. Passwords are never stored. A journey behind a login uses the login already in your browser. Tip: if EPIC can't fix the screen size (for example DevTools is open on that tab), pop EPIC out into its own window so the site gets the full width.

Step-by-step guide with screenshots →

Resilience Intelligence

Observe and Modify. Observe → Intelligence → How you're protected → Resilience (also shown as a card at the top of Intelligence) scores how ready a site is for unexpected traffic and common attacks: Protection (CDN, WAF and bot signals, HTTPS/HSTS, HTTP/3, origin exposure, rate-limit signals), Application exposure (sign-in observations, API endpoints, secrets, source maps, CORS, security headers) and Traffic efficiency (transfer, caching, compression, edge-cache hits, third-party share, large files). Only signals the browser can see count; unknown ones are left out. EPIC never sends attack or load traffic, so WAF rules and rate limits are reported as signals, not proof.

Step-by-step guide with screenshots →

Dependencies & Redirects

Observe and Modify. Observe → Network → Dependencies & redirects lists first- and third-party resources, the services behind third-party domains, trackers, render-blocking and failed third-party files, and what changed compared with the previous scan or 30/60/90 days ago, with plain-language insights. How visitors reach this site follows http/https and www/non-www addresses hop by hop. In Site Scan, Redirect health follows every scanned and linked address: 301/308 vs 302/307, chains, loops and the internal links still pointing at redirects; changes since the last Site Scan go to the Change Log. A dash always means the browser didn't reveal a value, never zero.

Step-by-step guide with screenshots →

Site Scan

Observe and Modify. Observe → Site Scan checks 10 to 100 pages, found from the sitemap (via robots.txt) or by following links. Issues are ranked by severity and number of pages affected. Pages are checked from the browser as a logged-out visitor so site-wide issues can be reviewed consistently.

Step-by-step guide with screenshots →

Deploy check

Observe and Modify. In Observe → Intelligence → Quality, save a snapshot before you deploy, run Quick Scan after, and click Compare. You get regressions and improvements across scores, console errors, failed requests, tags, headers, SEO fields and page weight, with a “Copy as PR comment” button.

Reports

Observe and Modify. Reporting → Report Center generates executive, engineering, QA, performance, AI intelligence and stakeholder reports from the latest scan. Print them, save as PDF from the print dialog, or export HTML.

Step-by-step guide with screenshots →

Modify

Modify only. Page Changes has HTML, CSS, JavaScript and Resources studios with an element inspector. Headers & Cookies adds request/response header rules and cookie edits. Device & browser emulation and Compare sit alongside. Changes apply only in your tab. Reload or use Reset to remove them. The HTTP/API Lab builds and sends requests with saved login profiles; saved snippets are encrypted on your device.

Step-by-step guide with screenshots →

Licenses

Activate in ⋯ → License. EPIC re-checks the license about once a day; if the licensing service can't be reached, paid features keep working for 3 days. Use Deactivate Device to move a license (and before you uninstall EPIC, so the slot is freed), and Manage billing to cancel or update payment details.

Exports

Every workspace has Download JSON/CSV. Observe adds HAR, Markdown and OpenAPI-draft exports from captured traffic. Findings can be copied as a GitHub or Jira issue.

Step-by-step guide with screenshots →