Website review, no card needed
byonyks.com website review
Visit site (opens in a new tab)Reviewed 24 October 202628 issues · 79 checks
This review found 28 issues worth fixing on byonyks.com, 13 of them high impact, across 79 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.3 s |
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 3.7 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.7 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.6 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 5.9 s |
| Sep 26, 2026 | 5.8 s |
| Oct 3, 2026 | 5.8 s |
| Oct 10, 2026 | 5.9 s |
| Oct 17, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 84 ms |
| May 9, 2026 | 89 ms |
| Jun 6, 2026 | 118 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 102 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 117 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 110 ms |
| Aug 29, 2026 | 110 ms |
| Sep 5, 2026 | 110 ms |
| Sep 12, 2026 | 107 ms |
| Sep 19, 2026 | 116 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 108 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 109 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
Improve image delivery
6.1 s · 1.2 MB4 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.1 s faster on a phone.
Use efficient cache lifetimes
2.0 s · 412 KiB78 files are served with short cache lifetimes, so returning visitors download them again (412 KiB).
Render-blocking requests
2.2 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Mobile performance score: 58
58/100Your mobile performance score is 58 (desktop: 72). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Legacy JavaScript
150 ms · 17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Fonts and others), adding 233 KiB and 131 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 91 ms. During a long task the page ignores taps.
Reduce unused JavaScript
73 KiBAbout 73 KiB of JavaScript is downloaded but never used 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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 409 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 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 FCP: 5.5 s
5.5 sReal visitors see the first content after 5.5 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 15.3 s
15.3 sYour largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dialysis at Home”. Most of its time is resource load delay (10.2 s).
Speed Index: 19.2 s
19.2 sVisually, the page fills in at 19.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 15.3 s
15.3 sThe page becomes fully interactive after 15.3 s. Good is under 3.8 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 84 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.3 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 48 ms
48 msScripts block the page for only 48 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.0 MB in 84 requests
3.0 MBYour homepage downloads 3.0 MB in 84 requests on a phone: images 2.3 MB (8), scripts 410 KiB (34) and fonts 169 KiB (7). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (229 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.
2 images below the first screen load straight away
2 images further down the page (209 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 102.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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
215 internal links, 5 external
The homepage links to 215 pages on byonyks.com and 5 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Dialysis at Home”.
Title: 34 characters
Your title is a healthy 34 characters: “Byonyks – A Medical Device Company”.
Canonical URL set
The canonical URL is https://byonyks.com/.
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://byonyks.com/wp-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.
No llms.txt
There is no https://byonyks.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 (955 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without a meta description
https://byonyks.com/innovation, https://byonyks.com/market, https://byonyks.com/learn, https://byonyks.com/byonyks-global, https://byonyks.com/europe and https://byonyks.com/about-us and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://byonyks.com/about-us has no <h1> headline, so visitors and search engines get no clear main topic.
11 pages slow to respond
https://byonyks.com/innovation, https://byonyks.com/market, https://byonyks.com/learn, https://byonyks.com/byonyks-global, https://byonyks.com/europe and https://byonyks.com/about-us and 5 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.
5 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
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.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 501 words of copy
The homepage carries about 501 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact”.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link 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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
5 other companies contacted
Loading the homepage contacts 5 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 byonyks.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 Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on byonyks.com, including 14 speed issues, 3 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.