BrowserSiftPlain-language edition

BrowserSift demo fixture page (local only)

Target http://fixture.browsersift.internal/scan · Created 2026-10-13T07:55:54.844Z · Plain-language edition

4 finding(s), 1 high priority. Execution completed is not a pass.

Actual issues found

including 1 high priority

Engine coverage

3/3

engines executed of those planned — executed, not passed

Main content visible (LCP)

36–120 ms

Time until the main content becomes visible (LCP)

Full page load

56–146 ms

Time until the full page finishes loading (load event)

Measured speedMain content became visible in 36 ms on the fastest completed engine and 120 ms on the slowest (84 ms spread, single local sample). This is one local, unthrottled sample — not a production-user speed rating.

Priority findings

Overview

#	Finding	Severity	Engines	First proposed action (UNVERIFIED)
1	JavaScript error thrown on page interaction	high	Chromium, Firefox, WebKit	Define or import the missing function before it is invoked. (unverified)
2	Horizontal page overflow at 1440px viewport	medium	Chromium, Firefox, WebKit	Use max-width or a responsive width instead of a fixed 1800px. (unverified)
3	An interactive feature needs review	medium	Chromium, Firefox, WebKit	Fix or define the referenced method on the component. (unverified)
4	A page module needs its loading settings checked	medium	Chromium, Firefox, WebKit	Confirm the .wasm artifact is served with the application/wasm MIME type. (unverified)

Measured overview

Load milestones by engine (absolute nav-origin times)Captured report data · see scope below

Full caption & source

Each marker is an actual measured milestone at its absolute time from navigation start — this is NOT a stacked duration chart. Coincident milestones share a position; hover for the exact label. Source: this report's current recorded run (initial observation window); no remote images or script output. Offline copy: hover and selection are unavailable; use the numeric table for exact values.

Numeric data — Load milestones by engine (absolute nav-origin times)

Engine	Milestone	ms
Chromium	TTFB	2.4
Chromium	FCP	36
Chromium	LCP	36
Chromium	DCL	132.7
Chromium	load	132.8
Firefox	TTFB	24
Firefox	FCP	120
Firefox	LCP	120
Firefox	DCL	146
Firefox	load	146
WebKit	TTFB	4
WebKit	FCP	57
WebKit	LCP	57
WebKit	DCL	55
WebKit	load	56

Diagnostics by category and engineCaptured report data · see scope below

Full caption & source

Actual observed diagnostic counts per completed engine, stacked by category. Translucent segments are policy-aborted entries caused by our own same-origin policy — they are shown separately, not as site errors. Source: this report's current recorded run (initial observation window); no remote images or script output. Offline copy: hover and selection are unavailable; use the numeric table for exact values.

Numeric data — Diagnostics by category and engine

category	Chromium site	Firefox site	WebKit site
javascript	1	1	1
vue	2	2	2
wasm	1	1	1

Findings × engine coverageCaptured report data · see scope below

Full caption & source

Teal = issue observed on that engine; grey = no observation on that engine (not a pass); blank = not collected. Severity is shown in the findings list. Source: this report's current recorded run (initial observation window); no remote images or script output. Offline copy: hover and selection are unavailable; use the numeric table for exact values.

Numeric data — Findings × engine coverage

Finding	Chromium	Firefox	WebKit
JavaScript error thrown on page interaction	observed	observed	observed
Horizontal page overflow at 1440px viewport	observed	observed	observed
Vue runtime warning/error	observed	observed	observed
Wasm load/compile failure	observed	observed	observed

Resource bytes by initiator type — ChromiumCaptured report data · see scope below

Full caption & source

Known transfer sizes only. 0 resource(s) had unknown size and are excluded — this ring is not full page weight. Source: this report's current recorded run (initial observation window); no remote images or script output. Offline copy: hover and selection are unavailable; use the numeric table for exact values.

Numeric data — Resource bytes by initiator type — Chromium

initiatorType	bytes	unknownSizeCount
script	599158	0
link	514	0

Resource bytes by initiator type — FirefoxCaptured report data · see scope below

Full caption & source

Numeric data — Resource bytes by initiator type — Firefox

initiatorType	bytes	unknownSizeCount
script	599158	0
link	514	0
other	0	0

Resource bytes by initiator type — WebKitCaptured report data · see scope below

Full caption & source

Numeric data — Resource bytes by initiator type — WebKit

initiatorType	bytes	unknownSizeCount
script	599158	0
link	514	0

Engines checked

Chromium

156.0.8078.4

completed

TTFB2 ms
First contentful paint36 ms
Largest contentful paint36 ms
Full page load133 ms
DOM content loaded133 ms
Cumulative layout shift0.001

