orbisfn.com website review

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

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

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

Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

1 file is served with short cache lifetimes, so returning visitors download them again (189 KiB).

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

About 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

6 third-party services load with your homepage (Hubspot, Google Tag Manager and Google Fonts and others), adding 523 KiB and 228 ms of main-thread time.

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

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.

3 KiB could be saved by minifying CSS.

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 627 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies on our website to give you the most relevant…”. Most of its time is element render delay (2.4 s).

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

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

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

Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 8.7 MB in 92 requests on a phone: media 6.2 MB (2), fonts 1.4 MB (9) and scripts 773 KiB (33). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (84 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Required ARIA attributes must be provided: 2 elements on the page fail this check, rated critical by axe-core.

Elements must only use permitted ARIA attributes: 10 elements on the page fail this check, rated serious by axe-core.

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

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

4 images have no alt text, which hurts accessibility and image search.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 16 characters: “Home - ViewTrade”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“A Wealth” and “Of Possibilities”). One clear main headline is easier for people and search engines.

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

The homepage links to 97 pages on orbisfn.com and 10 external pages.

https://www.viewtrade.com/author/tony, https://www.viewtrade.com/author/wirason, https://www.viewtrade.com/author/laksh and https://www.viewtrade.com/author/teaney have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.viewtrade.com/ai-access-and-the-future-of-global-investing, whose canonical is https://www.viewtrade.com/in-the-news/ai-access-and-the-future-of-global-investing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.viewtrade.com/author/tony, https://www.viewtrade.com/author/wirason, https://www.viewtrade.com/author/laksh and https://www.viewtrade.com/author/teaney have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.viewtrade.com/author/tony, https://www.viewtrade.com/our-services, https://www.viewtrade.com/our-clients, https://www.viewtrade.com/for-developers and https://www.viewtrade.com/author/laksh took over 3 s to send their HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Unexpected token ':'”.

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 857 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 16 cookies (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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.