ozkatyres.com website review

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

3 images could be 385 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

Google CDN costs a phone 1.0 s of main-thread work and 1.9 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.

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

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

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

7 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Maps and others), adding 4.0 MB and 1.5 s of main-thread time.

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

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

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

Google Maps costs a phone 237 ms of main-thread work and 463 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.

digitaloceanspaces.com costs a phone 0 ms of main-thread work and 1.2 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.

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

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

Your largest element takes 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Özka Lastik”.

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

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

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

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

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

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

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 5.6 MB in 87 requests on a phone: scripts 2.8 MB (22), images 1.5 MB (34) and other files 813 KiB (13). Under 2 MB keeps phones on slow connections fast.

NUmNTmQsh5bzRDSrC2TbvFb1OVarTlWsR8rE9oXA.jpg weighs 582 KiB. On a phone connection a single image that size takes seconds.

2 images (667 KiB) 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 1.58 g of CO₂e: 190.0 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”.

3 dropdowns have no label.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

29 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 66 characters: “Özka Tires, the leading brand in Agricultural and Industrial Tires”. 70 to 160 characters is enough to sell the click.

6 links have no real href, so search engines can't follow them.

The homepage links to 95 pages on ozkatyres.com and 16 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://ozkatires.us/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://ozkatires.us/us-us/policies, https://ozkatires.us/us-us/r-d-center, https://ozkatires.us/us-us/personal-data-protection-law and https://ozkatires.us/us-us/tbr have no meta description, so Google writes the search snippet from whatever text it finds.

https://ozkatires.us/us-us/tire-information, https://ozkatires.us/us-us/history, https://ozkatires.us/us-us/policies, https://ozkatires.us/us-us/r-d-center, https://ozkatires.us/us-us/personal-data-protection-law and https://ozkatires.us/us-us/news-from-ozka and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.8.1/css/all.css' from origin 'https://ozkatires.us…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Requests the geolocation permission on page load.

Large scripts ship without source maps.

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

Your longest form asks for 16 fields (0 required). Every extra field lowers completion.

The homepage shows no opening hours. If customers visit or call, show when.

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

Opening the homepage sets 4 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.