content · Aug 9, 2026

screensize.net

30/100 Sparse

Scores above 18% of 1,252 multi-step funnels we have measured. Among the 63 content funnels in that group, above 42%.

1/5 tactics
3 steps
11 checks
2 flagged

How this was measured

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.

Measured by Roentgen 1.20.1, one of our versioned rulesets. A capture is read once and its measurements freeze there, so the stamp says which ruleset read this one.

Walk 85 links seen, 82 walkable, 2 matched, and we walked 3 pages.

Captured Responsive Breakpoints — Step 1 · Responsive Breakpoints1 / 3

What we recorded

The funnel, frame by frame

3 steps walked

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

measured

Responsive Breakpoints

1 tactic

FAQ

Responsive Breakpoints

▼ thinnest

1 tactic

FAQ

Responsive Breakpoints

▲ strongest

2 tactics

FAQTrust badges

In their own words

23 quoted

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

measured

Page title: Responsive Breakpoint Checker — Tailwind, Bootstrap & CSS Media Queries
Meta description: Check the current responsive breakpoint live, compare Tailwind and Bootstrap defaults, and copy media queries for common viewport widths.
Headline: Responsive Breakpoint Checker
Section headings: Critical widths to testTailwind CSS breakpointsBootstrap breakpointsDebug responsive breakpointsFrequently asked questionsRelated toolsScreenBreakpoints
Buttons and links: ScreenBreakpointsCalculatorsDevicesTailwindBootstrapCopy reportTailwind xl 1280px-1535px 96px to 2xl (1536px)Bootstrap xxl 1400px+ Largest default breakpointQuery+2 more, not shown

Sections

4 identified

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

measured

Nav section of screensize.net — **Nav**3% down the page

Hero section of screensize.net — **Hero**2% down the page

FAQ section of screensize.net — **FAQ**63% down the page

Footer section of screensize.net — **Footer**83% down the page

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 › Which width do breakpoints use?

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" 448 of 1769 measured funnels run this

Us-vs-them comparison 304 of 1777 measured funnels run this

Proof above the fold 292 of 1777 measured funnels run this

Scarcity / urgency copy 94 of 1769 measured funnels run this

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

11 run · 2 flagged

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

measured

Readability & contrastclear

Text contrast (WCAG AA) not measurablecontrast:text-contrast-wcag-aa

All 3 sampled text runs sit over images or gradients. effective contrast is not computable.

Mobile & tap targetsclear

Mobile viewport passesmobile:mobile-viewport

Responsive viewport meta is present.

Typography1 flagged

Body text size needs worktype:body-text-size

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

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

Line length notetype:line-length

14 paragraphs run past ~95 characters per line.

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

Accessibility hygieneclear

Weight & delivery1 flagged

Page weight not measurableweight:page-weight

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

Render-blocking resources passesweight:render-blocking-resources

1 stylesheet/script in <head> block first paint.

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

Oversized images needs workweight:oversized-images

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

“featured-badge-small.webp” is 655px wide, displayed at 175px

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