rdw.com website review

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

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

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

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

6 third-party services load with your homepage (YouTube, Ensighten and Other Google APIs/SDKs and others), adding 2.1 MB and 884 ms of main-thread time.

YouTube costs a phone 811 ms of main-thread work and 1.9 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 52 (desktop: 59). Pages that score under 90 lose visitors before the first paint.

2 images could be 397 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

2 KiB could be saved by minifying JavaScript.

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

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

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.

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

Your largest element takes 30.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Five Years of Transformation and Global Expansion NYSE Welc…”.

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

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 17.0 MB in 157 requests on a phone: media 9.7 MB (2), images 3.5 MB (17) and scripts 2.2 MB (60). Under 2 MB keeps phones on slow connections fast.

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

5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 link inside paragraphs relies on colour alone to stand out.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h6, h3 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

There are 6 <h1> headlines (“New Home: 2025”, “Five Years of Transformation and Global Expansion” and “Accelerating Pharmaceutical Development In Space”). One clear main headline is easier for people and search engines.

11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 95 pages on rdw.com and 12 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://rdw.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.

Your homepage links to https://rdw.com/store, which answers with an error. Visitors hit a dead end and search engines drop it.

https://rdw.com/product-archive declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://rdw.com/careers is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://rdw.com/product-archive, https://rdw.com/defense-tech and https://rdw.com/space-tech all use the title “Redwire Space”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rdw.com/newsroom has no meta description, so Google writes the search snippet from whatever text it finds.

https://rdw.com/product-archive, https://rdw.com/defense-tech and https://rdw.com/space-tech use the same meta description. A description written for each page earns more clicks.

https://rdw.com/locations, https://rdw.com/about/community, https://rdw.com/product-archive, https://rdw.com/defense-tech, https://rdw.com/space-tech and https://rdw.com/newsroom and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 792 words of visible text.

Before a visitor clicks anything, the page loads Google Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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