Website review, no card needed

tchem.com logo

tchem.com website review

Visit site (opens in a new tab)Reviewed 4 November 202626 issues · 74 checks

This review found 26 issues worth fixing on tchem.com, 10 of them high impact, across 74 checks. The most urgent: improve image delivery. 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

Real-visitor load time (LCP)75th percentile, phones
5.3 s3.0 sMay 16Oct 313.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.9 s
May 23, 20264.7 s
May 30, 20264.7 s
Jun 6, 20265.0 s
Jun 13, 20265.0 s
Jun 20, 20264.9 s
Jun 27, 20264.6 s
Jul 4, 20263.8 s
Jul 11, 20263.5 s
Jul 18, 20263.2 s
Jul 25, 20263.5 s
Aug 1, 20263.7 s
Aug 8, 20263.4 s
Aug 15, 20263.8 s
Aug 22, 20263.4 s
Aug 29, 20263.6 s
Sep 5, 20264.1 s
Sep 12, 20263.7 s
Sep 19, 20264.1 s
Sep 26, 20263.9 s
Oct 3, 20263.7 s
Oct 10, 20263.6 s
Oct 17, 20263.7 s
Oct 24, 20263.5 s
Oct 31, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
116 ms66 msMay 16Oct 3176 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202694 ms
May 23, 2026105 ms
May 30, 2026105 ms
Jun 6, 2026110 ms
Jun 13, 2026104 ms
Jun 20, 202695 ms
Jun 27, 202684 ms
Jul 4, 202676 ms
Jul 11, 202675 ms
Jul 18, 202675 ms
Jul 25, 202673 ms
Aug 1, 202672 ms
Aug 8, 202672 ms
Aug 15, 202672 ms
Aug 22, 202674 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202684 ms
Sep 19, 202688 ms
Sep 26, 202684 ms
Oct 3, 202684 ms
Oct 10, 202677 ms
Oct 17, 202678 ms
Oct 24, 202679 ms
Oct 31, 202676 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of tchem.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tchem.com at 1.1 s1.1 s
  2. tchem.com at 2.1 s2.1 s
  3. tchem.com at 3.2 s3.2 s
  4. tchem.com at 4.3 s4.3 s
  5. tchem.com at 5.3 s5.3 s
  6. tchem.com at 6.4 s6.4 s
  7. tchem.com at 7.4 s7.4 s
  8. tchem.com at 8.5 s8.5 s

Speed

5 to fix65
  • Improve image delivery

    1.4 s · 356 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Use efficient cache lifetimes

    450 ms · 3.0 MB

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

  • Mobile performance score: 65

    65/100

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

  • Reduce unused JavaScript

    450 ms · 73 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Cloudflare CDN and others), adding 364 KiB and 293 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 10 KiB

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

  • 3 long tasks on the main thread

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 77 ms

    77 ms

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

Core Web Vitals

8 to fix50
  • Fails Core Web Vitals for real visitors

    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-user LCP: 4.2 s

    4.2 s

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

  • Real-user TTFB: 2.5 s

    2.5 s

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

  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Thatcher Home Graphic Main”. Most of its time is resource load delay (5.6 s).

  • Speed Index: 11.4 s

    11.4 s

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

  • Time to Interactive: 9.8 s

    9.8 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • 12 images without width and height

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

6 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 22% faster for real visitors

    -22%

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

  • Largest content (LCP) got 26% faster for real visitors

    -26%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.9 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 39 ms

    39 ms

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

Images and page weight

4 to fix52
  • Page weight: 11.9 MB in 73 requests

    11.9 MB

    Your homepage downloads 11.9 MB in 73 requests on a phone: media 9.9 MB (2), images 1.4 MB (27) and scripts 362 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (1.1 MB) 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.

  • An image on the first screen is lazy-loaded

    Thatcher-Truck-768x256.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 14 images below the first screen load straight away

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

  • About 3.4 g of CO₂ per visit

    3.36 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9699
  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 2 H1 headlines

    There are 2 <h1> headlines (“Home” and “From agriculture to water treatment, we’re the ch…”). One clear main headline is easier for people and search engines.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 56 internal links, 4 external

    The homepage links to 56 pages on tchem.com and 4 external pages.

7 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Family-founded in 1967, Thatcher Company is a trusted global leader in chemical manufacturing, distribution, and relate…”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “Thatcher Company - The Chemistry Experts”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.tchem.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (426 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 10 pages slow to respond

    https://www.tchem.com/industries, https://www.tchem.com/construction, https://www.tchem.com/mining, https://www.tchem.com/power-generation, https://www.tchem.com/toll-blending and https://www.tchem.com/water-treatment and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • No social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

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

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

  • About 319 words of copy

    The homepage carries about 319 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET IN TOUCH”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “get in touch”, “LEARN MORE” and “LEARN MORE ABOUT OUR VALUES”.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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 tchem.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
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on tchem.com, including 13 speed issues, 2 SEO issues 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