Website review, no card needed
butterflymx.com website review
Visit site (opens in a new tab)Reviewed 26 October 202639 issues · 88 checks
This review found 39 issues worth fixing on butterflymx.com, 20 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 6.0 s |
| Jun 27, 2026 | 6.5 s |
| Jul 4, 2026 | 6.9 s |
| Jul 11, 2026 | 7.2 s |
| Jul 18, 2026 | 7.4 s |
| Jul 25, 2026 | 7.6 s |
| Aug 1, 2026 | 7.6 s |
| Aug 8, 2026 | 7.3 s |
| Aug 15, 2026 | 6.9 s |
| Aug 22, 2026 | 5.4 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 5.1 s |
| Sep 26, 2026 | 5.0 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.7 s |
| Oct 24, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 112 ms |
| May 16, 2026 | 114 ms |
| May 23, 2026 | 114 ms |
| May 30, 2026 | 118 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 125 ms |
| Jun 20, 2026 | 173 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 227 ms |
| Jul 11, 2026 | 243 ms |
| Jul 18, 2026 | 243 ms |
| Jul 25, 2026 | 254 ms |
| Aug 1, 2026 | 243 ms |
| Aug 8, 2026 | 224 ms |
| Aug 15, 2026 | 206 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 173 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 195 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 208 ms |
| Oct 10, 2026 | 209 ms |
| Oct 17, 2026 | 212 ms |
| Oct 24, 2026 | 214 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.5 s
1.0 s
1.5 s
1.9 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Reduce unused JavaScript
1.8 s · 329 KiBAbout 329 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.9 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 33
33/100Your mobile performance score is 33 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
750 ms · 147 KiBAbout 147 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 119 KiB6 files are served with short cache lifetimes, so returning visitors download them again (119 KiB).
Improve image delivery
512 KiB21 images could be 512 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 341 ms. During a long task the page ignores taps.
2,561 HTML elements
The page has 2,561 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, termly.io and New Relic and others), adding 547 KiB and 327 ms of main-thread time.
Minify JavaScript
150 ms · 36 KiB36 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
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: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.7 s
5.7 sReal visitors wait 5.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.2 s
5.2 sReal visitors see the first content after 5.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.3 s
4.3 sReal visitors wait 4.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use essential cookies to make our site work. With your c…”.
Time to Interactive: 16.0 s
16.0 sThe page becomes fully interactive after 16.0 s. Good is under 3.8 s.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Real-user INP: 262 ms
262 msReal visitors wait 262 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 88% slower for real visitors
+88%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 214 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.6 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.129
0.129The layout shifts by 0.129 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 10.5 MB in 125 requests
10.5 MBYour homepage downloads 10.5 MB in 125 requests on a phone: media 7.3 MB (3), images 1.7 MB (55) and scripts 760 KiB (32). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
https://butterflymx.com/ weighs 746 KiB. On a phone connection a single image that size takes seconds.
9 images in older formats
9 images (436 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 3.0 g of CO₂ per visit
2.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.97 g of CO₂e: 356.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 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
37 tap targets too small
37 tap targets are too small or too close together to hit reliably with a finger.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (69 elements)
All page content should be contained by landmarks: 69 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 175 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“Property access made simple®”, “Property access made simple®” and “Tenants & Residents”). One clear main headline is easier for people and search engines.
137 internal links, 15 external
The homepage links to 137 pages on butterflymx.com and 15 external pages.
7 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “ButterflyMX makes property access simple. Get video & open doors/gates on a smartphone. Easy to install & easy to use. …”.
Title: 64 characters
Your title is a healthy 64 characters: “ButterflyMX - Video Intercoms, Access Control & Security Cameras”.
Canonical URL set
The canonical URL is https://butterflymx.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://butterflymx.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://butterflymx.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,976 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
7 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 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
1 broken image
1 image failed to load on a phone, for example https://butterflymx.com/.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
31 of 37 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 28 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 899 words of copy
The homepage carries about 899 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: “GET YOUR QUOTE” and “GET YOUR FREE QUOTE”.
10 calls to action
The homepage has 10 calls to action, for example “Get your quote”, “Contact us” and “Get your free quote”.
2 short forms
2 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Termly
A consent management tool (Termly) 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 butterflymx.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
Hiring
- Hiring
- 7 open roles
- Teams
- Engineering (4), Customer Experience (2), Product (1)
- Job board
- ashby
- Careers page
- butterflymx.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on butterflymx.com, including 22 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.