Website review, no card needed
publicrecapparel.com website review
Visit site (opens in a new tab)Reviewed 20 November 202643 issues · 90 checks
This review found 43 issues worth fixing on publicrecapparel.com, 21 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68D- #109,051 of 124,317 reviewed websitesbeats 10%
- #65,099 of 69,856 online storesbeats 5%
- #59,889 of 63,524 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.2 s |
| Nov 7, 2026 | 3.3 s |
| Nov 14, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 246 ms |
| Jun 6, 2026 | 252 ms |
| Jun 13, 2026 | 254 ms |
| Jun 20, 2026 | 255 ms |
| Jun 27, 2026 | 254 ms |
| Jul 4, 2026 | 237 ms |
| Jul 11, 2026 | 222 ms |
| Jul 18, 2026 | 212 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 198 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 193 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 195 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 195 ms |
| Sep 26, 2026 | 190 ms |
| Oct 3, 2026 | 187 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 188 ms |
| Oct 24, 2026 | 196 ms |
| Oct 31, 2026 | 205 ms |
| Nov 7, 2026 | 213 ms |
| Nov 14, 2026 | 221 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
How it loaded on a phone
2.0 s
4.1 s
6.1 s
8.2 s
10.2 s
12.3 s
14.3 s
16.4 s
Speed
Reduce unused JavaScript
5.7 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.
Use efficient cache lifetimes
4.0 s · 1.0 MB49 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Main-thread work: 41.3 s
A phone's processor spends 41.3 s on main-thread work while loading, 29.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
FullStory adds 2.2 s
2.2 sFullStory costs a phone 2.2 s of main-thread work and 203 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.
Shopify adds 1.8 s
1.8 sShopify costs a phone 1.8 s of main-thread work and 416 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.
17,809 HTML elements
The page has 17,809 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 1.4 s
1.4 sGoogle Tag Manager costs a phone 1.4 s of main-thread work and 735 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.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (FullStory, Shopify and Google Tag Manager and others), adding 2.5 MB and 7.1 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.
Render-blocking requests
950 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Improve image delivery
928 KiB26 images could be 928 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
fueled.io adds 727 ms
727 msfueled.io costs a phone 727 ms of main-thread work and 91 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
300 ms · 64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
govx.com adds 338 ms
338 msgovx.com costs a phone 338 ms of main-thread work and 7 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.
Reduce unused CSS
150 ms · 29 KiBAbout 29 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.
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 54 ms
54 msYour server sent the HTML in 54 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 35.7 s
35.7 sYour largest element takes 35.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Men's Fog Dealmaker 5-Pocket Pant Lower Body Front Angle.”.
Speed Index: 22.6 s
22.6 sVisually, the page fills in at 22.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 14.0 s
14.0 sScripts block taps and scrolling for 14.0 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 50.7 s
50.7 sThe page becomes fully interactive after 50.7 s. Good is under 3.8 s.
Real-user INP: 394 ms
394 msReal visitors wait 394 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
4 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user TTFB: 444 ms
444 msReal visitors wait 444 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 246 ms to 221 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.053
0.053The layout barely moves while loading (CLS 0.053, good is under 0.1).
Images and page weight
Page weight: 9.5 MB in 621 requests
9.5 MBYour homepage downloads 9.5 MB in 621 requests on a phone: images 3.8 MB (169), scripts 3.5 MB (166) and other files 1.0 MB (216). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
667 KiB8 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.7 g of CO₂ per visit
2.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.69 g of CO₂e: 322.2 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
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.
59 tap targets too small
59 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (39 elements)
Elements must only use permitted ARIA attributes: 39 elements on the page fail this check, rated serious by axe-core.
33 text elements with low contrast
33 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (9 elements)
Scrollable region must have keyboard access: 9 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 129 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 7 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
339 internal links, 0 external
The homepage links to 339 pages on publicrecapparel.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
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,043 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
6 pages without a meta description
https://nobullproject.com/products/nobull-performance-hat-black, https://nobullproject.com/collections/mens-week-of-deals, https://nobullproject.com/collections/womens-week-of-deals, https://nobullproject.com/collections/mens-week-of-deals-day4, https://nobullproject.com/collections/womens-week-of-deals-day4 and https://nobullproject.com/collections/week-of-deals-day4 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-week-of-deals, https://nobullproject.com/collections/womens-week-of-deals and https://nobullproject.com/collections/mens-week-of-deals-day4 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://nobullproject.com/collections/mens-shoes has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 123 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
83 small tap targets
83 of 121 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 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…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 410 words of copy
The homepage carries about 410 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: “Shop Men's” and “JOIN LOYALTY”.
39 calls to action
The homepage has 39 calls to action, for example “Shop Men's”, “Shop Women's” and “Join Loyalty”.
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks and a star rating.
Privacy and tracking
15 trackers load before any consent
15Before a visitor clicks anything, the page loads Criteo, FullStory, Google Ads, Google Analytics and Google Tag Manager and 10 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.
82 cookies set on arrival
82Opening the homepage sets 82 cookies (measured from a US location before any click).
93 other companies contacted
Loading the homepage contacts 93 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 publicrecapparel.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 · Attentive · Checkmate · Elevar Conversion Tracking · Ignite Formerly Fueled · Fullstory · Okendo · Visually A B Testing Cro · Wyllo Formerly Nofraud · Nosto · 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
- Shopify
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 43 issues on publicrecapparel.com, including 25 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.