ostglobal.com website review

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

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

About 1.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.8 s faster on a phone.

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

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and wpenginepowered.com and others), adding 1.3 MB and 748 ms of main-thread time.

Google CDN costs a phone 678 ms of main-thread work and 1.1 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.

49 KiB could be saved by minifying CSS.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

17 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.

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

Your largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Optimal Solutions and Technologies”.

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

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

Scripts block taps and scrolling for 403 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' largest content (lcp) went from 3.8 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 21.8 MB in 117 requests on a phone: media 14.2 MB (2), images 2.4 MB (9) and scripts 1.9 MB (43). Under 2 MB keeps phones on slow connections fast.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There are 10 <h1> headlines (“Innovative Solutions.”, “Unmatched Capabilities.” and “Innovation in Motion”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 98 pages on ostglobal.com and 5 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 /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.

/who-we-are/in-the-news and /our-capabilities have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 34 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”.

1 link from your homepage to your own site is broken, for example https://ostglobal.com/case-studies-white-papers/ (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ostglobal.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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.

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

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

The homepage has only about 34 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

DMARC is set to p=none, so mail pretending to be ostglobal.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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