Website review, no card needed
getfussy.com website review
Visit site (opens in a new tab)Reviewed 4 November 202637 issues · 84 checks
This review found 37 issues worth fixing on getfussy.com, 10 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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- #27,708 of 121,485 reviewed websitesbeats 72%
- #18,229 of 68,726 online storesbeats 67%
- #17,667 of 62,623 Shopify storesbeats 65%
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 | 2.0 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 150 ms |
| May 23, 2026 | 150 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 155 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 164 ms |
| Jul 18, 2026 | 166 ms |
| Jul 25, 2026 | 166 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 175 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 180 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 180 ms |
| Oct 10, 2026 | 180 ms |
| Oct 17, 2026 | 180 ms |
| Oct 24, 2026 | 179 ms |
| Oct 31, 2026 | 178 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.4 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Facebook and others), adding 1.9 MB and 1.5 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
829 KiBAbout 829 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 605 ms
605 msGoogle Tag Manager costs a phone 605 ms of main-thread work and 719 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.
Use efficient cache lifetimes
482 KiB35 files are served with short cache lifetimes, so returning visitors download them again (482 KiB).
Improve image delivery
389 KiB14 images could be 389 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 282 ms
282 msShopify costs a phone 282 ms of main-thread work and 486 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.
2,666 HTML elements
The page has 2,666 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 258 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need.
Reduce unused CSS
26 KiBAbout 26 KiB of CSS is downloaded but never applied on this page.
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 CSS
5 KiB5 KiB could be saved by minifying CSS.
Duplicated JavaScript
1 KiB1 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 26.6 s
26.6 sThe page becomes fully interactive after 26.6 s. Good is under 3.8 s.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 552 ms
552 msScripts block taps and scrolling for 552 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 150 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 133 ms
133 msReal visitors wait 133 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 323 ms
323 msReal visitors wait 323 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 445 requests
4.5 MBYour homepage downloads 4.5 MB in 445 requests on a phone: scripts 2.3 MB (144), images 1.0 MB (101) and other files 865 KiB (151). Under 2 MB keeps phones on slow connections fast.
9 images below the first screen load straight away
9 images further down the page (467 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images far larger than shown
130 KiB6 images are downloaded at several times the size a phone draws them, for example LavenderFieldsBAU_StarterPack_web.jpg at 640 px wide, shown at 171 px. Resized copies would save about 130 KiB.
About 1.3 g of CO₂ per visit
1.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 153.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
23 tap targets too small
23 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
25 images without alt text
25 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 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 6 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 (232 characters)
Your meta description is 232 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
165 internal links, 15 external
The homepage links to 165 pages on getfussy.com and 15 external pages.
6 checks passed
Title: 61 characters
Your title is a healthy 61 characters: “Fussy™ Refillable Natural Deodorant - As Seen On Dragons' Den”.
Canonical URL set
The canonical URL is https://www.getfussy.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://www.getfussy.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 (928 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.getfussy.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.getfussy.com/collections/back-from-the-dead-collection is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.getfussy.com/pages/subscribe and https://www.getfussy.com/pages/subscribe-bodywash all use the title “Subscribe - Fussy Natural Deodorant”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.getfussy.com/collections/back-from-the-dead-collection and https://www.getfussy.com/pages/subscribe-hand-wash have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.getfussy.com/pages/subscribe and https://www.getfussy.com/pages/subscribe-bodywash use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://www.getfussy.com/pages/subscribe, https://www.getfussy.com/pages/deodorant, https://www.getfussy.com/pages/subscribe-bodywash, https://www.getfussy.com/pages/body-wash and https://www.getfussy.com/pages/subscribe-hand-wash 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 41 found) and read each the way a search engine does.
3 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 title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343002010&tm=gtm002&Ver=2&mid=3cdaab5a-7871-47c9-909c-d173e5cc19f5&bo=1&sid=28872720d82011f1b9e19fb952944b0d&vid=28873910d82011f19075d7cffa633dd6&vids=1&msclkid=N&pi=9.
8 small tap targets
8 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 457 words of copy
The homepage carries about 457 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: “🪵 SHOP OUR LIMITED EDITION SCENTS 💐” and “Sign In / Register”.
18 calls to action
The homepage has 18 calls to action, for example “🪵 SHOP OUR LIMITED EDITION SCENTS 💐”, “Learn More” and “Contact us”.
13 short forms
13 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 32 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 6 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
30 cookies set on arrival
30Opening the homepage sets 30 cookies (measured from a US location before any click).
65 other companies contacted
Loading the homepage contacts 65 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 getfussy.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on getfussy.com, including 16 speed issues, 3 SEO issues and 1 conversion gap. 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.