robertsspaceindustries.com website review

115 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

18 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.

About 499 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

About 635 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.

Your mobile performance score is 26 (desktop: 28). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 5.8 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,822 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

16 long tasks block the main thread while loading, the longest for 213 ms. During a long task the page ignores taps.

Polyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

2 third-party services load with your homepage (Cookiebot and Adobe TypeKit), adding 239 KiB and 61 ms of main-thread time.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

35 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

The first text or image appears after 9.4 s on a phone. Good is under 1.8 s.

Your largest element takes 24.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wishlist Squadron 42 Today! The year is 2945. The United Em…”.

The page becomes fully interactive after 24.9 s. Good is under 3.8 s.

Visually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.

The layout shifts by 0.411 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 451 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 160 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.1 MB in 165 requests on a phone: media 5.9 MB (3), other files 2.1 MB (31) and scripts 1.4 MB (88). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 2.86 g of CO₂e: 343.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

15 visible links have no text or label, so screen readers cannot say where they go.

4 tap targets are too small or too close together to hit reliably with a finger.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 24 characters: “Roberts Space Industries”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

A phone browser shows 290 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://robertsspaceindustries.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

9 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 290 words of visible text.

Opening the homepage sets 1 cookie (measured from a US location before any click).

Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.