content · Aug 3, 2026

codenearby.space

30/100 Sparse

Scores higher than 54% of 577 entry-page captures we have measured.

1 conversion tactic detected
1 page captured
11 UX checks
2 flagged

Walk 11 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.

How this was measured

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

Coverage is detection coverage, not a verdict — it counts the conversion tactics we could prove are present, out of the 5 that apply to a content funnel. Per device: desktop 30 · mobile 30.

Scan

Captured Homepage / Lander — Step 1 · Homepage / Lander1 / 1

What we recorded

Progress

3 scans

this funnel’s coverage score across measured re-scans

measured

Unchanged across 3 scans Same 1 conversion tactic detected since 2026-07-30.

1 tactic 2026-07-30
→
1 tactic 2026-08-02
→
1 tactic 2026-08-03

The funnel, frame by frame

1 step walked

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

measured

Homepage / Lander

2 tactics

FAQNo card

In their own words

31 quoted

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

measured

Page title: CodeNearby
Meta description: Find developers near you, share ideas, and build something awesome together.
Headline: Code Nearby
Section headings: Connect across every language & frameworkEverything you need to connectThree steps. Zero friction.Why developers choose CodeNearbyBuilt for how developers actually workDevelopers love it. Here's why.This is the start of something newAdditions+8 more, not shown
Buttons and links: Login with GitHub01 Find Developers Near You02 Build Projects Together03 Your Ideas, Your Space04 Code Together, Chat Together05 Meet, Code, Connect06 Discover with AISign in with GitHubWhat is Codenearby?How can I find developers near me?+2 more, not shown

Elements

1 harvested

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

measured

No credit card element — **No credit card**“Free, no credit card”

What we found

1 tactic

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

measured

Friction reduction1 of 1

Answers buyer objections Frequently asked questions FAQS

What we didn’t find

4 of 5 applicable

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

measured

What we didn’t see4 of 5 applicable

Press / "as seen in" 508 of the 1,960 funnels we checked

Us-vs-them comparison 332 of the 1,968 funnels we checked

Proof above the fold 314 of the 1,968 funnels we checked

Scarcity / urgency copy 101 of the 1,960 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

12 run · 3 flagged

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

measured

3 of 12 measured checks need work

Text contrast (WCAG AA)

contrast:text-contrast-wcag-aa

75% of measurable text passes WCAG AA. 4+ runs fail.

worst: “React” at 1.62:1 (12px, #61dafb on #ffffff). needs 4.5:1

FixRaise text/background contrast to ≥4.5:1 (≥3:1 for large text), especially on CTAs and body copy.

Body text size

type:body-text-size

Smallest body text is 9px (base ~16px). below the ~16px readable floor.

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

Tap-target size (mobile)

mobile:tap-target-size-mobile

17 of 32 interactive targets are under 44×44px on mobile.

smallest: “Open menu” at 36×36px

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

Worth knowing5

Line length

7 paragraphs run past ~95 characters per line.

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

type:line-length

Page weight

At least 3.5 MB across 41 measurable resources. 3 cross-origin resources did not expose a size, so the real total is higher.

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

weight:page-weight

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

Keyboard reachability

3 elements look clickable but cannot be reached by keyboard.

FixUse <button>/<a>, or add role + tabindex="0" and a key handler.

structure:keyboard-reachability

Clear4

Mobile viewport · Language declared · Image alt text · Render-blocking resources

Brand kit

5 colour roles

palette by on-page usage · type rendered live

measured

full palette ordered by on-page usage %

primary#f97015

accent#f97015

bg#ffffff

surface#f4f4f5

text#09090b

See the roles applied

accent

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

the roles, doing their job

The quick brown fox96px

Jumps over the lazy dog60px

A subheading in their voice48px

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

10pxAa

11pxAa

12pxAa

14pxAa

16pxAa

18pxAa

20pxAa

24pxAa

30pxAa

48pxAa

60pxAa

96pxAa

WEIGHTS

Aa100

Aa300

Aa400

Aa500

Aa600

Aa700

FAMILIES

__Instrument_Serif_1f5468 · __Space_Grotesk_dd5b2f

rendered in their own type system · webfont not loaded. system fallback if uninstalled

Measured, found none

1 of 9 layers

layers we ran on this funnel that came back empty

measured

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

We ran this pass 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.

X-ray a funnel