Website review, no card needed
furiafuria.com website review
Visit site (opens in a new tab)Reviewed 9 November 202625 issues · 75 checks
This review found 25 issues worth fixing on furiafuria.com, 10 of them high impact, across 75 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
83B- #25,242 of 109,350 reviewed websitesbeats 72%
- #16,619 of 61,859 online storesbeats 67%
- #16,121 of 56,401 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 160 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 159 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 158 ms |
| Jul 25, 2026 | 157 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 163 ms |
| Aug 15, 2026 | 167 ms |
| Aug 22, 2026 | 169 ms |
| Aug 29, 2026 | 172 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 172 ms |
| Sep 26, 2026 | 175 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 178 ms |
| Oct 17, 2026 | 177 ms |
| Oct 24, 2026 | 177 ms |
| Oct 31, 2026 | 176 ms |
| Nov 7, 2026 | 176 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
2.5 s · 1.5 MB24 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 102 KiBAbout 102 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 137 ms
137 msKlaviyo costs a phone 137 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.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, avada.io and Clarity and others), adding 879 KiB and 444 ms of main-thread time.
Reduce unused JavaScript
142 KiBAbout 142 KiB of JavaScript is downloaded but never used on this page.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 102 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
46 KiB9 files are served with short cache lifetimes, so returning visitors download them again (46 KiB).
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.6 s
9.6 sYour largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “IMG_07883.jpg”.
Time to Interactive: 16.3 s
16.3 sThe page becomes fully interactive after 16.3 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.114
0.114The layout shifts by 0.114 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 160 ms to 176 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.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 176 ms
176 msReal visitors wait 176 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: 314 ms
314 msReal visitors wait 314 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 46 ms
46 msScripts block the page for only 46 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.8 MB in 246 requests
4.8 MBYour homepage downloads 4.8 MB in 246 requests on a phone: images 2.6 MB (31), scripts 1.0 MB (87) and other files 783 KiB (114). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 163.0 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
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (217 characters)
Your meta description is 217 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
80 internal links, 5 external
The homepage links to 80 pages on furiafuria.com and 5 external pages.
6 checks passed
Title: 35 characters
Your title is a healthy 35 characters: “FURIA - Illustrated cotton t-shirts”.
Canonical URL set
The canonical URL is https://furiafuria.com/en-us.
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://furiafuria.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 (275 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://furiafuria.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
10 pages share a meta description
https://furiafuria.com/en-us/collections/frontpage, https://furiafuria.com/en-us/collections/camisetas, https://furiafuria.com/en-us/collections/sudaderas, https://furiafuria.com/en-us/collections/bags, https://furiafuria.com/en-us/collections/prints-1 and https://furiafuria.com/en-us/collections/stickers and 4 others use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://furiafuria.com/en-us/products/zip-torneo%C2%A9-disponible-domingo-3-de-mayo, whose canonical is https://furiafuria.com/en-us/products/zip-torneo%c2%a9-disponible-domingo-3-de-mayo. 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 27 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.
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.
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
13 small tap targets
13 of 43 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Unexpected identifier 'CA'”.
1 checks passed
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 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 189 words
The homepage has only about 189 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.
3 checks passed
11 calls to action
The homepage has 11 calls to action, for example “Add order notes”, “Shop All” and “Quick Buy”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
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.
40 other companies contacted
Loading the homepage contacts 40 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 furiafuria.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Microsoft Clarity · Pagefly Ai Page Builder · Klaviyo Email Marketing Sms · Region Restrictions · Avada Cookie Bar · nfcube.com · web.app
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
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on furiafuria.com, including 10 speed issues, 2 SEO issues 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.