zeeco.com website review

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

4 images could be 435 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

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

Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google CDN, Hubspot and Google Tag Manager and others), adding 2.1 MB and 1.2 s of main-thread time.

About 692 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 CDN costs a phone 725 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.

Hubspot costs a phone 248 ms of main-thread work and 338 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.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

8 KiB could be saved by minifying CSS.

6 KiB could be saved by minifying JavaScript.

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 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Refinery Stock Image”.

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

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

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

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

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

Your homepage downloads 5.3 MB in 95 requests on a phone: images 2.8 MB (20), scripts 1.7 MB (24) and other files 475 KiB (24). Under 2 MB keeps phones on slow connections fast.

AdobeStock_87658741.jpeg weighs 628 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example AdobeStock_87658741.jpeg at 4,000 px wide, shown at 390 px. Resized copies would save about 805 KiB.

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

Required ARIA attributes must be provided: 3 elements on the page fail this check, rated critical by axe-core.

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

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 29 characters: “Zeeco | Redefining Combustion”. 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 174 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 92 pages on zeeco.com and 9 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://www.zeeco.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.zeeco.com/ar, https://www.zeeco.com/ru, https://www.zeeco.com/es, https://www.zeeco.com/pt and https://www.zeeco.com/zh 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.zeeco.com/ar, https://www.zeeco.com/ru, https://www.zeeco.com/es, https://www.zeeco.com/pt and https://www.zeeco.com/zh all use the title “Zeeco | Redefining Combustion”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.zeeco.com/contact has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.zeeco.com/ar, https://www.zeeco.com/ru, https://www.zeeco.com/es, https://www.zeeco.com/pt and https://www.zeeco.com/zh use the same meta description. A description written for each page earns more clicks.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 823 words of visible text.

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

Opening the homepage sets 3 cookies (measured from a US location before any click).

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