content · Oct 2, 2026

volume-shader.net

Fewer than 1% of the 640 entry-page captures we have measured showed fewer conversion tactics than we found here.

0 conversion tactics detected

1 page walked · measured by Roentgen 1.28.1

Walk 31 links seen, 24 walkable, and 0 matched a funnel step. If this funnel continues past the entry page, we did not reach it — everything below is measured from the entry page alone.

Put this x-ray to work Brief your AI X-ray your funnel
How this was measured

Measured by Roentgen 1.28.1 on 2026-10-02. A capture is read once and its measurements freeze there, so the stamp says which ruleset read this one.

This is detection coverage, not a verdict — it counts the conversion tactics we could prove are present, out of the 7 that apply to a content funnel. A low count means we did not detect those patterns, not that the funnel is weak.

The short version, in 3 parts

  1. Not seen

    7 of 7 applicable tactics we checked for and did not see

    FAQ / objection handling
    An accordion / FAQ block answering objections.
    Trusted-by logo wall
    Customer/company logos or a "trusted by / used by" claim.
    Press / "as seen in"
    Media logos or an "as seen in / featured in" claim borrowing publication credib…

    + 4 more

    See what we looked for

  2. Flagged

    5 of 14 build checks flagged, each with a fix

    Body text size
    Smallest sampled text is 12px, below the 13px floor this check uses.
    Form labels
    4 of 5 form fields have no label (+1 rely on placeholder only).
    Horizontal overflow
    The page scrolls ~480px horizontally at 1440px wide. content spills past the viewport.

    + 2 more

    See the fixes

  3. In their words

    The headline: GPU Benchmark Rankings

    Promise
    Comprehensive GPU performance rankings for Volume Shader BM. Compare desktop and mobile GPUs, filter by manuf…
    Prices shown
    $1599 · $1199 · $999

    Read every quote

Captured Devices
Step 1 · Devices1 / 1

What we recorded

Progress

2 scans

this funnel’s coverage score across measured re-scans

measuredextracted directly from the live page. a fact, not an opinion
Unchanged across 2 scans Same 0 conversion tactics detected since 2026-08-09.
  1. 0 tactics 2026-08-09
  2. 0 tactics 2026-10-02

The funnel, frame by frame

1 step walked

see their whole funnel without clicking through it. scored step by step

measuredextracted directly from the live page. a fact, not an opinion
Devices
01

Devices

▲ strongest
0 tactics

$1599 +17 more

no named tactics detected on this step

In their own words

32 quoted

the entry page’s own title, headline, buttons and prices — quoted, never paraphrased

measuredextracted directly from the live page. a fact, not an opinion
Page title
GPU Benchmark Rankings - Volume Shader BM Performance Database
Meta description
Comprehensive GPU performance rankings for Volume Shader BM. Compare desktop and mobile GPUs, filter by manufacturer, price range, and view detailed benchmark scores.
Headline
GPU Benchmark Rankings
Section headings
Test Your GPU PerformanceNVIDIA GeForce RTX 4090NVIDIA GeForce RTX 4080AMD Radeon RX 7900 XTXNVIDIA GeForce RTX 4070 TiAMD Radeon RX 7900 XTNVIDIA GeForce RTX 4090 MobileNVIDIA GeForce RTX 4070+1 more, not shown
Buttons and links
BenchmarksStart Benchmark Test
Prices on the page
$1599$1199$999$799$899$599$499$699+10 more, not shown

Sections

2 identified

structural bands identified on this funnel, cropped from its own capture

measuredextracted directly from the live page. a fact, not an opinion
Nav section of volume-shader.net
Nav0% down the page
Footer section of volume-shader.net
Footer80% down the page

What we didn’t find

7 of 7 applicable

applicable tactics we checked for and did not see on any step we reached

measuredextracted directly from the live page. a fact, not an opinion

What we didn’t see7 of 7 applicable

