Website review, no card needed
centralmcgowan.com website review
Visit site (opens in a new tab)Reviewed 22 October 202645 issues · 96 checks
This review found 45 issues worth fixing on centralmcgowan.com, 14 of them high impact, across 96 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
77C- #66,045 of 118,024 reviewed websitesbeats 39%
- #43,038 of 67,072 online storesbeats 31%
- #1,019 of 2,706 WooCommerce storesbeats 57%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 112 ms |
| May 9, 2026 | 112 ms |
| May 16, 2026 | 104 ms |
| May 23, 2026 | 100 ms |
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 102 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 108 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 92 ms |
| Aug 8, 2026 | 91 ms |
| Aug 15, 2026 | 91 ms |
| Aug 22, 2026 | 90 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 101 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 105 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
4.1 s
8.1 s
12.2 s
16.3 s
20.4 s
24.4 s
28.5 s
32.6 s
Speed
Reduce unused JavaScript
10.5 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.5 s faster on a phone.
Improve image delivery
3.5 s · 948 KiB14 images could be 948 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.
Main-thread work: 41.8 s
A phone's processor spends 41.8 s on main-thread work while loading, 11.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
2.1 s35 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 25
25/100Your mobile performance score is 25 (desktop: 51). 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 CDN, Google Tag Manager and YouTube and others), adding 3.4 MB and 2.5 s of main-thread time.
Use efficient cache lifetimes
850 ms · 292 KiB9 files are served with short cache lifetimes, so returning visitors download them again (292 KiB).
Reduce unused CSS
750 ms · 192 KiBAbout 192 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google CDN adds 784 ms
784 msGoogle CDN costs a phone 784 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 644 ms
644 msGoogle Tag Manager costs a phone 644 ms of main-thread work and 736 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.
YouTube adds 569 ms
569 msYouTube costs a phone 569 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 523 ms. During a long task the page ignores taps.
Facebook adds 263 ms
263 msFacebook costs a phone 263 ms of main-thread work and 212 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.
2,135 HTML elements
The page has 2,135 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 51 but mobile only 25. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 8.7 s
8.7 sThe first text or image appears after 8.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 95.5 s
95.5 sYour largest element takes 95.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 27.1 s
27.1 sVisually, the page fills in at 27.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 14.0 s
14.0 sScripts block taps and scrolling for 14.0 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 96.2 s
96.2 sThe page becomes fully interactive after 96.2 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 112 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 19.0 MB in 201 requests
19.0 MBYour homepage downloads 19.0 MB in 201 requests on a phone: images 14.4 MB (72), scripts 3.4 MB (68) and other files 408 KiB (13). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
69 KiB1 image is downloaded at several times the size a phone draws it, for example ColdZERO-Dry-Ice-Icon-1-circle-29b0c39217c8f781d90b3a3c166d9 at 556 px wide, shown at 100 px. Resized copies would save about 69 KiB.
About 5.4 g of CO₂ per visit
5.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.38 g of CO₂e: 646.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
30 text elements with low contrast
30 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
Positive tabindex
13 elements have a tabindex above 0, which scrambles the keyboard order.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail 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.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h5 and h3 → h6), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (8 elements).
2 checks passed
Every image has alt text
All 80 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 9 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
8 H1 headlines
There are 8 <h1> headlines (“BULK & PACKAGED GAS”, “AUTOMATION” and “LIVE TO WELD”). One clear main headline is easier for people and search engines.
15 links with vague text
15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
267 internal links, 16 external
The homepage links to 267 pages on centralmcgowan.com and 16 external pages.
7 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Central McGowan supplies welders, manufacturers, and restaurants with equipment, tools, and gases and installs automati…”.
Title: 64 characters
Your title is a healthy 64 characters: “Central McGowan | Robotics, Welding + Gas, Carbonation Suppliers”.
Canonical URL set
The canonical URL is https://centralmcgowan.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://centralmcgowan.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://centralmcgowan.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,306 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share 2 titles
https://centralmcgowan.com/automation/custom-automation-solutions, https://centralmcgowan.com/automation/standard-robotic-cells and https://centralmcgowan.com/automation/process-and-past-projects all use the title “Central McGowan | Industrial Robots + Automation Equipment Videos”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://centralmcgowan.com/automation/automation-overview, https://centralmcgowan.com/automation/crx-cobot-solutions, https://centralmcgowan.com/automation/automation-101, https://centralmcgowan.com/automation/cnc-plasma-cutting-systems, https://centralmcgowan.com/welding/welding-industrial and https://centralmcgowan.com/gas-products-delivery and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://centralmcgowan.com/automation/custom-automation-solutions, https://centralmcgowan.com/automation/standard-robotic-cells and https://centralmcgowan.com/automation/process-and-past-projects use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://centralmcgowan.com/rental-repair-services/repair-maintenance, whose canonical is https://centralmcgowan.com/services-rental/repair-maintenance. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 pages without an H1
https://centralmcgowan.com/automation/custom-automation-solutions, https://centralmcgowan.com/automation/standard-robotic-cells, https://centralmcgowan.com/automation/crx-cobot-solutions, https://centralmcgowan.com/automation/automation-101, https://centralmcgowan.com/automation/process-and-past-projects and https://centralmcgowan.com/services-rental/repair-maintenance and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://centralmcgowan.com/automation/cnc-plasma-cutting-systems took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 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
28 small tap targets
28 of 38 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.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Unexpected end of input”.
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
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 40 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 10-field form
Your longest form asks for 10 fields (8 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 817 words of copy
The homepage carries about 817 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More Here” and “Join Our Team”.
40 calls to action
The homepage has 40 calls to action, for example “Contact Automation Sales & Service”, “Shop Used Equipment” and “Contact Gas & Industrial Sales”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 1 of them by other companies (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.
20 other companies contacted
Loading the homepage contacts 20 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 centralmcgowan.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on centralmcgowan.com, including 19 speed issues, 2 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.