LaunchFix · Report LC-7F3K2Q · LaunchGraded Standard 2026.2 · Scanned Oct 20, 2026
Launch readiness report: example-startup.com scored 87 out of 100
Good shape — fix the remaining high-impact issues before launch.
3 blockers · 4 improvements · 44 passing
Up 25 points since your first scan
3 points and 3 blockers from the certificate.
LaunchGraded scores your public launch surface against the LaunchGraded Standard — not your traffic, revenue or product.
9 areas, worst first
Pick an area to see only its findings below.
Where this site stands
AI-assisted summaryExample Startup is close. The page explains itself well and converts cleanly, but three technical blockers would undercut a launch: the homepage is set to noindex, part of it loads over plain HTTP, and one link on the page is dead. Fix those (about an hour) and add a single piece of social proof, and this site clears the readiness bar.
Five quick wins, about 2 hours in all
Every finding, worst first (7)
P0 · Launch blockerGoogle isn't allowed to index your homepage.SEO · ~5 min · 0/3 pts
<meta name="robots" content="index, follow"><meta name="robots" content="noindex, nofollow">P0 · Launch blockerPart of your site isn't served securely.Technical · ~30 min · 0/2 pts
is-on-https failed · 3 insecure requests: http://cdn.example-startup.com/hero.png, http://cdn.example-startup.com/logo.png, http://cdn.example-startup.com/widget.jsP0 · Launch blockerThere are broken links on the page.Technical · ~30 min · gate
GET /changelog → 404 (anchor text "Changelog", in <footer>)P3 · PolishPeople using assistive tech will struggle with your site.Accessibility · ~1 day · 2/3 pts
accessibility 0.83 → round(0.83 × 3) = 2P3 · PolishSome resources load over plain HTTP.Technical · ~30 min · 0/1 pts
http://cdn.example-startup.com/hero.png
http://cdn.example-startup.com/logo.png
http://cdn.example-startup.com/widget.jsP3 · PolishYou have no favicon.Technical · ~15 min · 0/1 pts
<link rel="icon" href="/favicon.ico" sizes="32x32">
<link rel="icon" href="/icon.svg" type="image/svg+xml">no <link rel="icon"> · GET /favicon.ico → 404Protect these when you iterate
Visitors can tell what you do from the first line
4/4Keep the headline specific when you iterate copy — vague rewrites are the most common regression we see.
There's one obvious next step
8/8One primary button above the fold is doing its job — resist adding a second one that competes with it.
Your page loads fast on mobile
5/6Mobile performance is in the good band — watch it when you add analytics, chat widgets or embeds.
Fix the 3 blockers, rescan free, earn the certificate
At 90+ with no blockers you get a public certificate and badge. Launching soon? LaunchDay writes your copy for 12 platforms.
All 51 checks, by area
Messaging
13/13Headline "Invoices your clients actually pay on time" found above the fold (7 words).
One-liner under the headline names the audience (freelancers) and the outcome (paid in 9 days on average).
Product screenshot detected directly below the hero copy.
Title tag "Example Startup — invoicing for freelancers" is present and specific (44 characters).
The page has 620 words of visible body text (floor: 150).
Flesch Reading Ease score is 58, within the 30-70 band.
Conversion
12/12"Start free" is the only primary button above the fold.
Pricing is one click from the nav and visible on the page.
Secondary email opt-in ("Get product updates") found in the footer, separate from the main call to action.
Trust
7/11No testimonial, customer logo, review block or usage number detected on the page.
Privacy policy and terms are both linked from the footer.
Contact link and a support email address found in the footer.
Not a content-style page (no <article> or Article/BlogPosting/NewsArticle markup) — freshness doesn't apply.
Not a content-style page (no <article> or Article/BlogPosting/NewsArticle markup) — author byline doesn't apply.
UX & Mobile
7/7Responsive viewport meta tag present; Lighthouse viewport audit passes.
All tap targets are appropriately sized (Lighthouse tap-targets audit passes).
Body text is 16 px or larger on mobile (Lighthouse font-size audit passes).
SEO
11/14The homepage tells search engines not to index it.
Meta description present (138 characters).
og:title, og:description and a 1200×630 og:image are all set.
Canonical link points at https://example-startup.com/.
Link text is descriptive and every anchor has a crawlable href.
A sitemap at https://example-startup.com/sitemap.xml lists 14 URLs.
All 5 sampled sitemap URLs resolve.
robots.txt references your sitemap.
Performance
8/9Lighthouse mobile performance 91/100 — in the good band. Watch this when you add analytics or chat widgets.
Largest Contentful Paint 1.9 s on mobile.
Cumulative Layout Shift 0.02.
Accessibility
6/7Lighthouse accessibility 83/100 — two low-contrast captions and one unlabelled icon button.
Every meaningful image has alt text.
Both form inputs have visible labels.
<html lang="en"> is set.
Body text and buttons meet 4.5:1 contrast.
Technical
10/14The page is served over HTTPS but two images and one script are loaded over plain HTTP.
Strict-Transport-Security, X-Content-Type-Options and a framing defence are all present.
3 resources load over plain HTTP on an HTTPS page.
No JavaScript errors logged on load.
No favicon linked from the page head and /favicon.ico returns 404.
A logo image is present in the page header.
The plain http:// version of the site redirects to https://.
The www/apex alternate of this domain doesn't independently serve live content.
A random path returns a real 404 with a custom page.
Exactly one <h1>, and no heading levels are skipped.
One link on the page is dead: /changelog returns 404. It's in the footer, so it's on every page.
Discoverability
13/132 JSON-LD blocks parse as valid JSON.
Structured data declares an Organization entity.
The Organization entity has its required fields (name) populated.
No malformed JSON-LD or conflicting duplicate structured data.
BreadcrumbList or QAPage structured data is present.
robots.txt doesn't block the well-known AI crawlers.
/llms.txt is present and returns a 2xx response.