content · Sep 29, 2026

pocketjs.dev

1 conversion tactic detected

1 page walked · measured by Roentgen 1.28.1

Walk 45 links seen, 5 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
Captured Homepage / Lander
Step 1 · Homepage / Lander1 / 1

How this was measured

Every figure on this page was read off the live site by Roentgen 1.28.1 on 2026-09-29, a script that reads page structure, computed CSS and matched text. No AI judgment, nothing estimated, and a capture’s numbers stay as read.

Detection coverage, not a verdict. A low count means we did not detect those patterns, not that the funnel is weak.

  1. Links on the entry page45 links
  2. Walkable, same site5 links
  3. Matched a funnel step0 links
  4. Pages captured, entry page included1 page

Progress

4 scans

this funnel’s coverage score across measured re-scans

1 fewer tactic detected 2 → 1 across 4 scans since 2026-07-30. The ruleset changed in this window, so part of this may be our detection improving rather than the page changing.
  1. 2 tactics 2026-07-30
  2. 2 tactics 2026-08-02
  3. 2 tactics 2026-08-03
  4. 1 tactic 2026-09-29

What we found

1 of 7 applicable

pocketjs.dev shows 1 of the 7 tactics that apply to a content funnel, and we did not see the other 6.

Proven on the page · 1

Shows customer logos or a trusted-by claim logo wall (4 distinct marks)

Not seen on any step reached · 6

FAQ / objection handling 1,746 of the 2,586 funnels we checked
Press / "as seen in" 655 of the 2,583 funnels we checked
Us-vs-them comparison 493 of the 2,586 funnels we checked
Proof above the fold 419 of the 2,586 funnels we checked
Usage / adoption proof 299 of the 2,196 funnels we checked
Scarcity / urgency copy 135 of the 2,583 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.

Put these tactics to workBrief your AIX-ray your funnel

The funnel, frame by frame

1 step walked

We captured 1 page, Homepage / Lander, and did not walk past it.

Homepage / Lander
01

Homepage / Lander

2 tactics
Logo wallDemo / docs

Also captured on mobile, 1 step.

In their own words

31 quoted

Their headline: “CREATE ON EVERY SCREEN YOU LOVE CREATE ON EVERY SCREEN YOU LOVE”

Their description: “Create on every screen you love. Build apps and games with familiar JavaScript components, from handhelds and desktops to embedded screens.”

All 31 quoted strings: title, description, headings and buttons
Page title
PocketJS · Create on every screen you love
Meta description
Create on every screen you love. Build apps and games with familiar JavaScript components, from handhelds and desktops to embedded screens.
Headline
CREATE ON EVERY SCREEN YOU LOVE CREATE ON EVERY SCREEN YOU LOVE
Section headings
COMMUNITY VOICES COMMUNITY VOICESOpenStrikeOpenStrikePocket DocPocket DocPocket VoxelPocket VoxelPSPMANPSPMANPocket ShellPocket ShellPocket FigmaPocket FigmaPocket YouTubePocket YouTube+5 more, not shown
Buttons and links
ResourcesSee what people makeStar on GitHubSolidVue VaporOctaneAll casesNintendo 3DSPSPPS Vita+2 more, not shown
Borrow the wordingBrief your AI

Sections

4 identified

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

Nav section of pocketjs.dev
Nav0% down the page
Hero section of pocketjs.dev
Hero0% down the page
Logos section of pocketjs.dev
Logos94% down the page
Footer section of pocketjs.dev
Footer99% down the page

How well it’s built

13 run · 4 flagged

4 of 13 measured checks need work, and each comes with its fix

  • 4 Need work
  • 4 Worth knowing
  • 5 Clear
  • Body text size

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

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

    What this measures
  • Page weight

    At least 23.9 MB across 83 measurable resources. 1 cross-origin resource did not expose a size, so the real total is higher.

    Compress and lazy-load below-the-fold media; drop unused third-party scripts.

    What this measures
  • Oversized images

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

    “openstrike-psp-dust2.png” is 960px wide, displayed at 60px

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

    What this measures
  • Tap-target size (mobile)

    70 of 138 interactive targets are under 44×44px on mobile.

    smallest: “Docs” at 51×32px

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

    What this measures
4 worth knowing, 5 clear

Worth knowing4

  • Line length

    1 paragraph runs past ~95 characters per line.

    Cap measure at ~60-75ch for comfortable reading.

    What this measures
  • Heading levels

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

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

    What this measures
  • Landmark regions

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

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

    What this measures

Clear5

Text contrast (WCAG AA) · Mobile viewport · Language declared · Image alt text · Render-blocking resources

Hand the 4 fixes to your build agentBrief your AI

Brand kit

5 colour roles

We measured 4 colour roles on this funnel.

  • accent#fff6d6
  • bg#fff0f6
  • surface#fff6d6
  • text#a597c4
See the roles applied and the type scale
accent

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

the roles, doing their job
SIZE SCALE
9pxAa
10pxAa
11pxAa
12pxAa
13pxAa
14pxAa
15pxAa
16pxAa
17pxAa
24pxAa
30pxAa
41pxAa
WEIGHTS
Aa400
Aa500
Aa600
Aa700
FAMILIES
VT323 · IBM Plex Sans
rendered in their own type system · webfont not loaded. system fallback if uninstalled
Take their look into your buildDownload design tokens

We also ran these layers on the pages we captured and found nothing to show: Elements, Playbook match (2 of 10 layers). That is a measurement of this funnel, not a recommendation, and a layer we never ran is not listed.

Go further

Compare with the corpus

Measured ranges for the parts of a page, from the funnels we have x-rayed.

Take this report with you

The same measurements, in formats a build agent can read.

Similar crawls