Website review, no card needed

capsapparel.com logo

capsapparel.com website review

Visit site (opens in a new tab)Reviewed 9 November 202617 issues · 71 checks

This review found 17 issues worth fixing on capsapparel.com, 4 of them high impact, across 71 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
2.5 s757 msMay 23Nov 7964 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.0 s
Jun 20, 20261.8 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.5 s
Oct 3, 20261.3 s
Oct 10, 20261.1 s
Oct 17, 20261.0 s
Oct 24, 2026989 ms
Oct 31, 2026983 ms
Nov 7, 2026964 ms
Real-visitor tap response (INP)75th percentile, phones
411 ms112 msMay 23Nov 7300 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026146 ms
May 30, 2026150 ms
Jun 6, 2026164 ms
Jun 13, 2026186 ms
Jun 20, 2026206 ms
Jun 27, 2026242 ms
Jul 4, 2026259 ms
Jul 11, 2026269 ms
Jul 18, 2026273 ms
Jul 25, 2026271 ms
Aug 1, 2026275 ms
Aug 8, 2026277 ms
Aug 15, 2026330 ms
Aug 22, 2026347 ms
Aug 29, 2026363 ms
Sep 5, 2026376 ms
Sep 12, 2026347 ms
Sep 19, 2026356 ms
Sep 26, 2026347 ms
Oct 3, 2026334 ms
Oct 10, 2026321 ms
Oct 17, 2026308 ms
Oct 24, 2026298 ms
Oct 31, 2026302 ms
Nov 7, 2026300 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 capsapparel.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. capsapparel.com at 0.4 s0.4 s
  2. capsapparel.com at 0.8 s0.8 s
  3. capsapparel.com at 1.1 s1.1 s
  4. capsapparel.com at 1.5 s1.5 s
  5. capsapparel.com at 1.9 s1.9 s
  6. capsapparel.com at 2.3 s2.3 s
  7. capsapparel.com at 2.6 s2.6 s
  8. capsapparel.com at 3.0 s3.0 s

Speed

2 to fix99
  • Render-blocking requests

    1.3 s

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

  • 5,690 HTML elements

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

  • Improve image delivery

    224 KiB

    8 images could be 224 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    150 ms · 32 KiB

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

  • 4 long tasks on the main thread

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, cloudfront.net and Klaviyo and others), adding 314 KiB and 0 ms of main-thread time.

  • Reduce unused CSS

    22 KiB

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

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

3 checks passed
  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 78 ms of it running JavaScript. That is comfortably low.

  • Server response: 59 ms

    59 ms

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

Core Web Vitals

3 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user INP: 233 ms

    233 ms

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

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

    +103%

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

11 checks passed
  • Real-user LCP: 1.0 s

    1.0 s

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

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

    1.0 s

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

  • Real-user TTFB: 646 ms

    646 ms

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

  • Largest content (LCP) got 58% faster for real visitors

    -58%

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

  • Speed Index: 3.3 s

    3.3 s

    Visually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.3 s

    1.3 s

    Your largest element renders in 1.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Total Blocking Time: 44 ms

    44 ms

    Scripts block the page for only 44 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.7 s

    1.7 s

    The page is fully interactive after 1.7 s.

Images and page weight

2 to fix81
  • Page weight: 2.5 MB in 176 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 176 requests on a phone: images 1.8 MB (128), scripts 467 KiB (39) and HTML 86 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1_beb3cccb-b0bd-4eb4-8f27-ed7ceb8291ad.jpg 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).

  • About 0.7 g of CO₂ per visit

    0.70 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.70 g of CO₂e: 84.0 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

2 to fixGoogle 9597
  • 5 images without alt text

    5 images have no alt text, which hurts accessibility and image search.

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 47 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: 47 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 92100
  • 146 internal links, 9 external

    The homepage links to 146 pages on capsapparel.com and 9 external pages.

8 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Caps Apparel is a headwear and lifestyle brand based out of Amsterdam. Discover the latest arrivals and step into the n…”.

  • One H1 headline

    Your main headline reads: “CAPS”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “Character Over Hype. Since 2017”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization 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://capsapparel.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://capsapparel.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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

Other pages

3 to fix88
  • 1 page without a meta description

    https://capsapparel.com/collections/new-in-store has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://capsapparel.com/products/bubu-rescue-cap and https://capsapparel.com/products/suede-bow-cap use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://capsapparel.com/products/brooklyn-1947, https://capsapparel.com/products/brooklyn-ny, https://capsapparel.com/products/bubu-rescue-cap, https://capsapparel.com/collections/best-sellers, https://capsapparel.com/collections/new-in-store and https://capsapparel.com/products/suede-bow-cap and 1 other 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 67 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 6 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • 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 132 words

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop Caps”, “Shop Beanies Trending” and “Shop Buckets”.

  • 11 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 4 trust badges.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 6 cookies set on arrival

    6

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

  • 5 other companies contacted

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

Apps your storefront loads

Multifeeds · Bm Country Blocker Ip Blocker · Bloom Analytics · Klaviyo Email Marketing Sms · Pagefly Ai Page Builder · Elevate Ab Testing · Multi Location Inv · Triplewhale · Zepto Product Personalizer · Inventory Info Theme Exrtensions · Boostymark Regionblock · snapchat.com · loox.io · printful.com · cloudfront.net · zakeke.com · trustpilot.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

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 17 issues on capsapparel.com, including 5 speed issues and 3 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