occstrategy.com website review

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

19 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

Vimeo costs a phone 40 ms of main-thread work and 9.4 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.

Google CDN costs a phone 514 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.

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

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

The page has 1,781 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

14 long tasks block the main thread while loading, the longest for 129 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.

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

Your largest element takes 20.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to give you the best possible experience on …”.

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

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

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

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

4 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-24, real Chrome visitors' tap response (inp) went from 88 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.3 MB in 121 requests on a phone: other files 9.2 MB (15), images 3.4 MB (50) and scripts 2.3 MB (31). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example casper-roex-400x488.jpg at 390 px wide, shown at 90 px. Resized copies would save about 27 KiB.

8 images (299 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.

2 images further down the page (73 KiB) 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 4.35 g of CO₂e: 521.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

3 links have no real href, so search engines can't follow them.

The homepage links to 83 pages on occstrategy.com and 9 external pages.

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.

/en/about-us and /en/about-us/who-we-are all use the title “Who We Are | OC&C Strategy Consultants”. Search engines can't tell which page to show for a search, so each competes with the others.

/en/about-us/our-locations, /en/about-us/diversity-inclusion, /en/about-us/news-press, /en/industry-expertise, /en/industry-expertise/advanced-analytics-ai and /en/industry-expertise/b2b-services and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

/en/about-us and /en/about-us/who-we-are use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /en/about-us, whose canonical is /en/about-us/who-we-are. 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 52 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.occstrategy.com/en/.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

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

Large scripts ship without source maps.

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 14 fields (5 required). Every extra field lowers completion.

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

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

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

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