omegacollectiv.com website review

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

1 image could be 643 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

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

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

About 196 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 404 KiB and 171 ms of main-thread time.

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

About 26 KiB of CSS is downloaded but never applied on this page.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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.

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

20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

Your title is 67 characters, so Google will cut it off around 60: “OmegaCollectiv - Hire a team to build your early-stage SaaS product”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 50 characters: “Hire a team to build your early-stage SaaS product”. 70 to 160 characters is enough to sell the click.

No XML sitemap at https://omegacollectiv.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at omegacollectiv.com/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 8 pages on omegacollectiv.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://omegacollectiv.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.

/ and https://omegacollectiv.com/contact.html all use the title “OmegaCollectiv - Hire a team to build your early-stage SaaS product”. Search engines can't tell which page to show for a search, so each competes with the others.

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

We fetched 2 pages linked from your homepage 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.

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

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 669 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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