Website review, no card needed
buffbunny.com website review
Visit site (opens in a new tab)Reviewed 8 November 202634 issues · 87 checks
This review found 34 issues worth fixing on buffbunny.com, 8 of them high impact, across 87 checks. The most urgent: main-thread work: 9.9 s. 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
80B- #34,681 of 88,930 reviewed websitesbeats 55%
- #21,434 of 46,312 online storesbeats 47%
- #20,475 of 41,572 Shopify storesbeats 44%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 187 ms |
| May 23, 2026 | 201 ms |
| May 30, 2026 | 211 ms |
| Jun 6, 2026 | 215 ms |
| Jun 13, 2026 | 225 ms |
| Jun 20, 2026 | 236 ms |
| Jun 27, 2026 | 246 ms |
| Jul 4, 2026 | 271 ms |
| Jul 11, 2026 | 279 ms |
| Jul 18, 2026 | 280 ms |
| Jul 25, 2026 | 271 ms |
| Aug 1, 2026 | 237 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 179 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 153 ms |
| Oct 17, 2026 | 149 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 146 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
1.1 s
2.1 s
3.2 s
4.3 s
5.4 s
6.4 s
7.5 s
8.6 s
Speed
Main-thread work: 9.9 s
A phone's processor spends 9.9 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7,308 HTML elements
The page has 7,308 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
600 ms · 980 KiBAbout 980 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Yotpo and rebuyengine.com and others), adding 3.0 MB and 1.1 s of main-thread time.
Improve image delivery
150 ms · 1.1 MB42 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 971 KiB44 files are served with short cache lifetimes, so returning visitors download them again (971 KiB).
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Shopify adds 306 ms
306 msShopify costs a phone 306 ms of main-thread work and 619 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.
Yotpo adds 287 ms
287 msYotpo costs a phone 287 ms of main-thread work and 563 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.
rebuyengine.com adds 256 ms
256 msrebuyengine.com costs a phone 256 ms of main-thread work and 732 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 121 ms
121 msKlaviyo costs a phone 121 ms of main-thread work and 305 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.
Attentive adds 67 ms
67 msAttentive costs a phone 67 ms of main-thread work and 540 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 · 101 KiBAbout 101 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.
Minify JavaScript
150 ms · 52 KiB52 KiB could be saved by minifying JavaScript.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Legacy JavaScript
63 KiBPolyfills for old browsers add 63 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Duplicated JavaScript
19 KiB19 KiB JavaScript is shipped twice across bundles.
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
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 176 ms
176 msYour server sent the HTML in 176 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 37.7 s
37.7 sThe page becomes fully interactive after 37.7 s. Good is under 3.8 s.
Speed Index: 13.5 s
13.5 sVisually, the page fills in at 13.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 7.3 s
7.3 sYour largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 529 ms
529 msScripts block taps and scrolling for 529 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 140 ms
140 msReal visitors wait 140 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 432 ms
432 msReal visitors wait 432 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 187 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 8.0 MB in 572 requests
8.0 MBYour homepage downloads 8.0 MB in 572 requests on a phone: images 3.5 MB (153), scripts 2.5 MB (144) and other files 1.2 MB (209). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
dawesfrgdth_1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 2.3 g of CO₂ per visit
2.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.26 g of CO₂e: 271.2 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
30 links without text
30 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h4 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
17 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 17 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 0 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Buffbunny” and “Quick Add”). One clear main headline is easier for people and search engines.
Meta description is long (187 characters)
Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.
681 internal links, 14 external
The homepage links to 681 pages on buffbunny.com and 14 external pages.
6 checks passed
Title: 58 characters
Your title is a healthy 58 characters: “Shop Women's Athletic Wear for Every Body Type | Buffbunny”.
Canonical URL set
The canonical URL is https://www.buffbunny.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.buffbunny.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,313 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
/collections/momentum-shorts, /collections/pretty-gritty, /collections/metamorphosis, /collections/10-year-anniversary, /collections/summer-sale and /collections/hot-girl-summer and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 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.
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
10 broken images
10 images failed to load on a phone, for example https://cdn-yotpo-images-production.yotpo.com/Product/991686420/892404593/square.jpg?1789656048.
79 small tap targets
79 of 159 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "sticky-header" has already been use…”.
23 distorted images
23 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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,546 words of copy
The homepage carries about 1,546 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop All” and “Shop Pretty Gritty”.
18 calls to action
The homepage has 18 calls to action, for example “Shop All”, “Shop Pretty Gritty” and “Shop Now”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
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.
43 cookies set on arrival
43Opening the homepage sets 43 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.
55 other companies contacted
Loading the homepage contacts 55 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 buffbunny.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 17 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Bitly · Yotpo Product Reviews · Pfp7cml68 Opensend · Rebuy Personalization Engine · Klaviyo Email Marketing Sms · Triplewhale · Attentive · Yotpo Loyalty Rewards · Loop Returns · Swym Wishlist Plus · gorgias.chat · attn.tv · rebuyengine.com · 9gtb.com · global-e.com · getredo.com · cloudfront.net
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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Stafford
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on buffbunny.com, including 18 speed issues, 2 SEO issues and 3 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.