Public audit / not a customer
Raycast Landing Page Teardown: What the Evidence Shows
The headline communicates broad utility, while the product category and first action become clearer only after visitors inspect the surrounding copy and page structure. raycast.com This public snapshot was captured on September 17, 2026. Raycast is not a Nebula customer.
Score
6.8/10
Grade
B
Findings
3
Audited
September 17, 2026
Same engine, public URL
Analysis snapshot
What this page appears designed to accomplish
Position Raycast as a fast command layer for computer work and invite visitors to download or start using the desktop product.
What a first-time visitor can understand
The headline communicates broad utility, while the product category and first action become clearer only after visitors inspect the surrounding copy and page structure.
What is working
- The headline is short and memorable.
- The page uses a clear product demonstration to make the command model tangible.
- The audit found the CTA signal and mobile signal present in the captured page.
Material findings
headline
Observation: The H1 is “Your shortcut to everything.” and does not name the product category or the primary job.
Evidence: Audit 9a492caf-548f-42a2-bc57-4a42ed63c066: page_h1 was “Your shortcut to everything.”; headline finding reported no verb or value-proposition keyword.
Why it matters: A visitor unfamiliar with Raycast must infer whether this is a launcher, automation layer, AI tool, or productivity app before deciding whether the page is relevant.
Bounded remediation: Keep the concise brand line if desired, but pair it immediately with a plain category and audience statement that can stand alone in the first viewport.
above_fold
Observation: The audit did not find the CTA within its first 2,000-character source proxy.
Evidence: Audit 9a492caf-548f-42a2-bc57-4a42ed63c066: above_fold finding reported CTA not in first 2,000 chars.
Why it matters: The page may ask a cold visitor to understand an unfamiliar interaction model before showing how to take the next step.
Bounded remediation: Confirm the browser-rendered fold on desktop and mobile, then place one visually primary download or start action beside the category explanation if the gap remains.
load_speed
Observation: The fetched HTML was approximately 385 KiB.
Evidence: Audit 9a492caf-548f-42a2-bc57-4a42ed63c066: load_speed finding reported HTML is 385 KiB.
Why it matters: The document carries more parsing and transfer work than a focused product landing page needs before the core explanation is available.
Bounded remediation: Profile the rendered critical path and defer below-fold content without removing the product demonstration that provides the page’s strongest explanation.
Unknowns and limitations
- The audit does not establish desktop-app activation, extension adoption, or conversion performance.
- The product team’s intended audience segmentation and campaign mix were unavailable.
- Public homepage snapshot only, captured September 17, 2026.
- No private analytics, experiment history, or user research was available.
Transferable lessons
- Memorable positioning still needs a nearby category statement when the product introduces a new interaction model.
- A product demonstration can explain complexity, but it should not delay the visitor’s first clear action.
Methodology: Fresh static audit plus desktop and mobile browser captures. The score is a rule-derived prioritization aid, not predicted conversion performance.
Captured 2026-09-17T22:06:00Z from https://raycast.com. Analysis version 1.0.0; audit version 2026.08.31.
Page snapshot · September 17, 2026

Three Findings
Ranked by observable priority. Each finding includes the evidence Nebula used - no opinion, no estimation. Priority scores are rule-based heuristics for fix order, not predicted conversion loss.
Finding 1
Above-Fold Action
The audit source proxy did not find a CTA in the first 2,000 characters.
Evidence
CTA not in first 2,000 chars; rendered viewport confirmation remains required.
Recommended Fix
Confirm the rendered fold and expose one primary start action beside the product explanation if needed.
Finding 2
Category Clarity
The H1 is memorable but does not identify the product category.
Evidence
H1: “Your shortcut to everything.”
Recommended Fix
Add a plain category and audience statement near the brand line.
Finding 3
HTML Payload
The fetched HTML is approximately 385 KiB.
Evidence
Audit snapshot: 385 KiB HTML.
Recommended Fix
Profile and defer non-critical page content.
What This Demonstrates
This teardown examines the public Raycast homepage as a landing page for a desktop productivity tool. It does not evaluate the installed application, extension quality, or user retention.
Work at Raycast? Verify ownership to manage this teardown in your workspace.
Claim this teardownSee what it finds on your page
Same engine, your URL. Free, no signup. Results in under two minutes.
Find the Leak →Already know your page has issues? Skip the audit.
Fix one leak now, $97 →One finding. 48h delivery. No call, no retainer.