orbund.com website review

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Adroll and others), adding 1.1 MB and 842 ms of main-thread time.

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

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

3 images could be 93 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

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

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

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

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

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

19 KiB could be saved by minifying JavaScript.

Desktop scores 82 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

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 5.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Use our free Trade School Compliance Readiness Assessment t…”. Most of its time is element render delay (8.2 s).

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

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

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

Your homepage downloads 2.8 MB in 178 requests on a phone: scripts 1.2 MB (34), fonts 563 KiB (5) and other files 397 KiB (51). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found (BreadcrumbList, CollectionPage, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

The homepage links to 39 pages on orbund.com and 8 external pages.

https://orbund.com/career-colleges-trade-schools, https://orbund.com/colleges-universities, https://orbund.com/continuing-education, https://orbund.com/corporate-and-government-instruction, https://orbund.com/testimonials and https://orbund.com/privacy-policy and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://orbund.com/career-colleges-trade-schools, https://orbund.com/colleges-universities, https://orbund.com/continuing-education, https://orbund.com/corporate-and-government-instruction, https://orbund.com/testimonials and https://orbund.com/privacy-policy and 1 other took over 3 s to send their HTML from our server.

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

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 885 words of visible text.

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