orucase.com website review

About 710 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

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

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

8 third-party services load with your homepage (ZenDesk, Klaviyo and Shopify and others), adding 2.9 MB and 1.3 s of main-thread time.

About 111 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.

ZenDesk costs a phone 416 ms of main-thread work and 478 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.

Klaviyo costs a phone 374 ms of main-thread work and 645 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.

Shopify costs a phone 313 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.

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

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

monkcommerce.app costs a phone 209 ms of main-thread work and 602 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.

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

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

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

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

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

6 KiB could be saved by minifying CSS.

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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “7-DSC_3404-4.jpg”.

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

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

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

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

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

Your homepage downloads 6.7 MB in 646 requests on a phone: scripts 2.5 MB (268), images 2.0 MB (46) and other files 1.6 MB (302). Under 2 MB keeps phones on slow connections fast.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

6 images have no alt text, which hurts accessibility and image search.

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

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

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

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

There are 4 <h1> headlines (“”, “Bike Travel Cases Built to Protect. Engineered to…” and “Cycling Accessories from the Makers of the Sentin…”). One clear main headline is easier for people and search engines.

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

The homepage links to 97 pages on orucase.com and 8 external pages.

https://www.orucase.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.orucase.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.orucase.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.orucase.com/blogs/news and https://www.orucase.com/pages/our-story use the same meta description. A description written for each page earns more clicks.

https://www.orucase.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “oaiq is not defined”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 61 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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