Website review, no card needed
gh.uz website review
Visit site (opens in a new tab)Reviewed 4 November 202619 issues · 59 checks
This review found 19 issues worth fixing on gh.uz, 7 of them high impact, across 59 checks. The most urgent: fails Core Web Vitals for real visitors. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 259 ms |
| May 23, 2026 | 253 ms |
| May 30, 2026 | 245 ms |
| Jun 6, 2026 | 253 ms |
| Jun 13, 2026 | 249 ms |
| Jun 20, 2026 | 251 ms |
| Jun 27, 2026 | 253 ms |
| Jul 4, 2026 | 253 ms |
| Jul 11, 2026 | 265 ms |
| Jul 18, 2026 | 266 ms |
| Jul 25, 2026 | 271 ms |
| Aug 1, 2026 | 268 ms |
| Aug 8, 2026 | 264 ms |
| Aug 15, 2026 | 271 ms |
| Aug 22, 2026 | 278 ms |
| Aug 29, 2026 | 282 ms |
| Sep 5, 2026 | 278 ms |
| Sep 12, 2026 | 272 ms |
| Sep 19, 2026 | 270 ms |
| Sep 26, 2026 | 283 ms |
| Oct 3, 2026 | 288 ms |
| Oct 10, 2026 | 297 ms |
| Oct 17, 2026 | 293 ms |
| Oct 24, 2026 | 272 ms |
| Oct 31, 2026 | 256 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
Speed
Reduce unused CSS
176 KiBAbout 176 KiB of CSS is downloaded but never applied on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Improve image delivery
101 KiB1 image could be 101 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
43 KiB8 files are served with short cache lifetimes, so returning visitors download them again (43 KiB).
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.
3 checks passed
Mobile performance score: 97
97/100Your mobile performance score is 97. That is in Google's “good” band (90 and up).
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 22 ms of it running JavaScript. That is comfortably low.
Server response: 222 ms
222 msYour server sent the HTML in 222 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.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 263 ms
263 msReal visitors wait 263 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 259 ms to 256 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 609 ms
609 msReal visitors wait 609 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 101 ms
101 msScripts block the page for only 101 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
First Contentful Paint: 1.0 s
1.0 sThe first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 1.0 s
1.0 sYour largest element renders in 1.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Golden House и APEX BANK объявили о стратегическом партнерс…”.
Time to Interactive: 1.2 s
1.2 sThe page is fully interactive after 1.2 s.
Images and page weight
About 0.1 g of CO₂ per visit
0.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.13 g of CO₂e: 15.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 463 KiB in 14 requests
463 KiBYour homepage downloads 463 KiB in 14 requests on a phone: stylesheets 181 KiB (1), fonts 129 KiB (2) and images 117 KiB (5). That is a lean page.
Accessibility
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
16 links without text
16 links have no text or label, so screen readers cannot say where they go.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
153 internal links, 7 external
The homepage links to 153 pages on gh.uz and 7 external pages.
7 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Golden House — Искусство создавать! Мы формируем облик столицы, создавая современные жилые комплексы. Новостройки в Таш…”.
Title: 61 characters
Your title is a healthy 61 characters: “Новостройки в Ташкенте от Golden House — Искусство создавать!”.
Canonical URL set
The canonical URL is https://gh.uz/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://gh.uz/sitemap_index.xml.
AI search readiness
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
1 page points its canonical at the homepage
https://gh.uz/author/adm1n declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
1 linked page hidden from search
https://gh.uz/projects/commercial is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://gh.uz/author/adm1n all use the title “Новостройки в Ташкенте от Golden House — Искусство создавать!”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://gh.uz/news/vash-noviy-dom-nasha-zabota has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://gh.uz/projects/commercial, https://gh.uz/vacancies, https://gh.uz/uz and https://gh.uz/author/adm1n have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://gh.uz/projects and https://gh.uz/company took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 33 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 console errors
4 errors were logged to the browser console during Google's test (“Failed to load resource: net::ERR_TIMED_OUT”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 204 words
The homepage has only about 204 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
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 gh.uz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Arsenal D
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on gh.uz, including 5 speed issues, 1 SEO issue 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.