ngc.com website review

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

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

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

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Optanon and cloudfront.net and others), adding 508 KiB and 754 ms of main-thread time.

Google Tag Manager costs a phone 553 ms of main-thread work and 223 KiB 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.

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

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

Desktop scores 72 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

3 KiB JavaScript is shipped twice across bundles.

Your largest element takes 15.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to enhance user experience and to…”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 146.9 MB in 89 requests on a phone: media 143.7 MB (29), images 1.3 MB (8) and scripts 1.3 MB (25). Under 2 MB keeps phones on slow connections fast.

Arctic-Satellite-Broadband-Mission-slide-01_Original file.jp weighs 498 KiB. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example Arctic-Satellite-Broadband-Mission-slide-01_Original file.jp at 2,000 px wide, shown at 310 px. Resized copies would save about 919 KiB.

6 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (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).

Your title is only 23 characters: “Home | Northrop Grumman”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“Outpacing”, “Every” and “Threat”). One clear main headline is easier for people and search engines.

Your meta description is 303 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 24 pages on ngc.com and 11 external pages.

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

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.northropgrumman.com/Suppliers, whose canonical is https://www.northropgrumman.com/suppliers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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

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

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

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 7 cookies (measured from a US location before any click).

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