Website review, no card needed

culk.co logo

culk.co website review

Visit site (opens in a new tab)Reviewed 7 November 202628 issues · 82 checks

This review found 28 issues worth fixing on culk.co, 7 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
1.6 s951 msMay 16Aug 221.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.4 s
Jul 18, 20261.1 s
Jul 25, 20261.0 s
Aug 1, 20261.1 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
105 ms87 msMay 16Jul 1192 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026103 ms
May 23, 2026103 ms
May 30, 2026102 ms
Jun 6, 2026103 ms
Jun 13, 202696 ms
Jun 20, 202695 ms
Jun 27, 202693 ms
Jul 4, 202689 ms
Jul 11, 202692 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 culk.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. culk.co at 0.4 s0.4 s
  2. culk.co at 0.9 s0.9 s
  3. culk.co at 1.3 s1.3 s
  4. culk.co at 1.7 s1.7 s
  5. culk.co at 2.1 s2.1 s
  6. culk.co at 2.6 s2.6 s
  7. culk.co at 3.0 s3.0 s
  8. culk.co at 3.4 s3.4 s

Speed

5 to fix82
  • Reduce unused JavaScript

    1.7 s · 331 KiB

    About 331 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.

  • Mobile performance score: 82

    82/100

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

  • Render-blocking requests

    800 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • Reduce unused CSS

    300 ms · 42 KiB

    About 42 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.

  • Shopify adds 40 ms

    40 ms

    Shopify costs a phone 40 ms of main-thread work and 333 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.

  • Legacy JavaScript

    150 ms · 17 KiB

    Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, Bugsnag and shop.app), adding 350 KiB and 49 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    40 KiB

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

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

  • Improve image delivery

    4 KiB

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

3 to fix75
  • Largest Contentful Paint: 5.0 s

    5.0 s

    Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Minimal Bridge Tote Cream, I Heart SF Tote Cream, SF Seal T…”.

  • Time to Interactive: 5.0 s

    5.0 s

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -6%

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

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

5 checks passed
  • Tap response (INP) got 12% faster for real visitors

    -12%

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

  • Cumulative Layout Shift: 0.049

    0.049

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

  • Speed Index: 1.5 s

    1.5 s

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

  • Total Blocking Time: 11 ms

    11 ms

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

Images and page weight

100
  • 1 image in older formats

    1 image (41 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 0.4 g of CO₂ per visit

    0.44 g

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

3 checks passed
  • Page weight: 1.6 MB in 162 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 162 requests on a phone: other files 806 KiB (114), scripts 683 KiB (41) and stylesheets 52 KiB (3). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 9291
  • Links look like plain text

    37 links inside paragraphs rely on colour alone to stand out.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 6 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9284
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.culk.co/search?q={search_term_string}")”.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 23 internal links, 37 external

    The homepage links to 23 pages on culk.co and 37 external pages.

6 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Culk is a San Francisco based tee shirt company that produces iconic, urban-inspired tees, tanks, and sweatshirts for w…”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Culk | Commemorating Urban Landmarks Kinda”.

  • Canonical URL set

    The canonical URL is https://www.culk.co/.

  • 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.culk.co/sitemap.xml.

AI search readiness

100
4 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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://www.culk.co/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.culk.co/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://www.culk.co/pages/shop-culk-wholesale, https://www.culk.co/collections/the-culk-archive, https://www.culk.co/pages/custom-merch, https://www.culk.co/customer_authentication/redirect, https://www.culk.co/policies/shipping-policy and https://www.culk.co/policies/refund-policy and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.culk.co/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.culk.co/pages/shop-culk-wholesale, https://www.culk.co/pages/custom-merch and https://www.culk.co/pages/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://www.culk.co/customer_authentication/redirect took over 3 s to send its HTML from our server.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 10 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.

Best practices

1 to fixGoogle 10093
  • 8 small tap targets

    8 of 21 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

4 to fix63
  • 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.

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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,825 words of copy

    The homepage carries about 1,825 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop Culk Wholesale”, “Contact” and “Sign Up”.

  • 4 short forms

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 15 cookies set on arrival

    15

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 culk.co, 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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Forms

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
jQuery
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on culk.co, including 8 speed issues, 3 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