Website review, no card needed

pure-chemical.com logo

pure-chemical.com website review

Visit site (opens in a new tab)Reviewed 3 November 202643 issues · 79 checks

This review found 43 issues worth fixing on pure-chemical.com, 13 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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 pure-chemical.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pure-chemical.com at 0.8 s0.8 s
  2. pure-chemical.com at 1.5 s1.5 s
  3. pure-chemical.com at 2.3 s2.3 s
  4. pure-chemical.com at 3.0 s3.0 s
  5. pure-chemical.com at 3.8 s3.8 s
  6. pure-chemical.com at 4.6 s4.6 s
  7. pure-chemical.com at 5.3 s5.3 s
  8. pure-chemical.com at 6.1 s6.1 s

Speed

11 to fix24
  • Reduce unused JavaScript

    3.1 s · 1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Improve image delivery

    1.6 s · 852 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 24

    24/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, PageSense and Clarity and others), adding 821 KiB and 961 ms of main-thread time.

  • Font display

    950 ms

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

  • Reduce unused CSS

    600 ms · 179 KiB

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

  • Google Tag Manager adds 694 ms

    694 ms

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

  • Use efficient cache lifetimes

    400 ms · 93 KiB

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

  • Main-thread work: 4.0 s

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

  • 1,707 HTML elements

    The page has 1,707 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 15 long tasks on the main thread

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

  • Legacy JavaScript

    50 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 50 ms faster on a phone.

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 243 ms

    243 ms

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

Core Web Vitals

7 to fix17
  • Largest Contentful Paint: 23.9 s

    23.9 s

    Your largest element takes 23.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Catalyzing Your Growth ! Trusted Chemical Partner Since 198…”.

  • Time to Interactive: 24.2 s

    24.2 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • Cumulative Layout Shift: 0.608

    0.608

    The layout shifts by 0.608 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 742 ms

    742 ms

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

  • 30 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

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

Images and page weight

4 to fix43
  • Page weight: 9.9 MB in 106 requests

    9.9 MB

    Your homepage downloads 9.9 MB in 106 requests on a phone: media 5.3 MB (1), images 2.4 MB (38) and fonts 1.1 MB (9). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

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

  • 18 images below the first screen load straight away

    18 images further down the page (1,005 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 7 images far larger than shown

    70 KiB

    7 images are downloaded at several times the size a phone draws them, for example getintouch.jpeg at 1,152 px wide, shown at 366 px. Resized copies would save about 70 KiB.

  • About 2.8 g of CO₂ per visit

    2.79 g

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

Accessibility

5 to fixGoogle 9294
  • 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.

  • All page content should be contained by landmarks (7 elements)

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

  • 19 form fields without a label

    19 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 9 links without text

    9 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (8 elements)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

6 to fixGoogle 9270
  • No H1 headline

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

  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Pure Chemicals Co is the leading chemical supplier and distributor”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

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

  • No XML sitemap

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

  • 2 links with vague text

    2 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 incomplete here.

  • 112 internal links, 22 external

    The homepage links to 112 pages on pure-chemical.com and 22 external pages.

3 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Pure Chemicals Co part of Pon Pure Chemicals Group is a chemical manufacturing, Supplier & distribution company special…”.

  • Canonical URL set

    The canonical URL is https://www.pure-chemical.com/.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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://pure-chemical.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 (1,915 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix71
  • 2 pages point its canonical at the homepage

    https://pure-chemical.com/careers and https://pure-chemical.com/contact-us 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.

  • 3 pages share a title

    /, https://pure-chemical.com/careers and https://pure-chemical.com/contact-us all use the title “Pure Chemicals Co is the leading chemical supplier and distributor”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://pure-chemical.com/blog has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://pure-chemical.com/careers and https://pure-chemical.com/contact-us use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://pure-chemical.com/contact-us has 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 35 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

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

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    61 of 62 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • A 9-field form

    Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 352 words of copy

    The homepage carries about 352 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More” and “CONTACT US”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact Us” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks, 2 customer or partner logos, 1 trust badge and “over 13,000 customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 19 other companies contacted

    Loading the homepage contacts 19 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 pure-chemical.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
1 open role
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on pure-chemical.com, including 18 speed issues, 6 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

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