Website review, no card needed
mybusybee.net website review
Visit site (opens in a new tab)Reviewed 20 October 202622 issues · 61 checks
This review found 22 issues worth fixing on mybusybee.net, 8 of them high impact, across 61 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
75CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
2.0 s · 413 KiB3 images could be 413 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 388 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
550 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused JavaScript
450 ms · 99 KiBAbout 99 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
1 checks passed
Server response: 221 ms
221 msYour server sent the HTML in 221 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BUSYBEE platform”. Most of its time is element render delay (2.5 s).
Cumulative Layout Shift: 0.383
0.383The layout shifts by 0.383 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 5.9 s
5.9 sThe page becomes fully interactive after 5.9 s. Good is under 3.8 s.
32 images without width and height
32 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 37 ms
37 msScripts block the page for only 37 ms while loading. Good is under 200 ms.
Images and page weight
3 images far larger than shown
154 KiB3 images are downloaded at several times the size a phone draws them, for example image at 1,200 px wide, shown at 390 px. Resized copies would save about 154 KiB.
2 images in older formats
2 images (150 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.
5 images below the first screen load straight away
5 images further down the page (229 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 37.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.1 MB in 46 requests
1.1 MBYour homepage downloads 1.1 MB in 46 requests on a phone: images 705 KiB (19), scripts 284 KiB (11) and fonts 88 KiB (2). That is a lean page.
Accessibility
2 checks passed
Every image has alt text
All 63 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://mybusybee.net/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at mybusybee.net/robots.txt, the first file search crawlers ask for.
30 internal links, 0 external
The homepage links to 30 pages on mybusybee.net and 0 external pages.
5 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “BUSYBEE offers superior connectivity options via SMPP or HTTP. We offer aggressive pricing for Direct Connection to Loc…”.
One H1 headline
Your main headline reads: “Your No. 1 MessagingPartner in the Philippines”.
Title: 57 characters
Your title is a healthy 57 characters: “BUSYBEE - Your No. 1 Messaging Partner in the Philippines”.
Canonical URL set
The canonical URL is https://mybusybee.net/.
Structured data in place
Structured data found: Organization.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. 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://mybusybee.net/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (588 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages are broken
Your homepage links to https://mybusybee.net/products-services/domain-hosting and https://mybusybee.net/api-manual, which answer with an error. Visitors hit a dead end and search engines drop them.
13 pages point its canonical at the homepage
https://mybusybee.net/our-clients, https://mybusybee.net/press-release, https://mybusybee.net/company, https://mybusybee.net/careers, https://mybusybee.net/partners and https://mybusybee.net/investors and 7 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
6 pages share a title
/, https://mybusybee.net/our-clients, https://mybusybee.net/press-release, https://mybusybee.net/contact, https://mybusybee.net/products-services/other-digital-services and https://mybusybee.net/webinar all use the title “BUSYBEE - Your No. 1 Messaging Partner in the Philippines”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://mybusybee.net/our-clients, https://mybusybee.net/press-release, https://mybusybee.net/contact, https://mybusybee.net/products-services/other-digital-services and https://mybusybee.net/webinar use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://mybusybee.net/press-release 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
4 checks passed
Every page has a meta description
All 13 pages that loaded have a meta description.
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 13 pages that loaded have a <title>.
Best practices
8 broken images
8 images failed to load on a phone, for example https://mybusybee.net/images/clients/logos/ayala.png.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 577 words of copy
The homepage carries about 577 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 “Get Started”.
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Get Started” and “Learn more about our story”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 48 customer or partner logos and “Trusted by 1000+ companies”.
Direct contact links
Visitors can reach you directly: 3 phone links and 4 email links.
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
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.
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 mybusybee.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on mybusybee.net, including 10 speed issues, 3 SEO issues and 1 conversion gap. 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.