Website review, no card needed
jtspencer.com website review
Visit site (opens in a new tab)Reviewed 22 November 202628 issues · 78 checks
This review found 28 issues worth fixing on jtspencer.com, 9 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81B- #42,127 of 126,487 reviewed websitesbeats 61%
- #27,677 of 70,491 online storesbeats 54%
- #26,641 of 63,980 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 997 ms |
| Jun 6, 2026 | 999 ms |
| Jun 13, 2026 | 970 ms |
| Jun 20, 2026 | 961 ms |
| Jun 27, 2026 | 956 ms |
| Jul 4, 2026 | 960 ms |
| Jul 11, 2026 | 963 ms |
| Jul 18, 2026 | 958 ms |
| Jul 25, 2026 | 951 ms |
| Aug 1, 2026 | 956 ms |
| Aug 8, 2026 | 952 ms |
| Aug 15, 2026 | 954 ms |
| Aug 22, 2026 | 984 ms |
| Aug 29, 2026 | 976 ms |
| Sep 5, 2026 | 990 ms |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 983 ms |
| Sep 26, 2026 | 999 ms |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 993 ms |
| Oct 31, 2026 | 970 ms |
| Nov 7, 2026 | 948 ms |
| Nov 14, 2026 | 952 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 158 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 155 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 149 ms |
| Aug 8, 2026 | 148 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 148 ms |
| Sep 26, 2026 | 148 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 144 ms |
| Oct 17, 2026 | 140 ms |
| Oct 24, 2026 | 138 ms |
| Oct 31, 2026 | 137 ms |
| Nov 7, 2026 | 137 ms |
| Nov 14, 2026 | 137 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
0.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.3 s
5.0 s
5.7 s
Speed
Reduce unused JavaScript
1.9 s · 700 KiBAbout 700 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.4 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (rebuyengine.com, Google Tag Manager and Clarity and others), adding 1.3 MB and 671 ms of main-thread time.
rebuyengine.com adds 226 ms
226 msrebuyengine.com costs a phone 226 ms of main-thread work and 720 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
290 ms · 46 KiBAbout 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
Use efficient cache lifetimes
200 ms · 74 KiB11 files are served with short cache lifetimes, so returning visitors download them again (74 KiB).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 187 ms. During a long task the page ignores taps.
Improve image delivery
60 KiB1 image could be 60 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 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.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 15.7 s
15.7 sThe page becomes fully interactive after 15.7 s. Good is under 3.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 308 ms
308 msScripts block taps and scrolling for 308 ms in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 149 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 350 ms
350 msReal visitors wait 350 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.4 MB in 165 requests
2.4 MBYour homepage downloads 2.4 MB in 165 requests on a phone: scripts 1.1 MB (70), images 685 KiB (19) and fonts 338 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (70 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.7 g of CO₂ per visit
0.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 80.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
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 25 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (21 characters)
Your title is only 21 characters: “JT Spencer – Imperial”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (320 characters)
Your meta description is 320 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
183 internal links, 33 external
The homepage links to 183 pages on jtspencer.com and 33 external pages.
5 checks passed
One H1 headline
Your main headline reads: “JT Spencer”.
Canonical URL set
The canonical URL is https://imperial1916.com/pages/jtspencer.
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://imperial1916.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 (737 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://imperial1916.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://imperial1916.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://imperial1916.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages without a meta description
https://imperial1916.com/collections/all, https://imperial1916.com/customer_authentication/redirect, https://imperial1916.com/policies/shipping-policy, https://imperial1916.com/collections/accessories and https://imperial1916.com/pages/the-golf-shop have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://imperial1916.com/customer_authentication/redirect, https://imperial1916.com/pages/design-your-own and https://imperial1916.com/pages/the-golf-shop 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 94 found) and read each the way a search engine does.
3 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.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
51 of 61 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 267 words of copy
The homepage carries about 267 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “sign up for email & SMS”.
27 calls to action
The homepage has 27 calls to action, for example “sign up for email & SMS”, “The Imperial Tour Visor® Shop Now” and “Imperial x Slackertide Shop Now”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity and TikTok Pixel.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Microsoft Clarity (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
24 other companies contacted
Loading the homepage contacts 24 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 jtspencer.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Gorgias Live Chat Helpdesk · Rebuy Personalization Engine · Yotpo Product Reviews · Yotpo Loyalty Rewards · Elevar Conversion Tracking · Microsoft Clarity · Klaviyo Email Marketing Sms · Gdpr Cookie Consent
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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Cloudflare
Company
- Headquarters
- Richmond
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 jtspencer.com, including 12 speed issues, 4 SEO issues and 2 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.