Website review, no card needed
binsons.com website review
Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 91 checks
This review found 38 issues worth fixing on binsons.com, 16 of them high impact, across 91 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 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.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 94 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 97 ms |
| Jun 20, 2026 | 102 ms |
| Jun 27, 2026 | 103 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 92 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 93 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 93 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 95 ms |
| Oct 3, 2026 | 94 ms |
| Oct 10, 2026 | 93 ms |
| Oct 17, 2026 | 92 ms |
| Oct 24, 2026 | 89 ms |
| Oct 31, 2026 | 93 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.0 s
1.9 s
2.9 s
3.8 s
4.8 s
5.8 s
6.7 s
7.7 s
Speed
Improve image delivery
80.0 s · 14.9 MB7 images could be 14.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 80.0 s faster on a phone.
Render-blocking requests
4.6 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.6 s.
Reduce unused JavaScript
3.5 s · 619 KiBAbout 619 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 3.0 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, jotform.com and PageSense and others), adding 2.1 MB and 2.9 s of main-thread time.
Google Tag Manager adds 777 ms
777 msGoogle Tag Manager costs a phone 777 ms of main-thread work and 531 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
600 ms · 127 KiBAbout 127 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
550 ms · 112 KiB3 files are served with short cache lifetimes, so returning visitors download them again (112 KiB).
jotform.com adds 631 ms
631 msjotform.com costs a phone 631 ms of main-thread work and 294 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.
PageSense adds 318 ms
318 msPageSense costs a phone 318 ms of main-thread work and 79 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 319 ms. During a long task the page ignores taps.
Osano CMP adds 269 ms
269 msOsano CMP costs a phone 269 ms of main-thread work and 80 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.
vgmforbin.com adds 185 ms
185 msvgmforbin.com costs a phone 185 ms of main-thread work and 668 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.
1,826 HTML elements
The page has 1,826 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 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: 2 ms
2 msYour server sent the HTML in 2 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: 4.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 100.6 s
100.6 sYour largest element takes 100.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sanitize Your CPAP Mask in Just 3 Minutes Eliminate 99.9% o…”.
Speed Index: 20.8 s
20.8 sVisually, the page fills in at 20.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 100.9 s
100.9 sThe page becomes fully interactive after 100.9 s. Good is under 3.8 s.
First Contentful Paint: 5.5 s
5.5 sThe first text or image appears after 5.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Real-user TTFB: 861 ms
861 msReal visitors wait 861 ms for your server to start answering (75th percentile). Good is under 800 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 94 ms to 93 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 97 ms
97 msReal visitors wait 97 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.053
0.053The layout barely moves while loading (CLS 0.053, good is under 0.1).
Images and page weight
Page weight: 19.1 MB in 117 requests
19.1 MBYour homepage downloads 19.1 MB in 117 requests on a phone: images 16.6 MB (47), scripts 1.9 MB (35) and fonts 373 KiB (9). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 15.3 MB together. On a phone connection a single image that size takes seconds.
15 images in older formats
15 images (15.9 MB) 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.
20 images below the first screen load straight away
20 images further down the page (9.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.4 g of CO₂ per visit
5.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.41 g of CO₂e: 649.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
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.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (72 characters)
Your title is 72 characters, so Google will cut it off around 60: “Enroll Online for Medical Supplies | Fast Delivery Nationwide | Binson's”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
246 internal links, 12 external
The homepage links to 246 pages on binsons.com and 12 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Explore top-quality medical equipment, supplies, and services at Binson's. Discover unparalleled care at our MI, IN, an…”.
One H1 headline
Your main headline reads: “Insurance Covered Medical Equipment & Supplies | Orthotics & Prosthetic Services | Since 1953”.
Canonical URL set
The canonical URL is https://www.binsons.com/.
Structured data in place
Structured data found: Organization and WebPage.
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.binsons.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.binsons.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.
2 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 (1,278 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.binsons.com/bill-pay has no <title>, so Google invents the link text in results.
1 page without a meta description
https://www.binsons.com/bill-pay has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.binsons.com/bill-pay has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.binsons.com/bill-pay has 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.
3 pages slow to respond
https://www.binsons.com/reorder-online/cgm-supply/cgm-supply-enrollment-form, https://www.binsons.com/reorder-online/cgm-supply/cgm-reorder-form and https://www.binsons.com/reorder-online/cpap-supply took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 141 found) and read each the way a search engine does.
4 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
135 of 145 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.
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 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.
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,472 words of copy
The homepage carries about 1,472 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us” and “Shop Paptizer Now”.
24 calls to action
The homepage has 24 calls to action, for example “Contact Us”, “Login / Register” and “Shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: Osano
A consent management tool (Osano) loads with the page.
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 binsons.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
- Forbin PageBuilder 2.0
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Lightedge As
Company
- Employees
- 752
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on binsons.com, including 24 speed issues, 1 SEO issue 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.