Website review, no card needed
cclcolossal.com website review
Visit site (opens in a new tab)Reviewed 18 October 202640 issues · 80 checks
This review found 40 issues worth fixing on cclcolossal.com, 20 of them high impact, across 80 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
61D- #113,316 of 117,105 reviewed websitesbeats 3%
- #66,050 of 66,867 online storesbeats 1%
- #2,610 of 2,688 WooCommerce storesbeats 2%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.6 s
3.2 s
4.8 s
6.4 s
8.1 s
9.7 s
11.3 s
12.9 s
Speed
Use efficient cache lifetimes
11.6 s · 7.4 MB117 files are served with short cache lifetimes, so returning visitors download them again (7.4 MB).
Improve image delivery
7.8 s · 2.8 MB7 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.8 s faster on a phone.
Reduce unused JavaScript
4.8 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.8 s faster on a phone.
Render-blocking requests
4.0 s55 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 895 KiB 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.
Mobile performance score: 13
13/100Your mobile performance score is 13 (desktop: 34). 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, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Google Maps and Clarity and others), adding 1.6 MB and 1.5 s of main-thread time.
Reduce unused CSS
900 ms · 147 KiBAbout 147 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Font display
600 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).
Google Maps adds 340 ms
340 msGoogle Maps costs a phone 340 ms of main-thread work and 465 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
300 ms · 23 KiB23 KiB could be saved by minifying JavaScript.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 230 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 8 KiB8 KiB could be saved by minifying CSS.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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: 222 ms
222 msYour server sent the HTML in 222 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 29.6 s
29.6 sYour largest element takes 29.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 17.8 s
17.8 sVisually, the page fills in at 17.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 29.9 s
29.9 sThe page becomes fully interactive after 29.9 s. Good is under 3.8 s.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.6
0.6The layout shifts by 0.6 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 891 ms
891 msScripts block taps and scrolling for 891 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.
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.
Images and page weight
Page weight: 9.0 MB in 164 requests
9.0 MBYour homepage downloads 9.0 MB in 164 requests on a phone: images 6.5 MB (17), scripts 1.6 MB (70) and fonts 471 KiB (11). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.
7 images in older formats
7 images (3.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.
4 images below the first screen load straight away
4 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
368 KiB1 image is downloaded at several times the size a phone draws it, for example scientist-mixing-chemical-elements-scaled.jpg at 2,560 px wide, shown at 414 px. Resized copies would save about 368 KiB.
About 2.5 g of CO₂ per visit
2.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.54 g of CO₂e: 304.9 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.
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.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
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.
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Colossal International : Specialty Chemical Distributor Thailand |”.
Meta description is long (172 characters)
Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
93 internal links, 0 external
The homepage links to 93 pages on cclcolossal.com and 0 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Specialty Chemical Distributor in Thailand”.
Canonical URL set
The canonical URL is https://www.cclcolossal.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://www.cclcolossal.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.cclcolossal.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.
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.
Other pages
6 pages slow to respond
https://www.cclcolossal.com/paints_ga, https://www.cclcolossal.com/plastics-construction, https://www.cclcolossal.com/rubber-ia, https://www.cclcolossal.com/food-basic-chemicals, https://www.cclcolossal.com/pharmaceuticals and https://www.cclcolossal.com/cosmetics took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 92 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 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
Thin social proof
Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
Only about 148 words
The homepage has only about 148 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “JOIN US!” and “CONTACT”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
13 other companies contacted
Loading the homepage contacts 13 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 cclcolossal.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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
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 cclcolossal.com, including 19 speed issues, 3 SEO issues and 5 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.