Website review, no card needed
jackwhiteiiistore.com website review
Visit site (opens in a new tab)Reviewed 12 November 202627 issues · 74 checks
This review found 27 issues worth fixing on jackwhiteiiistore.com, 10 of them high impact, across 74 checks. The most urgent: use efficient cache lifetimes. 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
77C- #61,188 of 108,808 reviewed websitesbeats 39%
- #39,734 of 61,740 online storesbeats 30%
- #37,859 of 56,345 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 997 ms |
| Jul 25, 2026 | 934 ms |
| Aug 1, 2026 | 911 ms |
| Aug 8, 2026 | 883 ms |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 863 ms |
| Oct 10, 2026 | 736 ms |
| Oct 17, 2026 | 728 ms |
| Oct 24, 2026 | 792 ms |
| Oct 31, 2026 | 944 ms |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 87 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 91 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 101 ms |
| Jun 27, 2026 | 101 ms |
| Jul 4, 2026 | 101 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 90 ms |
| Jul 25, 2026 | 88 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 86 ms |
| Aug 15, 2026 | 88 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 97 ms |
| Sep 5, 2026 | 102 ms |
| Sep 12, 2026 | 101 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 92 ms |
| Oct 10, 2026 | 91 ms |
| Oct 17, 2026 | 89 ms |
| Oct 24, 2026 | 94 ms |
| Oct 31, 2026 | 95 ms |
| Nov 7, 2026 | 96 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.8 s
1.6 s
2.4 s
3.3 s
4.1 s
4.9 s
5.7 s
6.5 s
Speed
Use efficient cache lifetimes
1.5 s · 329 KiB13 files are served with short cache lifetimes, so returning visitors download them again (329 KiB).
Reduce unused JavaScript
1.5 s · 279 KiBAbout 279 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 2.0 s. During a long task the page ignores taps.
Improve image delivery
900 ms · 392 KiB11 images could be 392 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Klaviyo and Google Tag Manager and others), adding 988 KiB and 642 ms of main-thread time.
Render-blocking requests
450 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Klaviyo adds 148 ms
148 msKlaviyo costs a phone 148 ms of main-thread work and 310 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
200 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.2 s
13.2 sYour largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Tour Hoodie”.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.137
0.137The layout shifts by 0.137 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 87 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 94 ms
94 msReal visitors wait 94 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: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 490 ms
490 msReal visitors wait 490 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 2.5 MB in 209 requests
2.5 MBYour homepage downloads 2.5 MB in 209 requests on a phone: scripts 1.1 MB (74), other files 781 KiB (111) and images 523 KiB (17). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.71 g of CO₂e: 84.7 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
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.
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
49 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: 49 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
27 internal links, 12 external
The homepage links to 27 pages on jackwhiteiiistore.com and 12 external pages.
6 checks passed
Meta description: 101 characters
Your meta description is 101 characters: “Shop the collection of clothing, accessories, and music at the official Jack White Merchandise store!”.
One H1 headline
Your main headline reads: “Stay Up To Date”.
Title: 39 characters
Your title is a healthy 39 characters: “Jack White | Official Merchandise Store”.
Canonical URL set
The canonical URL is https://jackwhiteiiistore.com/.
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://jackwhiteiiistore.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 (181 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://jackwhiteiiistore.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://jackwhiteiiistore.com/collections/shop-all, https://jackwhiteiiistore.com/collections/media, https://jackwhiteiiistore.com/collections/tour-2025, https://jackwhiteiiistore.com/collections/apparel, https://jackwhiteiiistore.com/collections/accessoires and https://jackwhiteiiistore.com/products/silver-skull-patch-hat and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages with very little text
https://jackwhiteiiistore.com/products/silver-skull-patch-hat, https://jackwhiteiiistore.com/products/blue-skull-patch-hat and https://jackwhiteiiistore.com/products/tour-tote-bag have 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 21 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
6 small tap targets
6 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Only about 164 words
The homepage has only about 164 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SIGN UP”.
4 calls to action
The homepage has 4 calls to action, for example “Shop All”, “Sign Up” and “Contact Us”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
30 other companies contacted
Loading the homepage contacts 30 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 jackwhiteiiistore.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Essential Announcer · Minmaxify Order Limits · Essential Announcement Bar
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
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on jackwhiteiiistore.com, including 15 speed issues, 2 SEO 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.