orbee.com website review

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

About 331 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

39 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Your mobile performance score is 55 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.0 MB and 822 ms of main-thread time.

Google Tag Manager costs a phone 422 ms of main-thread work and 496 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.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

Facebook costs a phone 271 ms of main-thread work and 280 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.

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

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

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.

Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Orbee unifies your data across customer and business operat…”.

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

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

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

Scripts block taps and scrolling for 444 ms in total while the page loads. Good is under 200 ms.

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

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 6.7 MB in 112 requests on a phone: images 5.6 MB (74), scripts 939 KiB (13) and fonts 99 KiB (3). Under 2 MB keeps phones on slow connections fast.

data_platform.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

18 images are downloaded at several times the size a phone draws them, for example data_platform.png at 1,920 px wide, shown at 342 px. Resized copies would save about 1.4 MB.

40 images (3.6 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.

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

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

Your title is only 5 characters: “Orbee”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.

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

No XML sitemap at https://www.orbee.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at orbee.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 165 pages on orbee.com and 5 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 /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.

We fetched 15 pages linked from your homepage (of 57 found) and read each the way a search engine does.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

Opening https://orbee.com goes through 2 redirects before the homepage loads.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

orbee.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

orbee.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

The homepage carries about 1,090 words of visible text.

DMARC is set to p=none, so mail pretending to be orbee.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 8 cookies (measured from a US location before any click).

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