otrusa.com website review

18 images could be 983 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

Your mobile performance score is 82. Pages that score under 90 lose visitors before the first paint.

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

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

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

7 third-party services load with your homepage (Shopify, boostcommerce.io and useamp.com and others), adding 377 KiB and 116 ms of main-thread time.

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

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

13 KiB JavaScript is shipped twice across bundles.

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

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

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 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Your homepage downloads 3.1 MB in 200 requests on a phone: images 1.6 MB (42), other files 776 KiB (87) and scripts 430 KiB (47). Under 2 MB keeps phones on slow connections fast.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 10 characters: “OTRUSA.COM”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “Looking for tire for your vehicle?”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

The homepage links to 194 pages on otrusa.com and 1 external page.

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.

/collections/all-tires has no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all-products, /collections/otr-tires, /collections/agricultural-tires, /collections/industrial-tires, /collections/truck-tires and /collections/passenger-light-truck-tires use the same meta description. A description written for each page earns more clicks.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://otrusa.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

otrusa.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The page uses urgency cues (a countdown or limited-time wording).

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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