omaze.com website review

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

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

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

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

4 third-party services load with your homepage (posthog.com, Google Tag Manager and Optanon and others), adding 471 KiB and 219 ms of main-thread time.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

15 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 12.5 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 13.0 s. Good is under 3.8 s.

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

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

Your homepage downloads 3.3 MB in 83 requests on a phone: images 2.6 MB (54), scripts 435 KiB (13) and fonts 130 KiB (4). Under 2 MB keeps phones on slow connections fast.

28 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example uk-feb-26.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 60 KiB.

2 images (252 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.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

64 images have no alt text, which hurts accessibility and image search.

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

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

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

There are 8 <h1> headlines (“Win life-changing prizesHelp world-changing causes”, “Making Dreams Come True for Over a Decade” and “Making Dreams Come True for Over a Decade”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 9 pages on omaze.com and 31 external pages.

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://omaze.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://omaze.com/about.html, https://omaze.com/careers.html, https://omaze.com/team.html, https://omaze.com/story.html and https://omaze.com/privacy.html all use the title “Omaze”. Search engines can't tell which page to show for a search, so each competes with the others.

https://omaze.com/about.html, https://omaze.com/careers.html, https://omaze.com/team.html, https://omaze.com/story.html and https://omaze.com/privacy.html use the same meta description. A description written for each page earns more clicks.

https://omaze.com/privacy.html has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 5 pages linked from your homepage and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 14 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,281 words of visible text.

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