orrgroup.com website review

110 files are served with short cache lifetimes, so returning visitors download them again (7.5 MB).

49 images could be 9.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

YouTube costs a phone 3.1 s of main-thread work and 15.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

About 6.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

8 third-party services load with your homepage (YouTube, Google CDN and Google Tag Manager and others), adding 17.0 MB and 4.1 s of main-thread time.

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

Google CDN costs a phone 517 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.

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

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

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

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

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

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.

Your largest element takes 23.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Drawing of a team building a 3D puzzle of the globe”.

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

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

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

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

The layout shifts by 0.25 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 87 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 28.9 MB in 326 requests on a phone: scripts 14.8 MB (93), images 10.6 MB (66) and HTML 1.3 MB (21). Under 2 MB keeps phones on slow connections fast.

12 images weigh 6.7 MB together. On a phone connection a single image that size takes seconds.

39 images (10.0 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.

[email protected] 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).

4 images are downloaded at several times the size a phone draws them, for example [email protected] at 1,236 px wide, shown at 318 px. Resized copies would save about 359 KiB.

8 images further down the page (651 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 8.19 g of CO₂e: 983.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

30 elements have a tabindex above 0, which scrambles the keyboard order.

Form elements should have a visible label: 3 elements on the page fail this check, rated serious by axe-core.

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

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

The homepage links to 102 pages on orrgroup.com and 5 external pages.

robots.txt blocks Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

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

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

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

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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 13 cookies, 1 of them by other companies (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.