TTFB, paint and load values are independent observations from one initial-load sample, not additive phases. No performance score is computed.

Firefox

157.0

completed

TTFB24 ms
First contentful paint120 ms
Largest contentful paint120 ms
Full page load146 ms
DOM content loaded146 ms
Cumulative layout shiftNot collected

TTFB, paint and load values are independent observations from one initial-load sample, not additive phases. No performance score is computed.

WebKit

27.2

completed

TTFB4 ms
First contentful paint57 ms
Largest contentful paint57 ms
Full page load56 ms
DOM content loaded55 ms
Cumulative layout shiftNot collected

TTFB, paint and load values are independent observations from one initial-load sample, not additive phases. No performance score is computed.

Report details & scope

Report ID:: recorded-demo-20261013
Target:: BrowserSift demo fixture page (local only)
URL:: http://fixture.browsersift.internal/scan
Created:: 2026-10-13T07:55:54.844Z
Elapsed:: 17 s
Mode:: Live run
Scope:: Recorded demo scan of the fixed local fixture page including the signed-in (protected) area with the published demo account. External public URL scanning is not available.
Offline note:: Offline HTML export: screenshots and other private evidence files are not embedded; only their metadata and hashes are listed. Open the live report while signed in to view them.

Assessment

4 finding(s), 1 high priority. Execution completed is not a pass.

What was checked

Chromium, Firefox, WebKit completed against http://fixture.browsersift.internal/scan (fixed local demo fixture only — not an arbitrary public site).

Based on automated checks only; no AI interpretation is included for this report.

Issues in priority order

highFunctionality and interaction

1. JavaScript error thrown on page interaction

Affects: Chromium, Firefox, WebKit

Impact

Observed on: chromium, firefox, webkit. This was raised by rule-based checks; the visitor-facing impact has not been verified.

Suggested next action

Define or import the missing function before it is invoked.

Suggested fix and how to verify

Define or import the missing function before it is invoked.
Wrap third-party integrations in try/catch and log via a reporting hook.

Validation:

Reload the page and click the same button.
Confirm the console shows no uncaught errors.

Rule-based observation; no source-level cause asserted

mediumLayout and display

2. Horizontal page overflow at 1440px viewport

Affects: Chromium, Firefox, WebKit

Impact

Observed on: chromium, firefox, webkit. This was raised by rule-based checks; the visitor-facing impact has not been verified.

Suggested next action

Use max-width or a responsive width instead of a fixed 1800px.

Suggested fix and how to verify

Use max-width or a responsive width instead of a fixed 1800px.
Add overflow-x handling or container queries where fixed widths are required.

Validation:

Reload at 1440x900 and confirm document.scrollWidth <= window.innerWidth.

Rule-based diagnosis

mediumFunctionality and interaction

3. An interactive feature needs review

Affects: Chromium, Firefox, WebKit

Impact

Interactive parts of the page can stop working for visitors when this error happens.

Suggested next action

Fix or define the referenced method on the component.

Suggested fix and how to verify

Fix or define the referenced method on the component.
Add an app-level errorHandler to surface uncaught handler errors.

Validation:

Reload and repeat the interaction; confirm no [Vue Warn] or handler error appears.

Rule-based observation

mediumResource loading

4. A page module needs its loading settings checked

Affects: Chromium, Firefox, WebKit

Impact

Features built on WebAssembly may silently fail to load for visitors.

Suggested next action

Confirm the .wasm artifact is served with the application/wasm MIME type.

Suggested fix and how to verify

Confirm the .wasm artifact is served with the application/wasm MIME type.
Verify the module's import/export table matches the host object (link errors).

Validation:

Re-run with the specific cause addressed and confirm no wasm error appears.

Rule-based diagnosis

All findings summary

high JavaScript error thrown on page interaction — affects chromium, firefox, webkit
medium Horizontal page overflow at 1440px viewport — affects chromium, firefox, webkit
medium An interactive feature needs review — affects chromium, firefox, webkit
medium A page module needs its loading settings checked — affects chromium, firefox, webkit

Limitations

This is a recorded local fixture run, replayed read-only — no new scan happens when the page opens.
Rule-based observation; no AI interpretation is attached to this public dataset.
Demo targets a fixed local fixture; external public URLs are never fetched in v0.1.
Findings shared across engines are not proven engine-specific.
Performance numbers come from a single initial-load sample on a fast local fixture; they are not customer-site or real-user metrics.
Source file/line/column are generated bundle positions; no public source map exists.
Evidence files (screenshots, logs) are omitted from the public dataset — none are requested or faked.

Evidence

No evidence artifacts were collected.

Generated by BrowserSift prototype. Measurements are single-sample local observations, not production-user statistics.