Check guide · In the browser

Performance memory pings

Memory numbers that have to obey physics.

What this check is

Chromium exposes a running estimate of the page's JavaScript heap. While this page measures its latency to the server, it also samples that heap, and this check examines the samples for impossibilities: usage above the heap limit, totals that shrink impossibly, numbers a real memory manager would not report.

What Tells reads

performance.memory samples (used, total, limit) taken alongside the latency pings

How to read your result

Warning: At least one sample contains impossible heap values.
Pass: Every sample is physically plausible.
Not available: This browser does not expose performance.memory. Only Chromium browsers do, so Firefox and Safari always read Not available here. That is normal.

Why it matters

Fabricated environments have to invent their telemetry, and invented numbers tend to break the rules the real thing obeys without thinking. Memory is a good example because it is boring: nobody hand-tunes it, so a synthetic value stands out precisely because a real one never does.

Where this matters most

Across the platforms Blowhorn works with, rated in the platform guide (H = matters a lot, M = contributes, L = no public evidence; tags mark vendor-stated, reported, or inferred evidence):

LinkedIn (M): device memory and hardware values are among the 48 collected characteristics [Reported]

Everywhere else in the set this one rates Low.

In your report

Find it in the checks table on the tool page, with the detail in the Performance memory section. The same findings appear in the report JSON under verdict.reasons, and the agent guide explains how to read them programmatically.