orbyt.tech website review

About 280 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Cookiebot and Clarity and others), adding 914 KiB and 990 ms of main-thread time.

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

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

23 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

Google Tag Manager costs a phone 467 ms of main-thread work and 508 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 3.4 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Cookiebot costs a phone 278 ms of main-thread work and 158 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.

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

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

About 14 KiB of CSS is downloaded but never applied on this page.

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.

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 visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

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

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

Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

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

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

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

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

7 tap targets are too small or too close together to hit reliably with a finger.

4 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: 1 element on the page fails this check, rated moderate by axe-core.

9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

The homepage links to 60 pages on orbyt.tech and 2 external pages.

There is no https://orbyt.tech/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 23 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://use.typekit.net/ddh3bae.css' violates the following Content Security Policy directive: "connect-…”.

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

Social proof on the homepage: 28 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

The homepage carries about 663 words of visible text.

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 (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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