Website review, no card needed
jbalvin.com website review
Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 86 checks
This review found 33 issues worth fixing on jbalvin.com, 11 of them high impact, across 86 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
82B- #27,348 of 96,332 reviewed websitesbeats 66%
- #17,492 of 52,171 online storesbeats 60%
- #16,879 of 47,258 Shopify storesbeats 57%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 140 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 118 ms |
| Aug 1, 2026 | 110 ms |
| Aug 8, 2026 | 107 ms |
| Aug 15, 2026 | 107 ms |
| Aug 22, 2026 | 114 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 124 ms |
| Sep 12, 2026 | 124 ms |
| Sep 19, 2026 | 119 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 119 ms |
| Oct 10, 2026 | 118 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 119 ms |
| Oct 31, 2026 | 127 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
Speed
Reduce unused JavaScript
3.7 s · 758 KiBAbout 758 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.
Use efficient cache lifetimes
1.8 s · 386 KiB18 files are served with short cache lifetimes, so returning visitors download them again (386 KiB).
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
950 ms · 895 KiB19 images could be 895 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and OptiMonk and others), adding 1.8 MB and 1.0 s of main-thread time.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Shopify adds 410 ms
410 msShopify costs a phone 410 ms of main-thread work and 1.2 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.
Legacy JavaScript
350 ms · 38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
1,722 HTML elements
The page has 1,722 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
280 ms · 56 KiBAbout 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
Duplicated JavaScript
100 ms · 17 KiB17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.
Minify JavaScript
27 KiB27 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 23.6 s
23.6 sYour largest element takes 23.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: 25.9 s
25.9 sThe page becomes fully interactive after 25.9 s. Good is under 3.8 s.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 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.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
10 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 624 ms
624 msReal visitors wait 624 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 140 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 37% faster for real visitors
-37%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 111 ms
111 msScripts block the page for only 111 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.6 MB in 479 requests
5.6 MBYour homepage downloads 5.6 MB in 479 requests on a phone: scripts 1.8 MB (154), images 1.8 MB (38) and other files 1.3 MB (253). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
286 KiB8 images are downloaded at several times the size a phone draws them, for example AJ01_BACK_LAYFLAT_8bb0cd6a-e2db-44c1-91ae-e294c98b746d_800x. at 800 px wide, shown at 170 px. Resized copies would save about 286 KiB.
About 1.6 g of CO₂ per visit
1.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 190.3 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
Unlabelled dropdowns
1 dropdown has no label.
24 images without alt text
24 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
48 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: 48 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("jbalvin.com")”.
86 internal links, 89 external
The homepage links to 86 pages on jbalvin.com and 89 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “The Air Jordan 4 “Amazonas” are the latest exclusive collaboration between J Balvin and Jordan Brand, inspired by the y…”.
One H1 headline
Your main headline reads: “J Balvin”.
Title: 34 characters
Your title is a healthy 34 characters: “Air Jordan 4 x J Balvin | Amazonas”.
Canonical URL set
The canonical URL is https://jbalvin.com/.
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://jbalvin.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (406 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://jbalvin.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://jbalvin.com/pages/shop, https://jbalvin.com/collections/halloween, https://jbalvin.com/collections/aj4-amazonas, https://jbalvin.com/collections/mystery-boxes, https://jbalvin.com/collections/omerta and https://jbalvin.com/pages/velez-x-jbalvin and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://jbalvin.com/pages/shop, https://jbalvin.com/collections/halloween, https://jbalvin.com/collections/aj4-amazonas, https://jbalvin.com/collections/mystery-boxes, https://jbalvin.com/collections/omerta and https://jbalvin.com/pages/velez-x-jbalvin and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://jbalvin.com/collections/all 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 46 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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “jQuery is not defined”.
2 checks passed
Tap targets are thumb-sized
14 of 15 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 242 words
The homepage has only about 242 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Shop”, “Subscribe icon-right-arrow” and “Shop Now”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Meta Pixel and Microsoft Clarity.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (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.
24 cookies set on arrival
24Opening the homepage sets 24 cookies, 2 of them by other companies (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.
42 other companies contacted
Loading the homepage contacts 42 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 jbalvin.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on jbalvin.com, including 15 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.