orbitmedical.com website review

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

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

About 333 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and heyhalda.com and others), adding 3.0 MB and 1.5 s of main-thread time.

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

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

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

heyhalda.com costs a phone 231 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.

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

Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

3 images could be 118 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

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

Your largest element takes 28.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Find out how to get a power wheelchair for LITTLE or NO COS…”.

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

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

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

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

Your homepage downloads 5.9 MB in 492 requests on a phone: scripts 3.4 MB (374), fonts 1.0 MB (15) and images 679 KiB (21). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Go-Go-Elite-3-Wheel.jpg at 700 px wide, shown at 217 px. Resized copies would save about 21 KiB.

4 images (263 KiB) 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.68 g of CO₂e: 201.9 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.

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

2 links inside paragraphs rely on colour alone to stand out.

All page content should be contained by landmarks: 26 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.

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), 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, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://orbit-dev.successfullysmall.com/)”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

4 links have no real href, so search engines can't follow them.

The homepage links to 45 pages on orbitmedical.com and 20 external pages.

There is no https://www.orbitmedical.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.orbitmedical.com/order-process, https://www.orbitmedical.com/health_professionals, https://www.orbitmedical.com/health_professionals/how-to-order, https://www.orbitmedical.com/health_professionals/referral-forms, https://www.orbitmedical.com/health_professionals/submit-referral and https://www.orbitmedical.com/health_professionals/schedule-inservice and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.orbitmedical.com/order-process, https://www.orbitmedical.com/health_professionals and https://www.orbitmedical.com/health_professionals/referral-forms took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343128810&tm=gtm002&Ver=2&mid=59e28301-c53d-4d7c-8578-de0ea1bd7143&bo=1&sid=0dee3b10d67311f1be8d7feb893082c0&vid=0dee4f90d67311f195165760e46ac9e2&vids=1&msclkid=N&pi=9.

2 of 10 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 “Cannot read properties of undefined (reading 'call')”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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.

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

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

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