Website review, no card needed
cmx1.com website review
Visit site (opens in a new tab)Reviewed 25 October 202631 issues · 90 checks
This review found 31 issues worth fixing on cmx1.com, 8 of them high impact, across 90 checks. The most urgent: render-blocking requests. 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 134 ms |
| May 9, 2026 | 136 ms |
| May 16, 2026 | 104 ms |
| May 23, 2026 | 117 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 105 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 110 ms |
| Jul 11, 2026 | 106 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 101 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 105 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 117 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
Speed
Render-blocking requests
1.8 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and Facebook and others), adding 1.6 MB and 1.5 s of main-thread time.
Improve image delivery
250 ms · 934 KiB8 images could be 934 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70 (desktop: 67). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
100 ms · 702 KiB141 files are served with short cache lifetimes, so returning visitors download them again (702 KiB).
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 584 ms. During a long task the page ignores taps.
Reduce unused JavaScript
560 KiBAbout 560 KiB of JavaScript is downloaded but never used on this page.
hsappstatic.net adds 489 ms
489 mshsappstatic.net costs a phone 489 ms of main-thread work and 702 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 427 ms
427 msGoogle Tag Manager costs a phone 427 ms of main-thread work and 379 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.
1,790 HTML elements
The page has 1,790 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 22.3 s
22.3 sThe page becomes fully interactive after 22.3 s. Good is under 3.8 s.
Total Blocking Time: 617 ms
617 msScripts block taps and scrolling for 617 ms in total while the page loads. Good is under 200 ms.
37 images without width and height
37 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “chef_and_sous_chef”.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 105 ms
105 msReal visitors wait 105 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 772 ms
772 msReal visitors wait 772 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 134 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.061
0.061The layout barely moves while loading (CLS 0.061, good is under 0.1).
Images and page weight
Page weight: 3.5 MB in 270 requests
3.5 MBYour homepage downloads 3.5 MB in 270 requests on a phone: scripts 1.8 MB (65), images 1.2 MB (85) and fonts 142 KiB (6). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
chef_and_sous_chef.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image below the first screen load straight away
1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 120.5 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 buttons without a name
10 buttons have no accessible name, so screen readers announce just “button”.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
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 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 120 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
191 internal links, 11 external
The homepage links to 191 pages on cmx1.com and 11 external pages.
8 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “Enterprise software that simplifies safety compliance across restaurants, hospitality, and food manufacturing.”.
One H1 headline
Your main headline reads: “One powerful platform. Effortless compliance.”.
Title: 53 characters
Your title is a healthy 53 characters: “CMX1 | One platform for Quality, Risk, and Compliance”.
Canonical URL set
The canonical URL is https://www.cmx1.com/.
Structured data in place
Structured data found: LocalBusiness.
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://www.cmx1.com/sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,228 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.cmx1.com/llms.txt (11 KiB, 72 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.cmx1.com/resources/demo-old is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.
6 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.
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=97225711&tm=gtm002&Ver=2&mid=f3c7481c-b1e3-46b6-8c40-19126c38771c&bo=1&sid=c37b41d0d04b11f1a57ecd438596234b&vid=c37b4760d04b11f1a2431748978c6318&vids=1&msclkid=N&pi=91.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
47 of 53 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 1,176 words of copy
The homepage carries about 1,176 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “GET A DEMO”.
9 calls to action
The homepage has 9 calls to action, for example “Request a Demo ›”, “Contact us” and “Request Demo”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and 31 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Opening hours shown
Your opening hours are on the homepage.
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.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
21 cookies set on arrival
21Opening the homepage sets 21 cookies (measured from a US location before any click).
47 other companies contacted
Loading the homepage contacts 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 cmx1.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on cmx1.com, including 17 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.