Skip to content
LaunchGraded
Score my site
This is a sample. Example Startup isn't real — every number below comes from a fixture so you can see exactly what a report contains.Score your own site →

Launch readiness report — Example Startup

Report LC-7F3K2Q · example-startup.comLaunchGraded Standard 2026.1 · scanned 10 September 2026
LaunchGraded ScoreAlmost Ready

Good shape — fix the remaining high-impact issues before launch.

3 blockers·3 improvements·25 passing

LaunchGraded scores your public launch surface against the LaunchGraded Standard — not your traffic, revenue or product.

Overview

Where this site stands.

AI-assisted summary

Example 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.

Launch blockers (3)

Must fix before launch.

P0 · Launch blocker~5 minseo.indexable

Google isn't allowed to index your homepage.

Why it matters
Your page tells search engines to stay away. Every link, mention and launch post will point at a page Google won't list.
Fix
Remove the noindex directive from the robots meta tag or X-Robots-Tag header, redeploy, and rescan. The homepage tells search engines not to index it.
Technical
<meta name="robots" content="noindex, nofollow">
Think this is wrong? Tell us0/4 pts
P0 · Launch blocker~30 mintech.https

Part of your site isn't served securely.

Why it matters
Browsers show a "Not secure" warning when a page is served over HTTP or mixes HTTPS and HTTP content. For a first-time visitor that reads as "don't type your email here".
Fix
Serve the page and every asset — images, scripts, fonts, embeds — over HTTPS, and redirect http:// to https://. The page is served over HTTPS but two images and one script are loaded over plain HTTP.
Technical
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.js
Think this is wrong? Tell us0/3 pts
P0 · Launch blocker~30 mingate.broken_links

There are broken links on the page.

Why it matters
A dead link on launch day is the fastest way to look unfinished. If it's in the nav or footer, it's on every page.
Fix
Update or remove the link, then rescan — this check is a gate, so fixing it lifts the verdict cap. One link on the page is dead: /changelog returns 404. It's in the footer, so it's on every page.
Technical
GET /changelog → 404 (anchor text "Changelog", in <footer>)
Think this is wrong? Tell us0/0 pts
Fix first

The five things to do first.

Ordered by severity, then impact, then least effort.

  1. 1Google isn't allowed to index your homepage~5 minseo.indexable
  2. 2Part of your site isn't served securely~30 mintech.https
  3. 3There are broken links on the page~30 mingate.broken_links
  4. 4You show no evidence that other people use this~2 htrust.social_proof
  5. 5You have no favicon~15 mintech.favicon

Quick wins — under an hour each

  • Google isn't allowed to index your homepage~5 min
  • Part of your site isn't served securely~30 min
  • There are broken links on the page~30 min
  • You have no favicon~15 min
Improvements (3)

Worth fixing before or soon after launch.

P1 · High impact~2 htrust.social_proof

You show no evidence that other people use this.

Why it matters
A first-time visitor has no reason to believe you yet. Without logos, testimonials, review counts or usage numbers, they have only your word that this works.
Fix
Add one testimonial with a name and role near the primary call to action, or a row of customer logos, or a concrete usage number. No testimonial, customer logo, review block or usage number detected on the page.
Technical
no [class*="testimonial"], [class*="review"], [class*="trusted-by"] block detected
Think this is wrong? Tell us0/6 pts
P3 · Polish~1 daya11y.score

People using assistive tech will struggle with your site.

Why it matters
Accessibility failures shut out visitors using screen readers or keyboards, and the same issues — unlabelled controls, poor contrast — trip up everyone on a phone in sunlight.
Fix
Open the Lighthouse accessibility report and fix the failing audits in order; most are one-line fixes to labels, roles and contrast. Lighthouse accessibility 83/100 — two low-contrast captions and one unlabelled icon button.
Technical
accessibility 0.83 → round(0.83 × 5) = 4
Think this is wrong? Tell us4/5 pts
P3 · Polish~15 mintech.favicon

You have no favicon.

Why it matters
A blank tab icon is a small thing that signals "unfinished" in every tab, bookmark and share card.
Fix
Add a favicon (an SVG or 32×32 PNG) and link it from the page head. No favicon linked from the page head and /favicon.ico returns 404.
Technical
no <link rel="icon"> · GET /favicon.ico → 404
Think this is wrong? Tell us0/1 pts
What's already strong (7)

