Website review, no card needed

cottoncitizen.com logo

cottoncitizen.com website review

Visit site (opens in a new tab)Reviewed 19 November 202638 issues · 83 checks

This review found 38 issues worth fixing on cottoncitizen.com, 12 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.6 s1.2 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 6, 20261.8 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.4 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20263.0 s
Aug 8, 20262.7 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.8 s
Sep 19, 20263.0 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20262.9 s
Oct 24, 20262.7 s
Oct 31, 20262.6 s
Nov 7, 20262.4 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
132 ms72 msMay 30Nov 14112 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202679 ms
Jun 6, 202687 ms
Jun 13, 202688 ms
Jun 20, 202693 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202694 ms
Aug 22, 202696 ms
Aug 29, 202699 ms
Sep 5, 2026103 ms
Sep 12, 2026105 ms
Sep 19, 2026111 ms
Sep 26, 2026114 ms
Oct 3, 2026122 ms
Oct 10, 2026125 ms
Oct 17, 2026119 ms
Oct 24, 2026114 ms
Oct 31, 2026112 ms
Nov 7, 2026111 ms
Nov 14, 2026112 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

Full-page screenshot of cottoncitizen.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cottoncitizen.com at 1.5 s1.5 s
  2. cottoncitizen.com at 3.1 s3.1 s
  3. cottoncitizen.com at 4.6 s4.6 s
  4. cottoncitizen.com at 6.1 s6.1 s
  5. cottoncitizen.com at 7.7 s7.7 s
  6. cottoncitizen.com at 9.2 s9.2 s
  7. cottoncitizen.com at 10.7 s10.7 s
  8. cottoncitizen.com at 12.3 s12.3 s

Speed

9 to fix62
  • Render-blocking requests

    1.4 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Main-thread work: 4.3 s

    A phone's processor spends 4.3 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (rebuyengine.com, Shopify and Klaviyo and others), adding 3.5 MB and 608 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 473 KiB

    About 473 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Shopify adds 184 ms

    184 ms

    Shopify costs a phone 184 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.

  • rebuyengine.com adds 192 ms

    192 ms

    rebuyengine.com costs a phone 192 ms of main-thread work and 505 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.

  • 2,170 HTML elements

    The page has 2,170 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Klaviyo adds 128 ms

    128 ms

    Klaviyo costs a phone 128 ms of main-thread work and 343 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.

  • Use efficient cache lifetimes

    150 ms · 63 KiB

    13 files are served with short cache lifetimes, so returning visitors download them again (63 KiB).

  • 8 long tasks on the main thread

    8 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.

  • Minify JavaScript

    150 ms · 7 KiB

    7 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    48 KiB

    Polyfills for old browsers add 48 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    18 KiB

    About 18 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    15 KiB

    1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • Speed Index: 12.6 s

    12.6 s

    Visually, the page fills in at 12.6 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 16.4 s

    16.4 s

    The page becomes fully interactive after 16.4 s. Good is under 3.8 s.

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (7.4 s).

  • Tap response (INP) got 34% slower for real visitors

    +34%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 79 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 46% slower for real visitors

    +46%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

  • Total Blocking Time: 212 ms

    212 ms

    Scripts block taps and scrolling for 212 ms in total while the page loads. Good is under 200 ms.

7 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 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 106 ms

    106 ms

    Real visitors wait 106 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 634 ms

    634 ms

    Real visitors wait 634 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.073

    0.073

    The layout barely moves while loading (CLS 0.073, good is under 0.1).

Images and page weight

4 to fix52
  • Page weight: 6.6 MB in 464 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 464 requests on a phone: images 4.1 MB (217), scripts 1.3 MB (88) and other files 885 KiB (130). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    11.5-HP_mobile1_edited_copy.avif 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).

  • 16 images below the first screen load straight away

    16 images further down the page (734 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images far larger than shown

    349 KiB

    5 images are downloaded at several times the size a phone draws them, for example ec.svg at 1,440 px wide, shown at 24 px. Resized copies would save about 349 KiB.

  • 1 image in older formats

    1 image (74 KiB) is 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.

  • About 1.9 g of CO₂ per visit

    1.86 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.86 g of CO₂e: 223.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fixGoogle 7889
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 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.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious 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.

2 checks passed
  • Every image has alt text

    All 7 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 4 H1 headlines

    There are 4 <h1> headlines (“The Holiday 2026 Collection”, “The Womenswear Collection” and “The Menswear Collection”). One clear main headline is easier for people and search engines.

  • 100 internal links, 8 external

    The homepage links to 100 pages on cottoncitizen.com and 8 external pages.

6 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Born in a premiere Los Angeles denim dye house, COTTONCITIZEN was formed from the desire to bring the world premium gar…”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “COTTONCITIZEN – Cotton Citizen”.

  • Canonical URL set

    The canonical URL is https://cottoncitizen.com/.

  • 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://cottoncitizen.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (325 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://cottoncitizen.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://cottoncitizen.com/pages/womens-homepage, https://cottoncitizen.com/pages/womens-campaign, https://cottoncitizen.com/collections/womens-loungewear, https://cottoncitizen.com/collections/womens-trousers and https://cottoncitizen.com/pages/mens-homepage have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://cottoncitizen.com/collections/womens-new-arrivals, https://cottoncitizen.com/collections/womens-bestsellers, https://cottoncitizen.com/collections/women-tanks, https://cottoncitizen.com/collections/womens-t-shirts, https://cottoncitizen.com/collections/women-shirts and https://cottoncitizen.com/collections/womens-loungewear and 3 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 46 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

2 to fixGoogle 9687
  • 13 small tap targets

    13 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 JavaScript errors while loading

    5 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 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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 176 words

    The homepage has only about 176 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.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Women's” and “Shop Men's”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “Shop The Campaign”, “Shop All 277” and “Shop All 206”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 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.

  • 53 other companies contacted

    Loading the homepage contacts 53 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 cottoncitizen.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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Queen One Formerly Rejoiner · Loop Returns · locationinventory.info · b-cdn.net · shareasale.com · sesami.co · rebuyengine.com

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

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

Hiring

Hiring
2 open roles
Job board
careers page

Company

Headquarters
Los Angeles

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on cottoncitizen.com, including 16 speed issues, 2 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25