orsacu.org website review

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

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

410 KiB could be saved by minifying JavaScript.

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

8 third-party services load with your homepage (Google Tag Manager, zoom.us and Clarity and others), adding 2.7 MB and 792 ms of main-thread time.

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

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

zoom.us costs a phone 120 ms of main-thread work and 2.0 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.

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

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

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

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

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

Polyfills for old browsers add 26 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.

Your largest element takes 29.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A dog with an orsa bandana around her neck hangs out the wi…”.

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

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

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

Scripts block taps and scrolling for 586 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 2.6 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.7 MB in 106 requests on a phone: scripts 2.5 MB (38), fonts 1.4 MB (11) and images 586 KiB (14). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example image at 2,048 px wide, shown at 370 px. Resized copies would save about 109 KiB.

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

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

All page content should be contained by landmarks: 4 elements on the page fail 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.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 54 pages on orsacu.org and 9 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://orsacu.org/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://orsacu.org/loans took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://orsacu.org/_next/image?url=%2F_next%2Fstatic%2Fmedia%2FLogoFull.0mnjaskriaxij.svg&w=640&q=75.

9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CERT_VERIFIER_CHANGED”.

Chrome logged issues while loading the page (“Cookie”).

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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 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 1,398 words of visible text.

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