Protect these when you iterate.

  • Visitors can tell what you do from the first line

    8/8

    Keep the headline specific when you iterate copy — vague rewrites are the most common regression we see.

  • Your headline is backed up by a one-liner

    4/4

    Headline and one-liner read as a pair — keep them in sync when either changes.

  • Visitors can see the product (screenshot or demo)

    4/4

    Showing the real product removes guesswork — refresh the screenshot when the UI changes so it never looks stale.

  • There's one obvious next step

    11/11

    One primary button above the fold is doing its job — resist adding a second one that competes with it.

  • Visitors can find out what it costs (or how to talk to you)

    4/4

    Visitors can self-qualify without friction — keep pricing one click from the nav as the site grows.

  • Your page adapts to phones

    4/4

    The page is set up to render at phone width — retest on a real phone after any big layout change.

  • Your page loads fast on mobile

    7/8

    Mobile performance is in the good band — watch it when you add analytics, chat widgets or embeds.

Every check

Findings by dimension.

Messaging

18/18
PassVisitors can tell what you do from the first linePass

Headline "Invoices your clients actually pay on time" found above the fold (7 words).

PassYour headline is backed up by a one-linerPass

One-liner under the headline names the audience (freelancers) and the outcome (paid in 9 days on average).

PassVisitors can see the product (screenshot or demo)Pass

Product screenshot detected directly below the hero copy.

PassYour browser tab and search title say what you arePass

Title tag "Example Startup — invoicing for freelancers" is present and specific (44 characters).

Conversion

16/16
PassThere's one obvious next stepPass

"Start free" is the only primary button above the fold.

PassVisitors can find out what it costs (or how to talk to you)Pass

Pricing is one click from the nav and visible on the page.

PassNot-ready visitors have a low-commitment way to stay in touchPass

Secondary email opt-in ("Get product updates") found in the footer, separate from the main call to action.

Trust

6/12
FailYou show no evidence that other people use thisP1 · High impact

No testimonial, customer logo, review block or usage number detected on the page.

PassPrivacy policy and terms are linkedPass

Privacy policy and terms are both linked from the footer.

PassVisitors can reach a humanPass

Contact link and a support email address found in the footer.

UX & Mobile

10/10
PassYour page adapts to phonesPass

Responsive viewport meta tag present; Lighthouse viewport audit passes.

PassButtons and links are tappable on a phonePass

All tap targets are appropriately sized (Lighthouse tap-targets audit passes).

PassText is legible on a phonePass

Body text is 16 px or larger on mobile (Lighthouse font-size audit passes).

SEO

10/14
FailGoogle isn't allowed to index your homepageP0 · Launch blocker

The homepage tells search engines not to index it.

PassSearch results show a description you wrotePass

Meta description present (138 characters).

PassYour link looks right when sharedPass

og:title, og:description and a 1200×630 og:image are all set.

PassSearch engines know the one true URLPass

Canonical link points at https://example-startup.com/.

PassLinks say where they goPass

Link text is descriptive and every anchor has a crawlable href.

Performance

11/12
PassYour page loads fast on mobilePass

Lighthouse mobile performance 91/100 — in the good band. Watch this when you add analytics or chat widgets.

PassThe main content appears within 2.5 secondsPass

Largest Contentful Paint 1.9 s on mobile.

PassThe page doesn't jump around while loadingPass

Cumulative Layout Shift 0.02.

Accessibility

9/10
FailPeople using assistive tech will struggle with your siteP3 · Polish

Lighthouse accessibility 83/100 — two low-contrast captions and one unlabelled icon button.

PassImages have text alternativesPass

Every meaningful image has alt text.

PassForm fields have labelsPass

Both form inputs have visible labels.

PassThe page declares its languagePass

<html lang="en"> is set.

PassText is readable against its backgroundPass

Body text and buttons meet 4.5:1 contrast.

Technical

4/8
FailPart of your site isn't served securelyP0 · Launch blocker

The page is served over HTTPS but two images and one script are loaded over plain HTTP.

PassNothing is silently breaking in the browserPass

No JavaScript errors logged on load.

FailYou have no faviconP3 · Polish

No favicon linked from the page head and /favicon.ico returns 404.

PassA wrong URL gets a proper 404Pass

A random path returns a real 404 with a custom page.

FailThere are broken links on the pageP0 · Launch blocker

One link on the page is dead: /changelog returns 404. It's in the footer, so it's on every page.

Launch readiness isn't product-market fit. A 95/100 website can still launch a product nobody wants. LaunchGraded audits your public launch experience — not whether your business will succeed.

Now see yours.

https://
What the Full Report costs