orionlending.com website review

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.4 s faster on a phone.

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

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

12 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google CDN, website-files.com and tomnx.com and others), adding 12.1 MB and 1.1 s of main-thread time.

website-files.com costs a phone 137 ms of main-thread work and 10.3 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.

Google CDN costs a phone 548 ms of main-thread work and 1.1 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.

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

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

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

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

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

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

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

16 KiB could be saved by minifying CSS.

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

Your largest element takes 17.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “YOU’RE NOT JUST ANOTHER BROKER. WE’RE NOT JUST ANOTHER LEND…”.

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

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

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

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

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

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

Your homepage downloads 13.1 MB in 130 requests on a phone: images 10.1 MB (57), scripts 2.1 MB (31) and other files 366 KiB (14). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example 6a7a3ddebe6c4e76b1f559d4_4,380 Days of Serving the Broker Co at 2,250 px wide, shown at 140 px. Resized copies would save about 1.9 MB.

6a7a3ddebe6c4e76b1f559d4_4,380 Days of Serving the Broker Co weighs 500 KiB. On a phone connection a single image that size takes seconds.

6 images (2.1 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.

6acf8389ff6c9794787ba0e2_No Limit-Financed Properties- Web S is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

2 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

1 element hidden from screen readers can still receive keyboard focus.

<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: 14 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.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

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

There are 15 <h1> headlines (“LET'S STAY CONNECTED!”, “WE’RE NOT JUST ANOTHER LENDER.™” and “”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 71 pages on orionlending.com and 125 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://www.orionlending.com/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://www.orionlending.com/qrg has no meta description, so Google writes the search snippet from whatever text it finds.

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

10 images failed to load on a phone, for example https://www.orionlending.com/.

6 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Your longest form asks for 16 fields (3 required). Every extra field lowers completion.

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

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

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 2,000 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, 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 5 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.