Website review, no card needed

saintfranciscampusstore.com logo

saintfranciscampusstore.com website review

Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 78 checks

This review found 34 issues worth fixing on saintfranciscampusstore.com, 14 of them high impact, across 78 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.0 s600 msAug 29Sep 19976 ms
Show as table
DateReal-visitor load time (LCP)
Aug 29, 2026649 ms
Sep 5, 2026675 ms
Sep 12, 2026726 ms
Sep 19, 2026976 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 saintfranciscampusstore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. saintfranciscampusstore.com at 0.7 s0.7 s
  2. saintfranciscampusstore.com at 1.5 s1.5 s
  3. saintfranciscampusstore.com at 2.2 s2.2 s
  4. saintfranciscampusstore.com at 2.9 s2.9 s
  5. saintfranciscampusstore.com at 3.7 s3.7 s
  6. saintfranciscampusstore.com at 4.4 s4.4 s
  7. saintfranciscampusstore.com at 5.1 s5.1 s
  8. saintfranciscampusstore.com at 5.8 s5.8 s

Speed

11 to fix28
  • Reduce unused JavaScript

    2.3 s · 860 KiB

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

  • hcaptcha.com adds 1.7 s

    1.7 s

    hcaptcha.com costs a phone 1.7 s of main-thread work and 1.2 MB 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.

  • Mobile performance score: 28

    28/100

    Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (hcaptcha.com, hsappstatic.net and Shopify and others), adding 3.3 MB and 3.0 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 263 KiB

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

  • Improve image delivery

    600 ms · 175 KiB

    4 images could be 175 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • hsappstatic.net adds 498 ms

    498 ms

    hsappstatic.net costs a phone 498 ms of main-thread work and 716 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.

  • 20 long tasks on the main thread

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

  • Shopify adds 356 ms

    356 ms

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

  • Render-blocking requests

    300 ms

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

  • Reduce unused CSS

    150 ms · 60 KiB

    About 60 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    59 KiB

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix37
  • First Contentful Paint: 9.0 s

    9.0 s

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

  • Largest Contentful Paint: 15.4 s

    15.4 s

    Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 29.9 s

    29.9 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

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

    +29%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.6 s to 1.0 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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.7 MB in 362 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 362 requests on a phone: scripts 2.8 MB (187), other files 749 KiB (114) and HTML 506 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.32 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

5 to fixGoogle 9492
  • 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.

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (6 elements)

    All page content should be contained by landmarks: 6 elements on the page fail 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.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10074
  • No H1 headline

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

  • Title is long (102 characters)

    Your title is 102 characters, so Google will cut it off around 60: “Saint Francis Campus Store | Official Apparel, Gear & Merch – University of Saint Francis…”.

  • Meta description is long (232 characters)

    Your meta description is 232 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No robots.txt

    There is no robots.txt at saintfranciscampusstore.com/robots.txt, the first file search crawlers ask for.

  • 90 internal links, 6 external

    The homepage links to 90 pages on saintfranciscampusstore.com and 6 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://saintfranciscampusstore.com/sitemap.xml.

AI search readiness

100
2 checks passed
  • 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.

  • llms.txt published

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

Other pages

1 to fix95
  • 15 pages without a meta description

    https://saintfranciscampusstore.com/collections/mens-tshirts, https://saintfranciscampusstore.com/collections/mens-sweatshirts, https://saintfranciscampusstore.com/collections/mens-tops, https://saintfranciscampusstore.com/collections/mens-bottoms, https://saintfranciscampusstore.com/collections/mens-professional-wear and https://saintfranciscampusstore.com/collections/mens-outerwear and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 7397
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    12 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix70
  • 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.

  • 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 119 words

    The homepage has only about 119 words of visible text; thin pages give Google and first-time buyers little to go on.

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START SHOPPING”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop Now”, “SHOP BEST SELLERS” and “Start Shopping”.

  • 1 short form

    A short form (1 field at most) is 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

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 4 of them by other companies (measured from a US location before any click).

  • 16 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Local Pickup;Shopify Plus;Shopify POS
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on saintfranciscampusstore.com, including 17 speed issues, 4 SEO issues 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

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