Website review, no card needed
americanchemistry.com website review
Visit site (opens in a new tab)Reviewed 20 October 202644 issues · 90 checks
This review found 44 issues worth fixing on americanchemistry.com, 17 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.6 s |
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 137 ms |
| May 9, 2026 | 138 ms |
| May 16, 2026 | 142 ms |
| May 23, 2026 | 142 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 134 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 141 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 150 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 213 ms |
| Aug 29, 2026 | 195 ms |
| Sep 5, 2026 | 202 ms |
| Sep 12, 2026 | 177 ms |
| Sep 19, 2026 | 160 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 181 ms |
| Oct 10, 2026 | 206 ms |
| Oct 17, 2026 | 223 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
3.6 s · 788 KiBAbout 788 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Render-blocking requests
3.3 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Use efficient cache lifetimes
1.5 s · 627 KiB18 files are served with short cache lifetimes, so returning visitors download them again (627 KiB).
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and termly.io and others), adding 1.4 MB and 1.3 s of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51 (desktop: 64). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
590 ms · 182 KiBAbout 182 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 590 ms faster on a phone.
YouTube adds 652 ms
652 msYouTube costs a phone 652 ms of main-thread work and 974 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.
Google Tag Manager adds 437 ms
437 msGoogle Tag Manager costs a phone 437 ms of main-thread work and 200 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.
Improve image delivery
300 ms · 77 KiB2 images could be 77 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 261 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Document request latency
77 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 10.6 s
10.6 sThe first text or image appears after 10.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 17.0 s
17.0 sThe page becomes fully interactive after 17.0 s. Good is under 3.8 s.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
Real-user INP: 223 ms
223 msReal visitors wait 223 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 56% slower for real visitors
+56%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 137 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.6 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 262 ms
262 msScripts block taps and scrolling for 262 ms in total while the page loads. Good is under 200 ms.
2 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.7 MB in 64 requests
2.7 MBYour homepage downloads 2.7 MB in 64 requests on a phone: scripts 1.5 MB (16), images 599 KiB (14) and HTML 287 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 91.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA attributes must conform to valid names (4 elements)
ARIA attributes must conform to valid names: 4 elements on the page fail this check, rated critical by axe-core.
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (26 characters)
Your title is only 26 characters: “American Chemistry Council”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
12 links with vague text
12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
115 internal links, 10 external
The homepage links to 115 pages on americanchemistry.com and 10 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.americanchemistry.com/.
Structured data in place
Structured data found: 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.americanchemistry.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
28%A phone browser shows 1,065 words, but the HTML your server sends has only 296. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No Organization structured data
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.
No llms.txt
There is no https://www.americanchemistry.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.
1 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.
Other pages
1 linked page is broken
Your homepage links to https://www.americanchemistry.com/oauth2/acc-connect/auth0, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page with very little text
https://www.americanchemistry.com/chemistry-in-america-industry-innovation-impact/news-trends has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.
6 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
41 small tap targets
41 of 82 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.americanchemistry.com/acc-frontend/2.4.0/dist/css/main.css' from origin 'ht…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,065 words of copy
The homepage carries about 1,065 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
2 calls to action
The homepage has 2 calls to action, for example “Learn more”.
1 short form
A short form (2 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).
14 other companies contacted
Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Termly
A consent management tool (Termly) loads with the page.
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 americanchemistry.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Company
- Founded
- 1872
- Headquarters
- Washington, D.C.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on americanchemistry.com, including 23 speed issues, 4 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.