Website review, no card needed
guncelozturk.com website review
Visit site (opens in a new tab)Reviewed 20 November 202624 issues · 74 checks
This review found 24 issues worth fixing on guncelozturk.com, 14 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.6 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.6 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.7 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.4 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.5 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.8 s |
| Oct 31, 2026 | 4.8 s |
| Nov 7, 2026 | 4.9 s |
| Nov 14, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 97 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 100 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 102 ms |
| Aug 8, 2026 | 100 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 97 ms |
| Aug 29, 2026 | 97 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 130 ms |
| Oct 3, 2026 | 130 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 131 ms |
| Nov 7, 2026 | 133 ms |
| Nov 14, 2026 | 133 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
0.8 s
1.7 s
2.5 s
3.4 s
4.2 s
5.0 s
5.9 s
6.7 s
Speed
Render-blocking requests
6.3 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 6.3 s.
Reduce unused CSS
5.3 s · 1.0 MBAbout 1.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Document request latency
348 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
1,855 HTML elements
The page has 1,855 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
148 KiB7 images could be 148 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 67 ms. During a long task the page ignores taps.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 54 ms of it running JavaScript. That is comfortably low.
Server response: 490 ms
490 msYour server sent the HTML in 490 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: 4.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.3 s
4.3 sReal visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 9.8 s
9.8 sThe first text or image appears after 9.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Geliştirdiği Cerrahi Teknikler 15+ Yıl Premium Deneyim Avru…”.
Speed Index: 9.8 s
9.8 sVisually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 11.0 s
11.0 sThe page becomes fully interactive after 11.0 s. Good is under 3.8 s.
Tap response (INP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 98 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.0 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 17.8 MB in 37 requests
17.8 MBYour homepage downloads 17.8 MB in 37 requests on a phone: media 15.0 MB (3), stylesheets 1.2 MB (1) and fonts 772 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 5.0 g of CO₂ per visit
5.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.04 g of CO₂e: 604.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (2 elements)
ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (38 elements)
All page content should be contained by landmarks: 38 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 102 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 4 failed. 5 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.
149 internal links, 24 external
The homepage links to 149 pages on guncelozturk.com and 24 external pages.
7 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “DRGO Clinic'in kurucusu Doç. Dr. Güncel Öztürk, İstanbul doğumlu bir Estetik, Plastik ve Rekonstrüktif Cerrahi uzmanıdı…”.
Title: 59 characters
Your title is a healthy 59 characters: “DRGO Doç. Dr. Güncel Öztürk : En İyi Burun Estetiği Doktoru”.
Canonical URL set
The canonical URL is https://www.guncelozturk.com/.
Structured data in place
Structured data found: Article, ImageObject, MedicalClinic, Organization and Person.
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://www.guncelozturk.com/sitemap_index.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,241 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.guncelozturk.com/llms.txt (59 KiB, 101 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
8 pages slow to respond
https://www.guncelozturk.com/burun-estetigi, https://www.guncelozturk.com/push-down-rinoplasti, https://www.guncelozturk.com/3d-burun-estetigi, https://www.guncelozturk.com/finesse-burun-estetigi, https://www.guncelozturk.com/endoskopik-burun-estetigi-ameliyati and https://www.guncelozturk.com/kompozit-burun-estetigi and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 102 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
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
15 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 26 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 174 words
The homepage has only about 174 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call”.
1 call to action
The homepage has 1 call to action, for example “Call”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
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 guncelozturk.com, 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
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on guncelozturk.com, including 15 speed issues, 1 SEO issue and 2 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.