Website review, no card needed
columbiamachine.com website review
Visit site (opens in a new tab)Reviewed 3 November 202643 issues · 93 checks
This review found 43 issues worth fixing on columbiamachine.com, 19 of them high impact, across 93 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 7.7 s |
| May 23, 2026 | 7.7 s |
| May 30, 2026 | 8.2 s |
| Jun 6, 2026 | 8.2 s |
| Jun 13, 2026 | 8.0 s |
| Jun 20, 2026 | 7.6 s |
| Jun 27, 2026 | 7.1 s |
| Jul 4, 2026 | 6.9 s |
| Jul 11, 2026 | 6.8 s |
| Jul 18, 2026 | 6.9 s |
| Jul 25, 2026 | 7.0 s |
| Aug 1, 2026 | 6.9 s |
| Aug 8, 2026 | 6.8 s |
| Aug 15, 2026 | 6.4 s |
| Aug 22, 2026 | 6.1 s |
| Aug 29, 2026 | 5.8 s |
| Sep 5, 2026 | 5.5 s |
| Sep 12, 2026 | 5.8 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 5.9 s |
| Oct 3, 2026 | 7.2 s |
| Oct 10, 2026 | 8.6 s |
| Oct 17, 2026 | 9.0 s |
| Oct 24, 2026 | 7.7 s |
| Oct 31, 2026 | 7.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 219 ms |
| May 23, 2026 | 223 ms |
| May 30, 2026 | 231 ms |
| Jun 6, 2026 | 257 ms |
| Jun 13, 2026 | 261 ms |
| Jun 20, 2026 | 210 ms |
| Jun 27, 2026 | 205 ms |
| Jul 4, 2026 | 189 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 211 ms |
| Jul 25, 2026 | 232 ms |
| Aug 1, 2026 | 198 ms |
| Aug 8, 2026 | 183 ms |
| Aug 15, 2026 | 172 ms |
| Aug 22, 2026 | 183 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 220 ms |
| Sep 12, 2026 | 212 ms |
| Sep 19, 2026 | 181 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 167 ms |
| Oct 10, 2026 | 165 ms |
| Oct 17, 2026 | 146 ms |
| Oct 24, 2026 | 153 ms |
| Oct 31, 2026 | 153 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.8 s
1.6 s
2.5 s
3.3 s
4.1 s
4.9 s
5.8 s
6.6 s
Speed
Reduce unused JavaScript
4.1 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Render-blocking requests
1.1 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
900 ms · 3.0 MB66 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).
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 2.3 MB and 1.5 s of main-thread time.
Improve image delivery
1.2 MB15 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
YouTube adds 605 ms
605 msYouTube costs a phone 605 ms of main-thread work and 1,017 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 CDN adds 434 ms
434 msGoogle CDN costs a phone 434 ms of main-thread work and 742 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 239 ms
239 msGoogle Tag Manager costs a phone 239 ms of main-thread work and 323 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.
Reduce unused CSS
260 ms · 192 KiBAbout 192 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 260 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 246 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 43 KiB43 KiB could be saved by minifying JavaScript.
Minify CSS
8 KiB8 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.
1 checks passed
Server response: 18 ms
18 msYour server sent the HTML in 18 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: 7.0 s
7.0 sReal visitors wait 7.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 6.2 s
6.2 sReal visitors see the first content after 6.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.4 s
5.4 sReal visitors wait 5.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 8.6 s
8.6 sThe first text or image appears after 8.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “RUGGEDLY BUILT, PRECISELY ENGINEERED”.
Time to Interactive: 23.4 s
23.4 sThe page becomes fully interactive after 23.4 s. Good is under 3.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 363 ms
363 msScripts block taps and scrolling for 363 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 7.7 s to 7.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 153 ms
153 msReal visitors wait 153 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Tap response (INP) got 31% faster for real visitors
-31%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 219 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.095
0.095The layout barely moves while loading (CLS 0.095, good is under 0.1).
Images and page weight
Page weight: 14.2 MB in 109 requests
14.2 MBYour homepage downloads 14.2 MB in 109 requests on a phone: images 7.1 MB (44), media 4.1 MB (1) and scripts 2.2 MB (30). Under 2 MB keeps phones on slow connections fast.
33 images in older formats
33 images (7.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.
8 images below the first screen load straight away
8 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.0 g of CO₂ per visit
4.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.01 g of CO₂e: 481.3 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
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
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.
32 images without alt text
32 images have no alt text, which hurts accessibility and image search.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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 (h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
76 internal links, 9 external
The homepage links to 76 pages on columbiamachine.com and 9 external pages.
7 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Worldwide leader in design, manufacturing, and support of concrete product machines and solutions including batchers, m…”.
One H1 headline
Your main headline reads: “Ruggedly built, precisely engineered”.
Title: 58 characters
Your title is a healthy 58 characters: “Concrete Product Machines and Solutions - Columbia Machine”.
Structured data in place
Structured data found: BreadcrumbList, 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://columbiamachine.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://columbiamachine.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 (647 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://columbiamachine.com/blog is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages share a title
/, https://columbiamachine.com/br and https://columbiamachine.com/es all use the title “Concrete Product Machines and Solutions - Columbia Machine”. 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://columbiamachine.com/blog has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://columbiamachine.com/br and https://columbiamachine.com/es use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
4 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 an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187187072&tm=gtm002&Ver=2&mid=b32af31b-1c17-4cac-8850-d0336799c39c&bo=1&sid=4dc7c950d71b11f1aee331bae2140d22&vid=4dc7cf20d71b11f183317d3d6dc56668&vids=1&msclkid=N&pi=9.
25 small tap targets
25 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 “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 402 words of copy
The homepage carries about 402 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: “Order Parts Online” and “We Are Hiring - Learn More Here”.
4 calls to action
The homepage has 4 calls to action, for example “Order parts online”, “We Are Hiring - Learn More Here” and “Get In Touch”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Yandex Metrica (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
15 other companies contacted
Loading the homepage contacts 15 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 columbiamachine.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 Tag Manager
- Hosting
- Sucuri
Company
- Founded
- 1937
- Headquarters
- Vancouver
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 columbiamachine.com, including 20 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.