businet.dev website review

32 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.

About 422 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.2 s faster on a phone.

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

Reduce initial server response time. Google estimates savings of 718 ms on a phone.

105 files are served with short cache lifetimes, so returning visitors download them again (314 KiB).

The HTML itself could arrive about 700 ms sooner: redirects, a slow server response or missing compression delay everything after it.

65 KiB could be saved by minifying CSS.

5 images could be 306 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

A phone's processor spends 2.4 s on main-thread work while loading, 927 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your server takes 818 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

About 206 KiB of JavaScript is downloaded but never used on this page.

5 third-party services load with your homepage (Google Tag Manager, Facebook and Google Fonts and others), adding 410 KiB and 149 ms of main-thread time.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

4 long tasks block the main thread while loading, the longest for 81 ms. During a long task the page ignores taps.

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Visually, the page fills in at 14.5 s (Speed Index). Good is under 3.4 s.

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tu Socio en Desarrollo de Software de”. Most of its time is element render delay (5.0 s).

The first text or image appears after 4.2 s on a phone. Good is under 1.8 s.

The page becomes fully interactive after 6.8 s. Good is under 3.8 s.

2 images have no width and height attributes, so the layout jumps as each one loads.

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.

Your homepage downloads 2.7 MB in 118 requests on a phone: fonts 740 KiB (10), images 728 KiB (17) and scripts 717 KiB (52). Under 2 MB keeps phones on slow connections fast.

5 images (237 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.

By the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 90.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 link inside paragraphs relies on colour alone to stand out.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

10 visible links have no text or label, so screen readers cannot say where they go.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 67 pages on businet.dev and 12 external pages.

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.

There is no https://businet.dev/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.

https://businet.dev/Home and https://businet.dev/home 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.

/, https://businet.dev/Home and https://businet.dev/home all use the title “Businet – Software para empresas en Panamá”. Search engines can't tell which page to show for a search, so each competes with the others.

https://businet.dev/nosotros, https://businet.dev/service/desarrollo-de-software, https://businet.dev/service/blockchain, https://businet.dev/service/it-staff, https://businet.dev/achievements and https://businet.dev/cita and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://businet.dev/nosotros, https://businet.dev/service/desarrollo-de-software, https://businet.dev/service/blockchain, https://businet.dev/service/it-staff, https://businet.dev/achievements and https://businet.dev/cita and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://businet.dev/cita and https://businet.dev/contacto 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.

https://businet.dev/nosotros, https://businet.dev/service/desarrollo-de-software, https://businet.dev/service/blockchain, https://businet.dev/service/it-staff, https://businet.dev/achievements and https://businet.dev/cita and 2 others took over 3 s to send their HTML from our server.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.calendly.com/assets/external/widget.css' from origin 'https://businet.dev' …”.

1 image is served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 238 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.

Opening the homepage sets 10 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.