Website review, no card needed
soccerbreakersfc.com website review
Visit site (opens in a new tab)Reviewed 8 November 202622 issues · 78 checks
This review found 22 issues worth fixing on soccerbreakersfc.com, 5 of them high impact, across 78 checks. The most urgent: <dt> and <dd> elements must be contained by a <dl> (30 elements). 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
91A- #1,267 of 96,623 reviewed websitesbeats 98%
- #549 of 52,400 online storesbeats 98%
- #523 of 47,474 Shopify storesbeats 98%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 938 ms |
| May 23, 2026 | 950 ms |
| May 30, 2026 | 953 ms |
| Jun 6, 2026 | 971 ms |
| Jun 13, 2026 | 988 ms |
| Jun 20, 2026 | 989 ms |
| Jun 27, 2026 | 982 ms |
| Jul 4, 2026 | 954 ms |
| Jul 11, 2026 | 956 ms |
| Jul 18, 2026 | 959 ms |
| Jul 25, 2026 | 948 ms |
| Aug 1, 2026 | 979 ms |
| Aug 8, 2026 | 963 ms |
| Aug 15, 2026 | 957 ms |
| Aug 22, 2026 | 968 ms |
| Aug 29, 2026 | 949 ms |
| Sep 5, 2026 | 928 ms |
| Sep 12, 2026 | 875 ms |
| Sep 19, 2026 | 853 ms |
| Sep 26, 2026 | 859 ms |
| Oct 3, 2026 | 894 ms |
| Oct 10, 2026 | 926 ms |
| Oct 17, 2026 | 948 ms |
| Oct 24, 2026 | 954 ms |
| Oct 31, 2026 | 940 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 67 ms |
| May 23, 2026 | 67 ms |
| May 30, 2026 | 67 ms |
| Jun 6, 2026 | 69 ms |
| Jun 13, 2026 | 68 ms |
| Jun 20, 2026 | 68 ms |
| Jun 27, 2026 | 65 ms |
| Jul 4, 2026 | 63 ms |
| Jul 11, 2026 | 63 ms |
| Jul 18, 2026 | 62 ms |
| Jul 25, 2026 | 62 ms |
| Aug 1, 2026 | 63 ms |
| Aug 8, 2026 | 64 ms |
| Aug 15, 2026 | 66 ms |
| Aug 22, 2026 | 68 ms |
| Aug 29, 2026 | 68 ms |
| Sep 5, 2026 | 70 ms |
| Sep 12, 2026 | 70 ms |
| Sep 19, 2026 | 70 ms |
| Sep 26, 2026 | 70 ms |
| Oct 3, 2026 | 66 ms |
| Oct 10, 2026 | 66 ms |
| Oct 17, 2026 | 64 ms |
| Oct 24, 2026 | 64 ms |
| Oct 31, 2026 | 63 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.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.4 s
5.0 s
Speed
Render-blocking requests
500 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Improve image delivery
300 ms · 129 KiB8 images could be 129 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused JavaScript
300 ms · 102 KiBAbout 102 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 866 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,780 HTML elements
The page has 1,780 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 17 KiBAbout 17 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 134 ms. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (cloudfront.net, Shopify and Mailchimp and others), adding 262 KiB and 108 ms of main-thread time.
Use efficient cache lifetimes
89 KiB14 files are served with short cache lifetimes, so returning visitors download them again (89 KiB).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92. That is in Google's “good” band (90 and up).
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SOCCER BREAKERS FC”. Most of its time is resource load delay (1.3 s).
Time to Interactive: 3.9 s
3.9 sThe page becomes fully interactive after 3.9 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 67 ms to 63 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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: 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: 51 ms
51 msReal visitors wait 51 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: 213 ms
213 msReal visitors wait 213 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 130 ms
130 msScripts block the page for only 130 ms while loading. Good is under 200 ms.
Speed Index: 2.5 s
2.5 sVisually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Images and page weight
About 0.4 g of CO₂ per visit
0.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.41 g of CO₂e: 48.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.4 MB in 134 requests
1.4 MBYour homepage downloads 1.4 MB in 134 requests on a phone: other files 787 KiB (80), images 310 KiB (9) and scripts 309 KiB (41). That is a lean page.
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
<dt> and <dd> elements must be contained by a <dl> (30 elements)
<dt> and <dd> elements must be contained by a <dl>: 30 elements on the page fail this check, rated serious by axe-core.
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (15 elements)
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 15 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
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.
2 checks passed
Every image has alt text
All 31 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 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 short (18 characters)
Your title is only 18 characters: “Soccer Breakers FC”. Between 30 and 65 characters leaves room to say what you do and for whom.
49 internal links, 11 external
The homepage links to 49 pages on soccerbreakersfc.com and 11 external pages.
7 checks passed
Meta description: 70 characters
Your meta description is 70 characters: “Soccer Breakers FC , the best place to break soccer cards. Watch live.”.
One H1 headline
Your main headline reads: “<img src="//soccerbreakersfc.com/cdn/shop/files/Transparent_SBFC_Logo_1_49681304-0fc3-4e5c-80df-888676b3a904_110x.png?v…”.
Canonical URL set
The canonical URL is https://soccerbreakersfc.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://soccerbreakersfc.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,011 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://soccerbreakersfc.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages share 2 titles
https://soccerbreakersfc.com/collections/breaking-tonight/products/30-spot-30-winner-super-discounted-filler-to-fill-25-26-topps-stadium-club-chrome-x3-case-break-pytp25-dowman-rio-estevao-karl-salah and https://soccerbreakersfc.com/collections/2025-26-pristine-epl/products/30-spot-30-winner-super-discounted-filler-to-fill-25-26-topps-stadium-club-chrome-x3-case-break-pytp25-dowman-rio-estevao-karl-salah all use the title “30 SPOT 30 WINNER SUPER DISCOUNTED FILLER!! TO FILL 25-26 TOPPS STADI…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://soccerbreakersfc.com/collections/full-cases has no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://soccerbreakersfc.com/collections/breaking-tonight/products/30-spot-30-winner-super-discounted-filler-to-fill-25-26-topps-stadium-club-chrome-x3-case-break-pytp25-dowman-rio-estevao-karl-salah and https://soccerbreakersfc.com/collections/2025-26-pristine-epl/products/30-spot-30-winner-super-discounted-filler-to-fill-25-26-topps-stadium-club-chrome-x3-case-break-pytp25-dowman-rio-estevao-karl-salah use the same meta description. A description written for each page earns more clicks.
11 links to non-canonical URLs
Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://soccerbreakersfc.com/collections/breaking-tonight/products/30-spot-30-winner-super-discounted-filler-to-fill-25-26-topps-stadium-club-chrome-x3-case-break-pytp25-dowman-rio-estevao-karl-salah, whose canonical is https://soccerbreakersfc.com/products/30-spot-30-winner-super-discounted-filler-to-fill-25-26-topps-stadium-club-chrome-x3-case-break-pytp25-dowman-rio-estevao-karl-salah. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
17 of 18 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,617 words of copy
The homepage carries about 1,617 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Join Our WhatsApp Group” and “Subscribe”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 soccerbreakersfc.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
cloudfront.net · chimpstatic.com
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on soccerbreakersfc.com, including 8 speed issues, 1 SEO issue and 4 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.