Website review, no card needed

orbio.world logo

orbio.world website review

Visit site (opens in a new tab)Reviewed 4 November 202627 issues · 73 checks

This review found 27 issues worth fixing on orbio.world, 6 of them high impact, across 73 checks. The most urgent: 1 text element with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.1 s672 msJun 6Oct 10716 ms
Show as table
DateReal-visitor load time (LCP)
Jun 6, 2026948 ms
Jun 13, 20261.0 s
Jul 18, 2026739 ms
Oct 10, 2026716 ms
Real-visitor tap response (INP)75th percentile, phones
95 ms75 msJun 6Oct 1077 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 202693 ms
Jun 13, 202689 ms
Jul 18, 202679 ms
Oct 10, 202677 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

Full-page screenshot of orbio.world (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. orbio.world at 0.4 s0.4 s
  2. orbio.world at 0.8 s0.8 s
  3. orbio.world at 1.1 s1.1 s
  4. orbio.world at 1.5 s1.5 s
  5. orbio.world at 1.9 s1.9 s
  6. orbio.world at 2.3 s2.3 s
  7. orbio.world at 2.6 s2.6 s
  8. orbio.world at 3.0 s3.0 s

Speed

7 to fix75
  • Improve image delivery

    150 ms · 1.4 MB

    17 images could be 1.4 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Framer CDN, Google Tag Manager and Hotjar and others), adding 2.4 MB and 1.0 s of main-thread time.

  • Framer CDN adds 834 ms

    834 ms

    Framer CDN costs a phone 834 ms of main-thread work and 2.2 MB 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.

  • Mobile performance score: 75

    75/100

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

  • Reduce unused JavaScript

    450 ms · 200 KiB

    About 200 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.

  • Main-thread work: 2.2 s

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

  • 1,593 HTML elements

    The page has 1,593 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    150 ms · 23 KiB

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

  • 6 long tasks on the main thread

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

  • 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.

  • Forced reflow

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

1 checks passed
  • Server response: 35 ms

    35 ms

    Your server sent the HTML in 35 ms, well inside Google's 600 ms guideline.

Core Web Vitals

2 to fix67
  • Largest Contentful Paint: 8.1 s

    8.1 s

    Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 11.8 s

    11.8 s

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

  • 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.

6 checks passed
  • Tap response (INP) got 14% faster for real visitors

    -14%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 93 ms to 77 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 26% faster for real visitors

    -26%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 2.3 s

    2.3 s

    Visually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 99 ms

    99 ms

    Scripts block the page for only 99 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.005

    0.005

    The layout barely moves while loading (CLS 0.005, good is under 0.1).

  • First Contentful Paint: 1.0 s

    1.0 s

    The first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.

Images and page weight

2 to fix78
  • Page weight: 2.5 MB in 69 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 69 requests on a phone: images 1.8 MB (29), scripts 544 KiB (29) and fonts 102 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 11 images below the first screen load straight away

    11 images further down the page (302 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.7 g of CO₂ per visit

    0.70 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 7185
  • 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.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (36 elements)

    All page content should be contained by landmarks: 36 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 9 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h1 → h3, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 78 images in the HTML carry an alt attribute.

  • 19 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 25 WCAG 2.2 A/AA and best-practice rules on the phone render: 19 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 6959
  • Page is set to noindex

    The robots meta tag says “noindex”: Google is told not to list this page at all.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • No structured data

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

  • 8 H1 headlines

    There are 8 <h1> headlines (“We build”, “We build” and “online”). One clear main headline is easier for people and search engines.

  • 29 internal links, 3 external

    The homepage links to 29 pages on orbio.world and 3 external pages.

6 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “A direct-to-consumer online retailer with a vision to create brands that make a difference. Brands that make life a lit…”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Orbio World – We build online retail brands”.

  • Canonical URL set

    The canonical URL is https://orbio.world/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://orbio.world/sitemap.xml.

AI search readiness

1 to fix88
  • 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://orbio.world/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 (1,016 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://orbio.world/candidates-privacy and https://orbio.world/contact-us use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://orbio.world/who-we-are, https://orbio.world/careers, https://orbio.world/affiliates, https://orbio.world/social, https://orbio.world/candidates-privacy and https://orbio.world/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 internal pages checked

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

6 checks passed
  • Linked pages load

    All 7 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • 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 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • No direct contact details

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

  • No form on the homepage

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

  • 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 454 words of copy

    The homepage carries about 454 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN US JOIN US”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Join OrbioJoin Orbio”, “Join UsJoin Us” and “CONTACT US”.

  • Social proof on the page

    Social proof on the homepage: 3 trust badges and “0.0M CUSTOMERS”.

  • Analytics in place

    Analytics detected: Google Analytics and Hotjar.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 9 other companies contacted

    Loading the homepage contacts 9 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 orbio.world, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
Framer
Analytics
Google Analytics | Hotjar
Hosting
Framer

Hiring

Hiring
1 open role
Job board
smartrecruiters

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on orbio.world, including 9 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25