Nebula Frameworks
Discover Core Landing Page Concepts to Improve Conversions
These are the concepts behind the 9-signal audit. Each term has a precise definition, a measurable standard, and a specific role in Nebula’s diagnostic output. Understanding them makes it easier to read an audit report, interpret a grade, and decide which finding to act on first.
Signal
A single observable, measurable dimension of a landing page's conversion fitness. Nebula checks 9 signals per audit. Each has a defined pass standard and returns raw evidence.
Why it matters for conversion
Breaking the audit into discrete signals makes findings falsifiable and actionable. A composite score without signal-level detail cannot tell you which element to fix - and fixing the wrong element wastes the budget.
How Nebula measures it
The engine evaluates each signal independently against the page's actual HTML response. Signals include: headline (H1 count, ICP clarity), CTA (label, above-fold visibility), social proof (source-order position, specificity), load speed (payload bytes, LCP proxy), and four others. Each returns pass or fail with the raw value that determined the result.
Evidence Atom
The raw value from the page that justifies a pass or fail finding - H1 text, meta description character count, payload bytes, CTA label.
Why it matters for conversion
Most audit tools return recommendations without showing their work. An evidence atom makes every finding independently verifiable: you can open the page source and confirm whether the H1 Nebula found is actually the H1 on your page. There is no proprietary scoring black box.
How Nebula measures it
Every signal finding stores the evidence atom alongside the pass/fail verdict. Examples: headline signal stores the exact H1 text. Load speed signal stores the payload size in bytes. Meta description signal stores the character count and the full description text. The audit report surfaces these directly.
Conversion Leak
An observable page condition that fails a documented audit standard and may create friction in the conversion path. A page can have multiple failed conditions; the audit ranks them by priority.
Why it matters for conversion
The word "leak" is deliberate: it frames the problem as a fixable structural defect rather than a weak offer or wrong audience. A page leaking 60% of its mobile visitors through a buried CTA is not a traffic problem. It is a structural problem with a bounded fix.
How Nebula measures it
Nebula identifies failed conditions at the signal level. The audit ranks failed signals by priority - a heuristic incorporating journey position, severity, and reproducibility. Message match and CTA failures are ranked higher for paid traffic; load speed and SEO signals are ranked lower. The One-Leak Repair Sprint targets the highest-priority finding.
Message Match
The degree of continuity between the ad that brought the visitor and the headline they see when they arrive. A score of 0 means the ad and page are unrelated.
Why it matters for conversion
A visitor who clicked an ad for "project management for engineering teams" and lands on a headline that reads "The all-in-one workspace" faces an immediate disorientation: did they click the right link? The cognitive cost of resolving that question is a conversion-rate penalty. The ad already paid for the click - message mismatch discards that spend in the first two seconds.
How Nebula measures it
Nebula checks the H1 text against the page's own title tag and meta description for internal consistency. When an ad URL is provided, it compares ad copy against the H1 directly. The signal returns the H1 text as the evidence atom so the mismatch is visible, not inferred.
Above-Fold State
What a visitor sees before scrolling. For paid traffic, this is the only content that matters for the decision to stay or leave.
Why it matters for conversion
Cold paid traffic makes the stay-or-leave decision within the first viewport. If the primary CTA, an ICP-confirming headline, and at least one proof element are not visible before the first scroll, the page is asking visitors to commit effort before it has earned their attention. Most do not.
How Nebula measures it
Nebula checks for CTA presence in the source-order HTML above the fold proxy. It checks whether the H1 is in the static HTML (not rendered by JavaScript). It checks for at least one trust signal in the above-fold region. Each of these is a binary pass/fail backed by the raw HTML evidence.
Structural Friction
Page-level obstacles that cost conversions regardless of ad quality or offer strength. Structural friction is fixable; it does not require a new product or a different audience.
Why it matters for conversion
Founders and operators running paid traffic often assume the problem is the ad creative, the audience targeting, or the offer price. Structural friction - a five-field form, a CTA below fold, a page that loads in six seconds on mobile - is an observable, fixable variable that can be checked without making any of those assumptions. Addressing structural friction does not guarantee conversion lift, but it removes conditions that are measurably outside documented standards.
How Nebula measures it
Structural friction signals in Nebula's audit include: form field count (more than two fields above fold is a friction flag), CTA placement, mobile tap target size, page weight, and font size. These are observable in the HTML and CSS - no session recording or A/B test data required.
One-Leak Repair Sprint
Nebula's $97 paid product. Takes the highest-priority finding from the audit and delivers targeted implementation instructions. One leak, one fix, one re-audit window.
Why it matters for conversion
A full-page redesign is the wrong response to a single conversion leak. If the audit identifies that the H1 has zero ICP clarity, the correct intervention is a headline rewrite - not a new design system. The Repair Sprint scopes the change to the single highest-priority finding, delivers implementation-ready instructions, and includes a re-audit to confirm the finding is resolved.
How Nebula measures it
The Sprint is triggered by the audit output. The highest-ranked failed signal determines the sprint scope. Deliverables are specific to the signal: for a headline failure, the sprint returns three alternative H1 candidates with rationale. For a load speed failure, it returns the specific asset causing the LCP regression and the implementation path to fix it.
Grade
Letter grade (A–F) derived from the composite signal score. A = 90+, B = 75–89, C = 60–74, D = 45–59, F = below 45.
Why it matters for conversion
A numeric score without a reference frame is harder to act on. The grade maps the score to a decision: a Grade A page has no material leaks and is unlikely to benefit from structural changes. A Grade B page passes most signals but has at least one material leak worth fixing. A Grade D or F page has multiple structural failures that are collectively suppressing conversions.
How Nebula measures it
Each of the 9 signals contributes to the composite score with equal weighting unless override logic applies (a zero H1 count forces the score below 50 regardless of other signals). The grade is computed from the final composite. The audit report shows both the numeric score and the grade letter, with the failed signals that drove the result listed below.
See these concepts applied to your page
Paste your URL. Nebula runs all 9 signals and returns each finding with the raw evidence atom - H1 text, CTA label, payload bytes, trust signal count. Free, no signup, under 2 minutes.
Run Free Audit →