Website review, no card needed
fansbrands.com website review
Visit site (opens in a new tab)Reviewed 9 November 202635 issues · 82 checks
This review found 35 issues worth fixing on fansbrands.com, 12 of them high impact, across 82 checks. The most urgent: improve image delivery. 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- #33,211 of 117,905 reviewed websitesbeats 66%
- #22,181 of 67,032 online storesbeats 60%
- #21,446 of 61,120 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 203 ms |
| May 30, 2026 | 209 ms |
| Jun 6, 2026 | 201 ms |
| Jun 13, 2026 | 200 ms |
| Jun 20, 2026 | 206 ms |
| Jun 27, 2026 | 205 ms |
| Jul 4, 2026 | 218 ms |
| Jul 11, 2026 | 237 ms |
| Jul 18, 2026 | 243 ms |
| Jul 25, 2026 | 261 ms |
| Aug 1, 2026 | 259 ms |
| Aug 8, 2026 | 247 ms |
| Aug 15, 2026 | 232 ms |
| Aug 22, 2026 | 191 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 160 ms |
| Sep 12, 2026 | 164 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 177 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 158 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 155 ms |
| Nov 7, 2026 | 155 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
Improve image delivery
1.0 s · 1.8 MB25 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Main-thread work: 16.8 s
A phone's processor spends 16.8 s on main-thread work while loading, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 1.0 s
1.0 sShopify costs a phone 1.0 s of main-thread work and 2.1 MB 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: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,301 HTML elements
The page has 6,301 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, OptiMonk and Clarity and others), adding 3.4 MB and 2.0 s of main-thread time.
Reduce unused JavaScript
600 ms · 196 KiBAbout 196 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
OptiMonk adds 416 ms
416 msOptiMonk costs a phone 416 ms of main-thread work and 702 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.
Render-blocking requests
450 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Use efficient cache lifetimes
300 ms · 149 KiB18 files are served with short cache lifetimes, so returning visitors download them again (149 KiB).
Legacy JavaScript
300 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Clarity adds 250 ms
250 msClarity costs a phone 250 ms of main-thread work and 29 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.
Klaviyo adds 172 ms
172 msKlaviyo costs a phone 172 ms of main-thread work and 326 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 · 68 KiBAbout 68 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.
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: 18 ms
18 msYour server sent the HTML in 18 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.
Largest Contentful Paint: 35.6 s
35.6 sYour largest element takes 35.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “X Be Our Next Winner! Scratch and win a V.I.P. membership w…”.
Time to Interactive: 36.6 s
36.6 sThe page becomes fully interactive after 36.6 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 826 ms
826 msReal visitors wait 826 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 498 ms
498 msScripts block taps and scrolling for 498 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.182
0.182The layout shifts by 0.182 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 153 ms
153 msReal visitors wait 153 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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 203 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 7.8 MB in 526 requests
7.8 MBYour homepage downloads 7.8 MB in 526 requests on a phone: images 4.2 MB (65), scripts 1.2 MB (175) and fonts 1.1 MB (64). Under 2 MB keeps phones on slow connections fast.
16 images in older formats
16 images (1.3 MB) are 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.
1 image far larger than shown
95 KiB1 image is downloaded at several times the size a phone draws it, for example fb-black-friday-artwork-mobile.webp at 1,254 px wide, shown at 348 px. Resized copies would save about 95 KiB.
2 images below the first screen load straight away
2 images further down the page (173 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.2 g of CO₂ per visit
2.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.22 g of CO₂e: 266.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
38 links without text
38 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. (3 elements).
2 checks passed
Every image has alt text
All 141 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Formula 1® Shop | F1 Clothing & Accessories | FansBRANDS® – FansBRANDS® - COM”.
663 internal links, 23 external
The homepage links to 663 pages on fansbrands.com and 23 external pages.
7 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Official Formula 1® clothing, caps and accessories in stock. Ferrari, Red Bull Racing, Mercedes and McLaren products wi…”.
One H1 headline
Your main headline reads: “About Us – FansBRANDS®”.
Canonical URL set
The canonical URL is https://fansbrands.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://fansbrands.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,841 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fansbrands.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without an H1
https://fansbrands.com/collections/black-friday, https://fansbrands.com/collections/special-edition, https://fansbrands.com/collections/scuderia-ferrari-f1-new-collection, https://fansbrands.com/collections/red-bull-racing-f1-new-collection and https://fansbrands.com/collections/mercedes-f1-new-collection 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 197 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'getClientRects')”.
2 checks passed
Tap targets are thumb-sized
124 of 124 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: “3.500+ reviews”. 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.
About 1,403 words of copy
The homepage carries about 1,403 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “SHOP BLACK FRIDAY”.
19 calls to action
The homepage has 19 calls to action, for example “SHOP BY TEAM”, “SHOP BY DRIVER” and “➤ Orders & Order Management”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity and 1 more (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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
33 other companies contacted
Loading the homepage contacts 33 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 fansbrands.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 35 issues on fansbrands.com, including 21 speed issues, 1 SEO issue 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.