ogsystems.com website review

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

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

8 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

About 146 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

3 files are served with short cache lifetimes, so returning visitors download them again (10 KiB).

1 long task block the main thread while loading, the longest for 57 ms. During a long task the page ignores taps.

3 third-party services load with your homepage (FontAwesome CDN, bc0a.com and Adobe TypeKit), adding 271 KiB and 30 ms of main-thread time.

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

11 KiB could be saved by minifying CSS.

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

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “When challenges arise, we say, “Challenge Accepted.” We're …”.

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 5.4 MB in 62 requests on a phone: images 3.7 MB (17), media 1.3 MB (3) and fonts 163 KiB (7). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.53 g of CO₂e: 183.1 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”.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Your title is only 19 characters: “Parsons Corporation”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“Battle Tested, Mission Focused”, “From Strategy To Strike” and “Vision In Motion”). One clear main headline is easier for people and search engines.

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

The homepage links to 88 pages on ogsystems.com and 11 external pages.

There is no https://www.parsons.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 1 page by a URL that isn't its canonical one, for example https://www.parsons.com/Urban-Development, whose canonical is https://www.parsons.com/urban-development. 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 51 found) and read each the way a search engine does.

9 of 23 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”.

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.

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

Opening the homepage sets 1 cookie (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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.