Website review, no card needed
ugur.com.tr website review
Visit site (opens in a new tab)Reviewed 28 October 202639 issues · 80 checks
This review found 39 issues worth fixing on ugur.com.tr, 14 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 105 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 105 ms |
| Oct 24, 2026 | 107 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 JavaScript
1.2 s · 361 KiBAbout 361 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 92). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 574 KiB11 images could be 574 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
650 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
4 third-party services on the page
4 third-party services load with your homepage (ZenDesk, tsoftapps.com and Google Fonts and others), adding 2.4 MB and 387 ms of main-thread time.
ZenDesk adds 383 ms
383 msZenDesk costs a phone 383 ms of main-thread work and 473 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.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 883 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,622 HTML elements
The page has 2,622 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
tsoftstatic.com adds 0 ms
0 mstsoftstatic.com costs a phone 0 ms of main-thread work and 1.9 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.
Reduce unused CSS
280 ms · 25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.
Minify JavaScript
26 KiB26 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 92 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.
Use efficient cache lifetimes
8 KiB3 files are served with short cache lifetimes, so returning visitors download them again (8 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.
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: 7 ms
7 msYour server sent the HTML in 7 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.
Largest Contentful Paint: 7.9 s
7.9 sYour largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 9.8 s
9.8 sThe page becomes fully interactive after 9.8 s. Good is under 3.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.21
0.21For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.23
0.23The layout shifts by 0.23 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 105 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 179 ms
179 msScripts block the page for only 179 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
10yrs.svg weighs 790 KiB. On a phone connection a single image that size takes seconds.
3 images far larger than shown
811 KiB3 images are downloaded at several times the size a phone draws them, for example 10yrs.svg at 1,080 px wide, shown at 40 px. Resized copies would save about 811 KiB.
Page weight: 2.7 MB in 70 requests
2.7 MBYour homepage downloads 2.7 MB in 70 requests on a phone: images 1.9 MB (34), scripts 655 KiB (24) and fonts 55 KiB (2). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
slider-320px-x-456px-mobil-1.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (202 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.
1 image below the first screen load straight away
1 image further down the page (57 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 91.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
23 images without alt text
23 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
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.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 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.
247 internal links, 15 external
The homepage links to 247 pages on ugur.com.tr and 15 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Uğur buzdolabı, derin dondurucu, çamaşır makinesi, kurutma makinesi, bulaşık makinesi, klima ve diğer ev teknolojilerin…”.
Title: 45 characters
Your title is a healthy 45 characters: “Uğur Beyaz Eşya Modelleri ve Fiyatları | Uğur”.
Canonical URL set
The canonical URL is https://ugur.com.tr/.
Structured data in place
Structured data found: 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.
XML sitemap found
Your XML sitemap is reachable at https://ugur.com.tr/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,150 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://ugur.com.tr/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://ugur.com.tr/sepet has no <title>, so Google invents the link text in results.
1 page points its canonical at the homepage
https://ugur.com.tr/anasayfa 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.
2 pages share a title
/ and https://ugur.com.tr/anasayfa all use the title “Uğur Beyaz Eşya Modelleri ve Fiyatları | Uğur”. 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://ugur.com.tr/sepet has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://ugur.com.tr/derin-dondurucu, https://ugur.com.tr/anasayfa, https://ugur.com.tr/kampanyalar-1780470545206, https://ugur.com.tr/sepet, https://ugur.com.tr/dikey-derin-dondurucu and https://ugur.com.tr/yatay-derin-dondurucu and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 85 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
122 of 144 tappable elements near the top are at least 24 px.
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 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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 780 words of copy
The homepage carries about 780 words of visible text.
1 checks passed
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
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.
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 ugur.com.tr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on ugur.com.tr, including 18 speed issues, 1 SEO issue and 5 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.