Website review, no card needed

zeonchemicals.com logo

zeonchemicals.com website review

Visit site (opens in a new tab)Reviewed 28 October 202621 issues · 67 checks

This review found 21 issues worth fixing on zeonchemicals.com, 5 of them high impact, across 67 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of zeonchemicals.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. zeonchemicals.com at 0.4 s0.4 s
  2. zeonchemicals.com at 0.8 s0.8 s
  3. zeonchemicals.com at 1.1 s1.1 s
  4. zeonchemicals.com at 1.5 s1.5 s
  5. zeonchemicals.com at 1.9 s1.9 s
  6. zeonchemicals.com at 2.3 s2.3 s
  7. zeonchemicals.com at 2.6 s2.6 s
  8. zeonchemicals.com at 3.0 s3.0 s

Speed

6 to fix72
  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72 (desktop: 96). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    300 ms · 385 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Analytics and others), adding 1.1 MB and 357 ms of main-thread time.

  • Google Tag Manager adds 307 ms

    307 ms

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

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 354 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.

  • Reduce unused CSS

    290 ms · 44 KiB

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

  • Improve image delivery

    182 KiB

    3 images could be 182 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    16 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 318 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix72
  • Largest Contentful Paint: 5.8 s

    5.8 s

    Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Zeon Chemicals Specialty Elastomers”.

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Time to Interactive: 6.5 s

    6.5 s

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

  • Speed Index: 3.5 s

    3.5 s

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 42 ms

    42 ms

    Scripts block the page for only 42 ms while loading. Good is under 200 ms.

Images and page weight

100
  • 5 images in older formats

    5 images (389 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.

  • 1 image below the first screen load straight away

    1 image further down the page (166 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.4 g of CO₂ per visit

    0.43 g

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

2 checks passed
  • Page weight: 1.5 MB in 38 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 38 requests on a phone: scripts 797 KiB (8), images 439 KiB (12) and fonts 232 KiB (6). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9797
  • 1 text element with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • No XML sitemap

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

  • No X (Twitter) card tag

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

  • 32 internal links, 12 external

    The homepage links to 32 pages on zeonchemicals.com and 12 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Zeon Chemicals Specialty Elastomers. Let experts guide your next project from conception to completion. Making Rubber t…”.

  • One H1 headline

    Your main headline reads: “Zeon Chemicals”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Rubber Producer and Manufacturer of Specialty Elastomers”.

  • Canonical URL set

    The canonical URL is https://www.zeonchemicals.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

    There is no https://zeonchemicals.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://zeonchemicals.com/tech-spec and https://zeonchemicals.com/video-library have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://zeonchemicals.com/tech-spec, https://zeonchemicals.com/contact-us, https://zeonchemicals.com/locations, https://zeonchemicals.com/zeon-events, https://zeonchemicals.com/making-rubber-that-makes-a-difference/zeon-webinars and https://zeonchemicals.com/making-rubber-that-makes-a-difference/quality-certifications and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 9 small tap targets

    9 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

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

  • Only about 94 words

    The homepage has only about 94 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 5 cookies set on arrival

    5

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

  • No consent tool detected

    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.

  • 7 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at zeonchemicals.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Google Cloud

Company

Employees
317

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on zeonchemicals.com, including 11 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25