Website review, no card needed

pacsun.com logo

pacsun.com website review

Visit site (opens in a new tab)Reviewed 11 October 202627 issues · 62 checks

This review found 27 issues worth fixing on pacsun.com, 9 of them high impact, across 62 checks. The most urgent: crcldu.com adds 1.9 s. 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.6 s1.9 sApr 18Oct 32.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.2 s
Apr 25, 20262.3 s
May 2, 20262.3 s
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
276 ms224 msApr 18Oct 3269 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026270 ms
Apr 25, 2026259 ms
May 2, 2026246 ms
May 9, 2026238 ms
May 16, 2026232 ms
May 23, 2026230 ms
May 30, 2026232 ms
Jun 6, 2026233 ms
Jun 13, 2026235 ms
Jun 20, 2026237 ms
Jun 27, 2026237 ms
Jul 4, 2026240 ms
Jul 11, 2026237 ms
Jul 18, 2026236 ms
Jul 25, 2026233 ms
Aug 1, 2026231 ms
Aug 8, 2026238 ms
Aug 15, 2026248 ms
Aug 22, 2026260 ms
Aug 29, 2026268 ms
Sep 5, 2026270 ms
Sep 12, 2026265 ms
Sep 19, 2026262 ms
Sep 26, 2026265 ms
Oct 3, 2026269 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 pacsun.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix59
  • crcldu.com adds 1.9 s

    1.9 s

    crcldu.com costs a phone 1.9 s of main-thread work and 219 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.

  • px-cloud.net adds 1.1 s

    1.1 s

    px-cloud.net costs a phone 1.1 s of main-thread work and 333 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.

  • Main-thread work: 7.0 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (crcldu.com, px-cloud.net and PerimeterX Bot Defender and others), adding 637 KiB and 3.0 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 706 KiB

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

  • 19 long tasks on the main thread

    19 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    150 ms · 96 KiB

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

Core Web Vitals

10 to fix33
  • 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.

  • Total Blocking Time: 2.8 s

    2.8 s

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

  • Time to Interactive: 10.8 s

    10.8 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 373 ms

    373 ms

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Press & Hold to confirm you are a human (and not a bot).”.

  • Speed Index: 4.1 s

    4.1 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

2 checks passed
  • Real-user CLS: 0.04

    0.04

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.25 g

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

1 checks passed
  • Page weight: 913 KiB in 20 requests

    913 KiB

    Your homepage downloads 913 KiB in 20 requests on a phone: scripts 811 KiB (4), fonts 75 KiB (2) and other files 15 KiB (9). That is a lean page.

Accessibility

1 to fix85
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • No main landmark

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

1 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

SEO

3 to fixGoogle 9173
  • No H1 headline

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

  • Error status code

    The page answers with an error status, so search engines may drop it.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 433 internal links, 16 external

    The homepage links to 433 pages on pacsun.com and 16 external pages.

6 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Pacsun is the go-to for the latest baggy jeans, hoodies, graphic tees, swimwear, and more. Build your next 'fit, and en…”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Pacsun | Denim, Streetwear, & Everyday Essentials”.

  • Canonical URL set

    The canonical URL is https://www.pacsun.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.pacsun.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.pacsun.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 contact details; description would complete it.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

2 to fixGoogle 7789
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 2 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 18 words

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 116 calls to action

    The homepage has 116 calls to action, for example “SHOP MEN”, “SHOP WOMEN” and “SHOP KIDS”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

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

  • 8 other companies contacted

    Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 pacsun.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on pacsun.com, including 17 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