content · Aug 9, 2026

invitem.io

33/100 Sparse

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

2 conversion tactics detected
1 page captured
13 UX checks
4 flagged

Walk 85 links seen, 66 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.20.1 on 2026-08-09. 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 65 · mobile 0.

Scan

Captured Rsvp Invites — Step 1 · Rsvp Invites1 / 1

What we recorded

Progress

3 scans

this funnel’s coverage score across measured re-scans

measured

1 more tactic detected 2 → 3 across 3 scans since 2026-08-09. The ruleset changed in this window, so part of this may be our detection improving rather than the page changing.

2 tactics 2026-08-09
→
3 tactics 2026-08-12
→
3 tactics 2026-08-15

The funnel, frame by frame

1 step walked

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

measured

Rsvp Invites

3 tactics

subscription

ComparisonFAQLogo wall

In their own words

10 quoted

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

measured

Page title: About Our Sports Team Management App for Teams & Clubs | Invitem
Headline: RSVP Invites
Section headings: The Most Advanced RSVP System for Sports Clubs, Teams and OrganisationsKey BenefitsOne RSVP System for Every EventCreate Recurring Events in SecondsSet Maximum Attendance LimitsAutomatic Waiting ListsPriority ListsAccept Payment Before Confirming Attendance

Sections

5 identified

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

measured

Nav section of invitem.io — **Nav**0% down the page

Features section of invitem.io — **Features**3% down the page

Logos section of invitem.io — **Logos**15% down the page

FAQ section of invitem.io — **FAQ**91% down the page

Footer section of invitem.io — **Footer**96% down the page

What we found

2 tactics

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

measured

Friction reduction1 of 1

Answers buyer objections Can I create recurring events? Yes. Invitem supports both single and recurring events, mak

Value reinforcement1 of 1

Compares itself against alternatives comparison grid: 21 rows

What we didn’t find

3 of 5 applicable

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

measured

What we didn’t see3 of 5 applicable

Press / "as seen in" 508 of the 1,960 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

14 run · 5 flagged

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

measured

5 of 14 measured checks need work

Body text size

type:body-text-size

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

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

Render-blocking resources

weight:render-blocking-resources

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

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

Oversized images

weight:oversized-images

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

“invitem-logo-blue-side-2-scaled.jpg” is 2560px wide, displayed at 155px

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

Tap-target size (mobile)

mobile:tap-target-size-mobile

75 of 99 interactive targets are under 44×44px on mobile.

smallest: “(unnamed)” at 67×21px

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

Worth knowing5

Line length

66 paragraphs run past ~95 characters per line.

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

type:line-length

Page weight

At least 4.1 MB across 101 measurable resources. 10 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

Landmark regions

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

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

structure:landmark-regions

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

measured

full palette ordered by on-page usage %

primary#04223d

accent#04223d

bg#ffffff

surface#ffffff

text#4b535d

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 dog48px

A subheading in their voice46px

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

15pxAa

16pxAa

18pxAa

24pxAa

40pxAa

46pxAa

48pxAa

72pxAa

WEIGHTS

Aa400

Aa500

Aa600

Aa700

FAMILIES

Urbanist · Mulish

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

Measured, found none

2 of 10 layers

layers we ran on this funnel that came back empty

measured

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

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.

X-ray a funnel