Website review, no card needed
furbo.com website review
Visit site (opens in a new tab)Reviewed 4 November 202627 issues · 80 checks
This review found 27 issues worth fixing on furbo.com, 5 of them high impact, across 80 checks. The most urgent: no social proof. 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
87B- #8,157 of 117,610 reviewed websitesbeats 90%
- #4,752 of 66,923 online storesbeats 89%
- #4,611 of 61,018 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 237 ms |
| May 23, 2026 | 237 ms |
| May 30, 2026 | 238 ms |
| Jun 6, 2026 | 235 ms |
| Jun 13, 2026 | 239 ms |
| Jun 20, 2026 | 244 ms |
| Jun 27, 2026 | 246 ms |
| Jul 4, 2026 | 254 ms |
| Jul 11, 2026 | 270 ms |
| Jul 18, 2026 | 327 ms |
| Jul 25, 2026 | 366 ms |
| Aug 1, 2026 | 370 ms |
| Aug 8, 2026 | 360 ms |
| Aug 15, 2026 | 294 ms |
| Aug 22, 2026 | 276 ms |
| Aug 29, 2026 | 294 ms |
| Sep 5, 2026 | 303 ms |
| Sep 12, 2026 | 323 ms |
| Sep 19, 2026 | 308 ms |
| Sep 26, 2026 | 289 ms |
| Oct 3, 2026 | 263 ms |
| Oct 10, 2026 | 236 ms |
| Oct 17, 2026 | 235 ms |
| Oct 24, 2026 | 236 ms |
| Oct 31, 2026 | 241 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
Reduce unused JavaScript
1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
750 ms · 245 KiB4 images could be 245 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 383 ms. During a long task the page ignores taps.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 295 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
236 KiBAbout 236 KiB of CSS is downloaded but never applied on this page.
4 third-party services on the page
4 third-party services load with your homepage (VWO, Shopify and Builder and others), adding 918 KiB and 9 ms of main-thread time.
Render-blocking requests
100 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
10 KiB3 files are served with short cache lifetimes, so returning visitors download them again (10 KiB).
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
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A key visual featuring a Corgi and a cat standing next to a…”.
Time to Interactive: 8.9 s
8.9 sThe page becomes fully interactive after 8.9 s. Good is under 3.8 s.
Total Blocking Time: 296 ms
296 msScripts block taps and scrolling for 296 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 237 ms to 241 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.6 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 195 ms
195 msReal visitors wait 195 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: 487 ms
487 msReal visitors wait 487 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
An image on the first screen is lazy-loaded
NA___mini360_2_launch_mobile.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).
1 image far larger than shown
54 KiB1 image is downloaded at several times the size a phone draws it, for example US_Evergreen_Mobile.png at 1,425 px wide, shown at 390 px. Resized copies would save about 54 KiB.
About 0.5 g of CO₂ per visit
0.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.54 g of CO₂e: 65.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.9 MB in 94 requests
1.9 MBYour homepage downloads 1.9 MB in 94 requests on a phone: scripts 581 KiB (40), images 476 KiB (23) and other files 451 KiB (18). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
11 internal links, 3 external
The homepage links to 11 pages on furbo.com and 3 external pages.
6 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Stay connected with your furbabies anytime, anywhere. See, talk, and toss treats even when you're away. Furbo Nanny kee…”.
Title: 50 characters
Your title is a healthy 50 characters: “Furbo|#1 Best-selling Interactive Pet Camera Brand”.
Canonical URL set
The canonical URL is https://furbo.com/us.
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://furbo.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (708 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://furbo.com/llms.txt (4 KiB, 14 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a title
https://furbo.com/us/pages/cookie-policy, https://furbo.com/us/pages/privacy-policy and https://furbo.com/us/pages/terms-conditions all use the title “Furbo”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://furbo.com/us/pages/cookie-policy, https://furbo.com/us/pages/privacy-policy and https://furbo.com/us/pages/terms-conditions have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://furbo.com/pages/saving-lives, whose canonical is https://furbo.com/us/pages/saving-lives. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://furbo.com/us/pages/furbo-for-good, https://furbo.com/pages/saving-lives, https://furbo.com/us/pages/cookie-policy, https://furbo.com/us/pages/privacy-policy and https://furbo.com/us/pages/terms-conditions have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://furbo.com/us/pages/cookie-policy, https://furbo.com/us/pages/privacy-policy and https://furbo.com/us/pages/terms-conditions have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://furbo.com/pages/saving-lives took over 3 s to send its HTML from our server.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 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 “Minified React error #418; visit https://react.dev/errors/418?args[]= for the full message or use the non-minified dev …”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
12 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 704 words of copy
The homepage carries about 704 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop for Dog” and “Shop for Cat”.
9 calls to action
The homepage has 9 calls to action, for example “Shop for Dog”, “Shop for Cat” and “Learn more”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
12 cookies set on arrival
12Opening the homepage sets 12 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 furbo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Next.js
- E-commerce
- Shopify
- Hosting
- CloudFront
Company
- Employees
- 160
- Founded
- 2014
- Headquarters
- Seattle
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on furbo.com, including 10 speed issues, 3 SEO issues 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.