Programmable

Website review, no card needed

publicrec.com logo

publicrec.com website review

Visit site (opens in a new tab)Reviewed 11 November 202623 issues · 60 checks

This review found 23 issues worth fixing on publicrec.com, 9 of them high impact, across 60 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
3.4 s2.1 sMay 23Nov 73.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.4 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.5 s
Jul 11, 20262.7 s
Jul 18, 20262.8 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20263.0 s
Oct 31, 20263.2 s
Nov 7, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
265 ms177 msMay 23Nov 7213 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026244 ms
May 30, 2026246 ms
Jun 6, 2026252 ms
Jun 13, 2026254 ms
Jun 20, 2026255 ms
Jun 27, 2026254 ms
Jul 4, 2026237 ms
Jul 11, 2026222 ms
Jul 18, 2026212 ms
Jul 25, 2026204 ms
Aug 1, 2026198 ms
Aug 8, 2026196 ms
Aug 15, 2026193 ms
Aug 22, 2026194 ms
Aug 29, 2026195 ms
Sep 5, 2026196 ms
Sep 12, 2026196 ms
Sep 19, 2026195 ms
Sep 26, 2026190 ms
Oct 3, 2026187 ms
Oct 10, 2026187 ms
Oct 17, 2026188 ms
Oct 24, 2026196 ms
Oct 31, 2026205 ms
Nov 7, 2026213 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

nobullproject.com (opens in a new tab)

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

5 to fix33

  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user INP: 213 ms

    213 ms

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

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

    +36%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

3 checks passed

  • Real-user CLS: 0.09

    0.09

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

  • Real-user TTFB: 527 ms

    527 ms

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

  • Tap response (INP) got 15% faster for real visitors

    -15%

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

Images and page weight

2 to fix50

  • Page weight: 7.2 MB

    7.2 MB

    Your homepage downloads 7.2 MB on a phone, 2.0 MB of it images (28%). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    667 KiB

    8 images are downloaded at several times the size a phone draws them, for example Dealmaker_5-Pocket_Pant_d84cccbc-216c-44cc-bf32-2dc3c4390477 at 800 px wide, shown at 114 px. Resized copies would save about 667 KiB.

  • About 2.0 g of CO₂ per visit

    2.05 g

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

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

Accessibility

8 to fix87

  • Certain ARIA roles must contain particular children (6 elements)

    Certain ARIA roles must contain particular children: 6 elements on the page fail this check, rated critical by axe-core.

  • 62 tap targets too small

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

  • Elements must only use permitted ARIA attributes (38 elements)

    Elements must only use permitted ARIA attributes: 38 elements on the page fail this check, rated serious by axe-core.

  • 30 text elements with low contrast

    30 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (10 elements)

    Scrollable region must have keyboard access: 10 elements on the page fail this check, rated serious by axe-core.

  • 20 images without alt text

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

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

    All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.

  • 48 form fields without a label

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

  • Headings skip levels

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

1 checks passed

  • 45 automated accessibility rules passed

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

SEO

100

  • 329 internal links, 0 external

    The homepage links to 329 pages on publicrec.com and 0 external pages.

8 checks passed

  • Meta description: 145 characters

    Your meta description is 145 characters: “NOBULL Public Rec Pants combine premium comfort, athletic performance, and everyday versatility in a streamlined fit de…”.

  • One H1 headline

    Your main headline reads: “Collection: Men's Lifestyle Collection”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Men's Lifestyle Collection – NOBULL”.

  • Canonical URL set

    The canonical URL is https://nobullproject.com/collections/public-rec.

  • Structured data in place

    Structured data found: WebPage.

  • 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://nobullproject.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 (2,011 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90

  • 7 pages without a meta description

    https://nobullproject.com/products/nobull-performance-hat-black, https://nobullproject.com/collections/mens-sitewide, https://nobullproject.com/collections/womens-sitewide, https://nobullproject.com/collections/mens-mix-match-footwear, https://nobullproject.com/collections/womens-mix-match-footwear and https://nobullproject.com/collections/womens-matching-sets and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://nobullproject.com/products/mens-nobull-tee-black, https://nobullproject.com/products/everyday-quarter-crew-sock-white, https://nobullproject.com/products/nobull-performance-hat-black, https://nobullproject.com/collections/mens-sitewide, https://nobullproject.com/collections/womens-sitewide and https://nobullproject.com/collections/mens-mix-match-footwear and 9 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 125 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 fix87

  • 85 small tap targets

    85 of 121 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 “SecurityError: Failed to read a named property 'document' from 'Window': Blocked a frame with origin "null" from access…”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75

  • No analytics detected

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

  • A 14-field form

    Your longest form asks for 14 fields (0 required). Every extra field lowers completion.

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

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

    The homepage carries about 365 words of visible text.

  • Urgency cues

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

3 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN LOYALTY” and “Order Status”.

  • 42 calls to action

    The homepage has 42 calls to action, for example “Shop Men's”, “Shop Women's” and “Join Loyalty”.

  • Social proof on the page

    Social proof on the homepage: 13 testimonial or review blocks and a star rating.

Privacy and tracking

  • 11 trackers load before any consent

    11

    Before a visitor clicks anything, the page loads Criteo, FullStory, Google Ads, Google Analytics and Google Tag Manager and 6 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

  • 57 cookies set on arrival

    57

    Opening the homepage sets 57 cookies (measured from a US location before any click).

  • 75 other companies contacted

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

1 checks passed

  • Consent tool: Ketch

    A consent management tool (Ketch) 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 publicrec.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 19 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Ignite Formerly Fueled · Fullstory · Nosto · Okendo · Visually A B Testing Cro · Checkmate · Wyllo Formerly Nofraud · Elevar Conversion Tracking · Attentive · Applovin Shop Integration · rise-ai.com · global-e.com · attn.tv · amazonaws.com · retention.com · govx.com · socialsnowball.io · dailykarma.io

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
Analytics
FullStory
Hosting
Cloudflare

Company

Headquarters
Chicago

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on publicrec.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