FAQ / objection handling 1,615 of the 2,420 funnels we checked
Trusted-by logo wall 1,484 of the 2,043 funnels we checked
Press / "as seen in" 642 of the 2,417 funnels we checked
Us-vs-them comparison 441 of the 2,420 funnels we checked
Proof above the fold 381 of the 2,420 funnels we checked
Usage / adoption proof 289 of the 2,043 funnels we checked
Scarcity / urgency copy 125 of the 2,417 funnels we checked

Absence is a measurement, not a recommendation: we do not know why a tactic is missing, whether it belongs here, or whether adding it would change anything. Where a walk stopped early, a tactic living deeper would also read as not detected.

How well it’s built

14 run · 5 flagged

contrast, mobile, typography, accessibility, weight — each with what would fix it

measuredextracted directly from the live page. a fact, not an opinion

5 of 13 measured checks need work1 could not be measured — not counted either way

Body text size

type:body-text-size

Smallest sampled text is 12px, below the 13px floor this check uses.

FixKeep body copy ≥15-16px; reserve sub-13px for fine print only.

Form labels

a11y:form-labels

4 of 5 form fields have no label (+1 rely on placeholder only).

FixGive every input a <label> or aria-label; placeholders are not labels.

Horizontal overflow

layout:horizontal-overflow

The page scrolls ~480px horizontally at 1440px wide. content spills past the viewport.

FixFind the overflowing element (fixed widths, unwrapped rows) and constrain it to 100%.

Landmark regions

structure:landmark-regions

No <main> or <header> landmark. screen-reader users cannot jump between regions.

FixWrap the page in <header>, <main> and <footer> (or matching ARIA roles).

Tap-target size (mobile)

mobile:tap-target-size-mobile

59 of 68 interactive targets are under 44×44px on mobile.

smallest: “GitHub” at 40×40px

FixGive tappable controls a ≥44×44px hit area. the touch minimum.

Worth knowing4

Heading levels

1 heading skips a level (e.g. <h2> followed by <h4>). Screen-reader users navigate by this outline.

FixStep heading levels one at a time; use CSS for size, not a deeper level.

a11y:heading-levels
Render-blocking resources

5 stylesheets/scripts in <head> block first paint.

FixDefer non-critical JS (defer/async) and inline only critical CSS.

weight:render-blocking-resources
Oversized images

4 images are shipped at more than 2x the width shown.

FixServe responsive sizes (srcset/sizes) matching the rendered width.

weight:oversized-images

Not measurable1

Page weight

At least 0.8 MB across 70 measurable resources, but 31 cross-origin resources did not expose a size. The true weight cannot be determined from the page.

weight:page-weight

Clear4

Text contrast (WCAG AA) · Mobile viewport · Language declared · Image alt text

Brand kit

5 colour roles

palette by on-page usage · type rendered live

measuredextracted directly from the live page. a fact, not an opinion
full palette ordered by on-page usage %
primary#3b82f6
accent#3b82f6
bg#f8f9fa
surface#ffffff
text#d1d5db
See the roles applied
accent

Body copy in their text role, on a surface card.

the roles, doing their job
The quick brown fox72px
Jumps over the lazy dog36px
A subheading in their voice24px

Body copy set at their measured paragraph size. This is how their product reads to a first-time visitor. same family, same scale, same weight.

  • List item one, at body scale
  • List item two
  • List item three
Type scale, weights & families
SIZE SCALE
12pxAa
14pxAa
16pxAa
18pxAa
20pxAa
24pxAa
36pxAa
72pxAa
WEIGHTS
Aa400
Aa500
Aa600
Aa700
FAMILIES
Geist
rendered in their own type system · webfont not loaded. system fallback if uninstalled

Measured, found none

3 of 10 layers

layers we ran on this funnel that came back empty

measuredextracted directly from the live page. a fact, not an opinion

Elements — the atomic pieces — price anchors, ratings, guarantees — with their verbatim on-page text

What we found — conversion tactics we could prove are present, with the on-page text that evidences each

Playbook match — which funnel play this page runs — measured, evidence-quoted

We ran these passes on the pages we captured and found nothing to show. That is a measurement of this funnel, not a recommendation — and it is a different statement from a layer we never ran, which does not appear here at all.

Similar crawls