Website review, no card needed

crcindustries.com logo

crcindustries.com website review

Visit site (opens in a new tab)Reviewed 27 October 202640 issues · 94 checks

This review found 40 issues worth fixing on crcindustries.com, 20 of them high impact, across 94 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

Real-visitor load time (LCP)75th percentile, phones
2.9 s2.2 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.6 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.4 s
Jul 18, 20262.5 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.7 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
116 ms88 msMay 9Oct 2491 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026111 ms
May 16, 2026111 ms
May 23, 2026113 ms
May 30, 2026112 ms
Jun 6, 2026108 ms
Jun 13, 2026106 ms
Jun 20, 2026100 ms
Jun 27, 202698 ms
Jul 4, 202696 ms
Jul 11, 202695 ms
Jul 18, 202695 ms
Jul 25, 202695 ms
Aug 1, 202694 ms
Aug 8, 202694 ms
Aug 15, 202693 ms
Aug 22, 202692 ms
Aug 29, 202691 ms
Sep 5, 202694 ms
Sep 12, 202695 ms
Sep 19, 202695 ms
Sep 26, 202696 ms
Oct 3, 202693 ms
Oct 10, 202694 ms
Oct 17, 202694 ms
Oct 24, 202691 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 crcindustries.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crcindustries.com at 1.0 s1.0 s
  2. crcindustries.com at 2.0 s2.0 s
  3. crcindustries.com at 3.0 s3.0 s
  4. crcindustries.com at 4.0 s4.0 s
  5. crcindustries.com at 5.0 s5.0 s
  6. crcindustries.com at 6.0 s6.0 s
  7. crcindustries.com at 7.0 s7.0 s
  8. crcindustries.com at 8.0 s8.0 s

Speed

12 to fix31
  • Reduce unused JavaScript

    21.6 s · 2.9 MB

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

  • Use efficient cache lifetimes

    1.1 s · 3.8 MB

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

  • Reduce unused CSS

    3.0 s · 516 KiB

    About 516 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • Render-blocking requests

    3.0 s

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

  • YouTube adds 1.6 s

    1.6 s

    YouTube costs a phone 1.6 s of main-thread work and 3.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 10.9 s

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

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31 (desktop: 39). 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 (YouTube, Google CDN and Google Tag Manager and others), adding 5.8 MB and 3.1 s of main-thread time.

  • Google CDN adds 638 ms

    638 ms

    Google CDN costs a phone 638 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.

  • Google Tag Manager adds 477 ms

    477 ms

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

  • Minify JavaScript

    450 ms · 48 KiB

    48 KiB could be saved by minifying JavaScript.

  • 20 long tasks on the main thread

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

  • Improve image delivery

    18 KiB

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

  • 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: 4 ms

    4 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • First Contentful Paint: 21.4 s

    21.4 s

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

  • Largest Contentful Paint: 46.7 s

    46.7 s

    Your largest element takes 46.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 21.4 s

    21.4 s

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

  • Time to Interactive: 49.8 s

    49.8 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user CLS: 0.11

    0.11

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

  • 15 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

5 checks passed
  • Real-user INP: 103 ms

    103 ms

    Real visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 686 ms

    686 ms

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

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

    -17%

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

  • Cumulative Layout Shift: 0.058

    0.058

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

Images and page weight

1 to fix70
  • Page weight: 12.4 MB in 446 requests

    12.4 MB

    Your homepage downloads 12.4 MB in 446 requests on a phone: scripts 5.7 MB (282), media 3.6 MB (2) and images 1.3 MB (64). Under 2 MB keeps phones on slow connections fast.

  • About 3.5 g of CO₂ per visit

    3.50 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.50 g of CO₂e: 420.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

9 to fixGoogle 7388
  • Certain ARIA roles must be contained by particular parents (8 elements)

    Certain ARIA roles must be contained by particular parents: 8 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • 2 text elements with low contrast

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 12 links without text

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

  • 3 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 9 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 8595
  • 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.

  • 4 links with vague text

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

  • 125 internal links, 42 external

    The homepage links to 125 pages on crcindustries.com and 42 external pages.

7 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “CRC manufactures over 1300 chemical MRO products for Automotive, Marine, Mining, Oil & Gas, Hardware, Electrical, Indus…”.

  • One H1 headline

    Your main headline reads: “CRC Industries has the Perfect Solution for Your Next Project”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “CRC Industries | Global Supplier of Chemical MRO Products”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and Store.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

100
  • No llms.txt

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

3 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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5076
  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 5 small tap targets

    5 of 23 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.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “eapps.Platform throws: "Widget "ecf2c04e-32a9-41b5-ad75-a727bdb1c857" can`t be initialized because WIDGET_DISABLED" wit…”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • 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

2 to fix81
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

    Social proof on the homepage: 14 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • About 765 words of copy

    The homepage carries about 765 words of visible text.

6 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “CONTACT”, “GENERAL CONTACT” and “Join Now”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 4 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 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). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

  • 28 other companies contacted

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

1 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) 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 crcindustries.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
E-commerce
Magento
Analytics
Google Tag Manager
Hosting
Nexcess Net

Company

Employees
314
Founded
1958

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on crcindustries.com, including 21 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