oriux.com website review

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

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

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

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

2 images could be 219 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 200 ms).

3 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Google Analytics), adding 207 KiB and 150 ms of main-thread time.

About 72 KiB of JavaScript is downloaded but never used on this page.

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

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 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CREATING SOLUTIONS FOR TRAFFIC SAFETY & MOBILITY View Produ…”.

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

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

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

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 17.6 MB in 112 requests on a phone: media 10.0 MB (2), images 6.2 MB (20) and fonts 817 KiB (5). Under 2 MB keeps phones on slow connections fast.

9 images weigh 5.7 MB together. On a phone connection a single image that size takes seconds.

10 images (5.8 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.

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

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

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

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

The homepage links to 112 pages on oriux.com and 3 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description 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.

https://oriux.com/about-us, https://oriux.com/product-category/cabinets, https://oriux.com/products/sg-1000-nema-mmu2-and-conflict-monitor, https://oriux.com/products/biu-bus-interface-unit-oriux, https://oriux.com/products/nema-cabinet-power-supply and https://oriux.com/products/central-business-destrict-cbd-cabinet and 6 others took over 3 s to send their HTML from our server.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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.

The homepage carries about 368 words of visible text.

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