“A launch tracker that’s still waiting on its own liftoff.”
Next Spaceflight looks like it knows exactly where every rocket is headed, except its own homepage is stuck in traffic on the pad. The schedule is there, the data is there, but the page keeps tripping over its own sneakers like a demo flight with the brakes on.
https://nextspaceflight.com/
screenshot
TECHNICAL SUMMARY
The biggest drag is performance: Largest Contentful Paint is 14.3 s, interactive time is 14.5 s, and unused JavaScript could save 399 KiB. SEO is partly in orbit with a perfect pageSpeed SEO score, but the HTML still ships with no canonical, no sitemap.xml, no JSON-LD, and no H1, which is a lovely way to make search engines guess your identity like a weather forecast with no map. Fix the heavy hero assets first, then clean up the page’s structural signals so discovery and community signups don’t bleed out before the page even settles.
LCP14.3 sInteractive14.5 sUnused JS Savings399 KiBFCP1.5 s
🔥Your Largest Contentful Paint is 14.3 s, so the homepage loads like a launch window that forgot what year it is.
💀
The page spends so long getting out of the launch tower that the rocket may age into a museum exhibit.
→
Compress hero images and switch them to WebP/AVIF so the homepage stops dragging a 14.3 s LCP around like spare fuel tanks.
LCP: 14.3 sImpact: highEffort: medium
Why this matters
A 14.3 s LCP is the biggest visible bottleneck, and the hero is almost certainly doing the damage.
→
Defer non-critical JavaScript and trim render-blocking resources so interactive time stops hanging at 14.5 s.
TBT: 70 msImpact: highEffort: medium
Why this matters
Even with modest blocking time, the page still reaches interactivity far too late, so reduce upfront script burden.
→
Enable CDN caching and long cache TTLs for static assets to make better use of the 1.5 s FCP you already have.
FCP: 1.5 sImpact: mediumEffort: low
Why this matters
First paint is decent, but static asset caching can help keep the experience from stalling after the initial render.
02
SEO
75
SEO Score100Canonicalmissingsitemap.xmlMissingSchemaNoneH1 Count0
🔥You’ve got a perfect SEO score from PageSpeed, then the HTML shows up without a canonical tag, like a rocket with no launch site.
💀
Search engines can probably find the page; understanding it is where the astrophysics starts.
→
Add a self-referencing canonical tag so the homepage stops making duplicate-signal confetti out of itself.
Canonical: missingImpact: highEffort: low
Why this matters
Without a canonical, search engines get no clear preferred URL for this page.
→
Add JSON-LD structured data for the page type so the site stops giving search engines a blank stare where context should be.
Schema: NoneImpact: mediumEffort: medium
Why this matters
There are zero structured data blocks, so rich-result and entity context are completely absent.
→
Add one H1 tag with the primary value proposition and generate a sitemap.xml so the launch schedule is easier to understand and index.
H1 Count: 0Impact: highEffort: low
Why this matters
An H1 is missing entirely, and the page also lacks a sitemap, which weakens indexability and content hierarchy.
03
DESIGN
80
Images26Missing Alt2H1 Count0Font Families4
🔥The page has 26 images, but no H1 to anchor them, so the visual hierarchy is doing air traffic control with no runway lights.
💀
The design knows how to look competent, but it still forgot to give the page a proper mission patch.
→
Add supporting imagery intentionally around the 26 images so the page feels curated instead of just fully loaded.
Images: 26Impact: mediumEffort: medium
Why this matters
The page already relies on a lot of imagery, so better supporting composition will make the layout feel designed rather than assembled.
→
Fix the 2 missing alt attributes so the visual system stops leaving accessibility on the launch pad.
Missing Alt: 2Impact: mediumEffort: medium
Why this matters
Two missing alt attributes are enough to fail a basic accessibility check and weaken semantic clarity.
→
Test spacing and alignment across breakpoints so the viewport remains stable when the page is squeezed into mobile launch windows.
Viewport: PresentImpact: lowEffort: medium
Why this matters
The viewport is present, but responsive behavior still needs real cross-device validation to preserve the current clean layout.
04
COPY
91
Word Count302Sentence Count14CTA Count2Social Proof1
🔥Your homepage has 302 words across 14 sentences, which is lean for a site carrying 40 links and a whole launch universe.
💀
The copy is competent, but that broken CTA is the literary equivalent of a mission scrub.
→
Tighten the headline into one clear value statement so the page stops hiding the point behind launch-card small talk.
H1 Count: 0Impact: highEffort: low
Why this matters
There is no H1, so the page lacks a single, obvious headline for the brand promise.
→
Make the primary CTA stand out because 2 CTAs on a 302-word home page is not enough guidance for a community build.
CTA Count: 2Impact: mediumEffort: low
Why this matters
The page has very few CTAs relative to its content, so the main action needs a clearer spotlight.
→
Break long paragraphs into shorter, skimmable chunks so the 14 sentences don’t read like a launch status memo.
Avg Words/Sentence: 22Impact: lowEffort: medium
Why this matters
The text is readable but still dense enough to benefit from shorter, faster-scan formatting.
05
UX
71
Broken Assets12Buttons9Links40Footermissing
🔥Twelve broken assets is not a small hiccup; it’s the site serving users a launch checklist with missing bolts.
💀
The interface is trying to guide space enthusiasts while tripping over its own asset pipeline.
→
Repair the 12 failed asset URLs and deployment paths so the page stops arriving with half the launch hardware missing.
Broken Assets: 12Impact: highEffort: medium
Why this matters
Broken assets create immediate user-facing friction and can interrupt scripts, data, and visuals.
→
Add a consistent footer so the page has an actual landing zone instead of ending like a cut livestream.
Nav/Footer: Nav / No footerImpact: lowEffort: medium
Why this matters
The site has navigation but no footer, which weakens consistency and wayfinding on longer browsing sessions.
→
Keep runtime errors at zero with browser smoke tests even though current console errors are already clean, because the broken fetches prove the page is not done behaving.
JS Errors: 0Impact: lowEffort: low
Why this matters
There are no console errors today, but routine monitoring helps catch regressions before they become visible issues.
06
CONVERSION
67
CTA Count2Contact PathPresentSocial Proof1External Links17 of 40
🔥Two CTAs on a community-focused home page is shy behavior for a site that wants people to join the orbit.
💀
The page asks for commitment with the enthusiasm of a launch scrub notice.
→
Add a primary CTA above the fold that directly matches the community offer so visitors don’t have to decode the launch schedule first.
CTA Count: 2Impact: mediumEffort: low
Why this matters
With only 2 CTAs, the page needs one dominant action to guide signups instead of scattering attention.
→
Place social proof closer to the CTA because 1 trust signal is not much reassurance for a page asking for community commitment.
Social Proof: 1Impact: mediumEffort: low
Why this matters
The site has very limited proof near the action, which makes the join path feel under-supported.
→
Offer a low-friction contact option alongside the existing contact path so interested users don’t have to hunt for a way in.
Contact Path: PresentImpact: lowEffort: medium
Why this matters
A contact path exists, but making it more visible and immediate can improve the likelihood of follow-through.
