Website review, no card needed
colorfastapparel.com website review
Visit site (opens in a new tab)Reviewed 10 November 202639 issues · 81 checks
This review found 39 issues worth fixing on colorfastapparel.com, 11 of them high impact, across 81 checks. The most urgent: page weight: 10.3 MB in 407 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
83B- #27,558 of 120,620 reviewed websitesbeats 72%
- #18,141 of 68,290 online storesbeats 67%
- #17,583 of 62,230 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 131 ms |
| Aug 15, 2026 | 133 ms |
| Aug 22, 2026 | 136 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 163 ms |
| Oct 31, 2026 | 159 ms |
| Nov 7, 2026 | 162 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
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.6 s
7.6 s
8.7 s
Speed
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
400 ms · 1.2 MB6 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and tidio.co and others), adding 3.4 MB and 781 ms of main-thread time.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused JavaScript
300 ms · 252 KiBAbout 252 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 257 ms
257 msShopify costs a phone 257 ms of main-thread work and 2.4 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.
Reduce unused CSS
300 ms · 83 KiBAbout 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Klaviyo adds 234 ms
234 msKlaviyo costs a phone 234 ms of main-thread work and 384 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.
tidio.co adds 168 ms
168 mstidio.co costs a phone 168 ms of main-thread work and 515 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,739 HTML elements
The page has 1,739 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
40 KiB11 files are served with short cache lifetimes, so returning visitors download them again (40 KiB).
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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 23.9 s
23.9 sThe page becomes fully interactive after 23.9 s. Good is under 3.8 s.
Largest Contentful Paint: 7.8 s
7.8 sYour largest element takes 7.8 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: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 127 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
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
+9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 141 ms
141 msReal visitors wait 141 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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 415 ms
415 msReal visitors wait 415 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 127 ms
127 msScripts block the page for only 127 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 10.3 MB in 407 requests
10.3 MBYour homepage downloads 10.3 MB in 407 requests on a phone: media 4.5 MB (4), images 2.9 MB (36) and scripts 1.3 MB (178). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
CF_Drop_4_561_popup.webp weighs 952 KiB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
597 KiB2 images are downloaded at several times the size a phone draws them, for example CF_Drop_4_561_popup.webp at 1,600 px wide, shown at 400 px. Resized copies would save about 597 KiB.
2 images in older formats
2 images (1.3 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.
2 images below the first screen load straight away
2 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.9 g of CO₂ per visit
2.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.91 g of CO₂e: 348.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
7 elements hidden from screen readers can still receive keyboard focus.
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.
9 links without text
9 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 skip levels
Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 95 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (286 characters)
Your meta description is 286 characters; Google truncates after about 160, so the end of your pitch is cut.
164 internal links, 6 external
The homepage links to 164 pages on colorfastapparel.com and 6 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Colorfast Shop”.
Title: 34 characters
Your title is a healthy 34 characters: “Colorfast Apparel – Colorfast Shop”.
Canonical URL set
The canonical URL is https://colorfastapparel.com/.
Structured data in place
Structured data found: Organization.
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://colorfastapparel.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
llms.txt published
The site publishes https://colorfastapparel.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without a meta description
https://colorfastapparel.com/collections/d2c-crewnecks, https://colorfastapparel.com/collections/jackets, https://colorfastapparel.com/pages/lookbooks, https://colorfastapparel.com/pages/create-an-account, https://colorfastapparel.com/pages/size-chart and https://colorfastapparel.com/pages/custom-dye-program-policies and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://colorfastapparel.com/collections/d2c-tees, https://colorfastapparel.com/collections/d2c-hoodies, https://colorfastapparel.com/collections/d2c-bottoms, https://colorfastapparel.com/collections/d2c-crewnecks, https://colorfastapparel.com/collections/jackets and https://colorfastapparel.com/collections/d2c-all-styles and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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
71 small tap targets
71 of 92 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
1 checks passed
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 138 words
The homepage has only about 138 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Shop as Business”, “SIGN UP” and “Track My Order”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
32 other companies contacted
Loading the homepage contacts 32 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 colorfastapparel.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Klaviyo Email Marketing Sms · Wsh Wholesale Pricing · Kaching Bundles · Judge Me Reviews · webmarked.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on colorfastapparel.com, including 17 speed issues, 1 SEO issue 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.