Website review, no card needed
uzautomotors.com website review
Visit site (opens in a new tab)Reviewed 3 November 202655 issues · 94 checks
This review found 55 issues worth fixing on uzautomotors.com, 22 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.9 s |
| Oct 31, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 106 ms |
| May 23, 2026 | 106 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 109 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 108 ms |
| Jul 4, 2026 | 107 ms |
| Jul 11, 2026 | 106 ms |
| Jul 18, 2026 | 103 ms |
| Jul 25, 2026 | 101 ms |
| Aug 1, 2026 | 101 ms |
| Aug 8, 2026 | 100 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 105 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 106 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 102 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 98 ms |
| Oct 24, 2026 | 98 ms |
| Oct 31, 2026 | 97 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.9 s
3.8 s
5.8 s
7.7 s
9.6 s
11.5 s
13.5 s
15.4 s
Speed
Use efficient cache lifetimes
13.8 s · 31.9 MB92 files are served with short cache lifetimes, so returning visitors download them again (31.9 MB).
Improve image delivery
4.9 s · 8.0 MB20 images could be 8.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.9 s faster on a phone.
Render-blocking requests
10.4 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 10.4 s.
Reduce unused CSS
4.7 s · 728 KiBAbout 728 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.7 s faster on a phone.
Reduce unused JavaScript
3.3 s · 713 KiBAbout 713 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 444 ms. During a long task the page ignores taps.
Legacy JavaScript
350 ms · 55 KiBPolyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 850 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Jivochat adds 73 ms
73 msJivochat costs a phone 73 ms of main-thread work and 369 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.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, jivo.ru and Jivochat and others), adding 788 KiB and 476 ms of main-thread time.
Document request latency
49 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Minify CSS
26 KiB26 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 55 ms
55 msYour server sent the HTML in 55 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
First Contentful Paint: 11.3 s
11.3 sThe first text or image appears after 11.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 51.5 s
51.5 sYour largest element takes 51.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “slider photo”.
Speed Index: 23.2 s
23.2 sVisually, the page fills in at 23.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 53.5 s
53.5 sThe page becomes fully interactive after 53.5 s. Good is under 3.8 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Largest content (LCP) got 50% slower for real visitors
+50%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
48 images without width and height
48 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.172
0.172The layout shifts by 0.172 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 347 ms
347 msScripts block taps and scrolling for 347 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 106 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 100 ms
100 msReal visitors wait 100 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 798 ms
798 msReal visitors wait 798 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
40 images over 500 KB
40 images weigh 36.9 MB together. On a phone connection a single image that size takes seconds.
Page weight: 32.6 MB in 130 requests
32.6 MBYour homepage downloads 32.6 MB in 130 requests on a phone: images 30.0 MB (79), scripts 1.4 MB (22) and stylesheets 779 KiB (15). Under 2 MB keeps phones on slow connections fast.
40 images far larger than shown
28.2 MB40 images are downloaded at several times the size a phone draws them, for example 7d9c4d84974295bc50c0dfc5b1114052.png at 1,702 px wide, shown at 390 px. Resized copies would save about 28.2 MB.
40 images in older formats
40 images (36.9 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.
About 9.2 g of CO₂ per visit
9.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.25 g of CO₂e: 1109.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
16 links without text
16 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Alternative text of images should not be repeated as text (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (73 characters)
Your title is 73 characters, so Google will cut it off around 60: “UZAUTO MOTORS - MDHdagi eng yirik avtomobil ishlab chiqaruvchi kompaniya!”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (210 characters)
Your meta description is 210 characters; Google truncates after about 160, so the end of your pitch is cut.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
131 internal links, 39 external
The homepage links to 131 pages on uzautomotors.com and 39 external pages.
2 checks passed
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://uzautomotors.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://uzautomotors.com/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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (595 words), so crawlers that don't run JavaScript still read it.
Other pages
16 pages share a title
/, https://uzautomotors.com/lang/ru, https://uzautomotors.com/lang/uz, https://uzautomotors.com/lang/en, https://uzautomotors.com/treatments and https://uzautomotors.com/companies and 10 others all use the title “UZAUTO MOTORS - MDHdagi eng yirik avtomobil ishlab chiqaruvchi kompan…”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://uzautomotors.com/companies/supervisory_board, https://uzautomotors.com/companies/corporativnaya_diyatelnost, https://uzautomotors.com/companies/open_data, https://uzautomotors.com/companies/normativno_pravovye_akty, https://uzautomotors.com/companies/jamiyatning_tasdiqlangan_biznes_rejasi and https://uzautomotors.com/companies/web_site and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://uzautomotors.com/lang/ru, https://uzautomotors.com/lang/uz and https://uzautomotors.com/lang/en use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://uzautomotors.com/lang/ru, https://uzautomotors.com/lang/uz and https://uzautomotors.com/lang/en have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://uzautomotors.com/lang/en took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 90 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
60 small tap targets
60 of 92 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Unexpected token 'function'”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 363 words of copy
The homepage carries about 363 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Call-markazlari”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before 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.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
No consent tool detected
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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at uzautomotors.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Tpsuz As "Ist Telekom" Jv Llc
Company
- Founded
- 2019
- Headquarters
- Asaka
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 55 issues on uzautomotors.com, including 23 speed issues, 6 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.