ocoglobal.com website review

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.6 MB and 885 ms of main-thread time.

Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

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

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

13 images could be 410 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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

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

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

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

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

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.

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 9.2 s on a phone. Good is under 1.8 s.

Your largest element takes 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OCO GLOBAL Shaping Future Economies”.

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

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

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

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

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

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

Your homepage downloads 3.2 MB in 82 requests on a phone: scripts 1.4 MB (27), images 1.2 MB (25) and other files 358 KiB (9). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (363 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example dubai-start-500x500.jpg at 500 px wide, shown at 147 px. Resized copies would save about 17 KiB.

4 images (296 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

2 buttons have no accessible name, so screen readers announce just “button”.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Structured data found (BreadcrumbList, WebPage and WebSite) but with 1 problem, for example “ld+json block 2 is not valid JSON (Bad control character in string literal in JSON at position )”.

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

The homepage links to 49 pages on ocoglobal.com and 1 external page.

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://www.ocoglobal.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.

https://www.ocoglobal.com/zh-hans, https://www.ocoglobal.com/us, https://www.ocoglobal.com/mena, https://www.ocoglobal.com/fr and https://www.ocoglobal.com/de declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://www.ocoglobal.com/zh-hans, https://www.ocoglobal.com/us, https://www.ocoglobal.com/mena, https://www.ocoglobal.com/fr and https://www.ocoglobal.com/de all use the title “Economic Development, Trade & Investment Services”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ocoglobal.com/trade-and-investment, https://www.ocoglobal.com/innovation-and-entrepreneurship, https://www.ocoglobal.com/talent-and-skills, https://www.ocoglobal.com/ecosystem-enablers, https://www.ocoglobal.com/case-studies and https://www.ocoglobal.com/strategic-partnerships and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ocoglobal.com/zh-hans, https://www.ocoglobal.com/us, https://www.ocoglobal.com/mena, https://www.ocoglobal.com/fr and https://www.ocoglobal.com/de use the same meta description. A description written for each page earns more clicks.

https://www.ocoglobal.com/about/publications, https://www.ocoglobal.com/about/senior-management-team and https://www.ocoglobal.com/social-responsibility took over 3 s to send their HTML from our server.

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

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

Social proof on the homepage: 6 customer or partner logos. 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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (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 3 cookies (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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.