Website review, no card needed
ccl-techlogix.com website review
Visit site (opens in a new tab)Reviewed 21 October 202627 issues · 75 checks
This review found 27 issues worth fixing on ccl-techlogix.com, 11 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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
78CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
Use efficient cache lifetimes
2.6 s · 680 KiB45 files are served with short cache lifetimes, so returning visitors download them again (680 KiB).
Improve image delivery
1.0 s · 173 KiB2 images could be 173 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 74). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
750 ms · 151 KiBAbout 151 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
750 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
7 third-party services on the page
7 third-party services load with your homepage (Google Maps, Hubspot and Cloudflare CDN and others), adding 642 KiB and 433 ms of main-thread time.
Reduce unused CSS
150 ms · 18 KiBAbout 18 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.
Minify CSS
150 ms · 5 KiB5 KiB could be saved by minifying CSS.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 74 but mobile only 44. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 726 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.4 s
22.4 sYour largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Turn logistics complexity into control, cost wins and bette…”.
Time to Interactive: 22.6 s
22.6 sThe page becomes fully interactive after 22.6 s. Good is under 3.8 s.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.245
0.245The layout shifts by 0.245 while loading, so content jumps under the reader's thumb. Good is under 0.1.
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Total Blocking Time: 95 ms
95 msScripts block the page for only 95 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.2 MB in 79 requests
5.2 MBYour homepage downloads 5.2 MB in 79 requests on a phone: images 4.4 MB (26), scripts 534 KiB (27) and fonts 275 KiB (8). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.
14 images in older formats
14 images (2.6 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.
14 images below the first screen load straight away
14 images further down the page (722 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images far larger than shown
170 KiB6 images are downloaded at several times the size a phone draws them, for example swagelok.png at 500 px wide, shown at 138 px. Resized copies would save about 170 KiB.
About 1.5 g of CO₂ per visit
1.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 178.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
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.
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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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, so links shared on LinkedIn, Slack or Facebook show no preview picture.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
66 internal links, 2 external
The homepage links to 66 pages on ccl-techlogix.com and 2 external pages.
6 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Transform your logistics with CCL's Managed 4PL, enabling control, cost savings, and superior customer service tailored…”.
One H1 headline
Your main headline reads: “Turn logistics complexity into control, cost wins and better customer service.”.
Title: 53 characters
Your title is a healthy 53 characters: “Managed 4PL & Supply Chain Technology | CCL Techlogix”.
Canonical URL set
The canonical URL is https://ccl-techlogix.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://ccl-techlogix.com/sitemap.xml.
AI search readiness
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://ccl-techlogix.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,094 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 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
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
10 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,002 words of copy
The homepage carries about 1,002 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: “Get your complimentary copy →”.
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Get your complimentary copy →” and “Learn more”.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and 15 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads HubSpot (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
18 other companies contacted
Loading the homepage contacts 18 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 ccl-techlogix.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on ccl-techlogix.com, including 11 speed issues and 4 SEO issues. 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.