ecomgroup.com website review

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

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

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

73 KiB could be saved by minifying CSS.

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

1 image could be 21 KiB 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.

3 third-party services load with your homepage (Cookiebot, Cloudflare CDN and Google Tag Manager), adding 502 KiB and 131 ms of main-thread time.

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

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

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need.

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

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.

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

Real visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 8.9 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 personalise content and ads, to provide s…”.

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

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

2 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 122 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.3 MB in 55 requests on a phone: images 1.3 MB (14), scripts 597 KiB (23) and fonts 269 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

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

1 form field has 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.

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 15 characters: “Homepage | ECOM”. 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.

Your meta description is 242 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

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

The homepage links to 60 pages on ecomgroup.com and 6 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.

/products-services/cocoa and /products-services/cocoa/cocoa-beans all use the title “ECOM Cocoa: Sustainable Sourcing and Supply Chain Solutions for Cocoa…”. Search engines can't tell which page to show for a search, so each competes with the others.

/about-us/policies has no meta description, so Google writes the search snippet from whatever text it finds.

/products-services/cocoa and /products-services/cocoa/cocoa-beans 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 /products-services/cocoa/cocoa-beans, whose canonical is /products-services/cocoa. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/products-services/cocoa/cocoa-products has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'innerHTML')”.

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

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

ecomgroup.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

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

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

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.

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

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