Website review, no card needed
clockwork.com.tr website review
Visit site (opens in a new tab)Reviewed 19 October 202622 issues · 89 checks
This review found 22 issues worth fixing on clockwork.com.tr, 7 of them high impact, across 89 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 183 ms |
| May 9, 2026 | 167 ms |
| May 16, 2026 | 167 ms |
| May 23, 2026 | 160 ms |
| May 30, 2026 | 176 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 180 ms |
| Jun 27, 2026 | 155 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 164 ms |
| Jul 18, 2026 | 156 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 181 ms |
| Aug 15, 2026 | 176 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 168 ms |
| Sep 5, 2026 | 168 ms |
| Oct 10, 2026 | 202 ms |
| Oct 17, 2026 | 189 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
clockwork.com.tr does not allow embedding, so this is Google's rendering of the page.
Speed
Mobile performance score: 88
88/100Your mobile performance score is 88 (desktop: 93). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 207 KiBAbout 207 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 198 ms
198 msGoogle Tag Manager costs a phone 198 ms of main-thread work and 312 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, efilli.com and Cloudflare and others), adding 472 KiB and 273 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 153 KiB6 files are served with short cache lifetimes, so returning visitors download them again (153 KiB).
Legacy JavaScript
200 ms · 24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 119 ms. During a long task the page ignores taps.
Improve image delivery
29 KiB2 images could be 29 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 470 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 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 TTFB: 931 ms
931 msReal visitors wait 931 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 6.2 s
6.2 sThe page becomes fully interactive after 6.2 s. Good is under 3.8 s.
Largest Contentful Paint: 3.3 s
3.3 sYour largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AKILLICA”.
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 183 ms to 189 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
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.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 113 ms
113 msScripts block the page for only 113 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.034
0.034The layout barely moves while loading (CLS 0.034, good is under 0.1).
Images and page weight
Page weight: 6.8 MB in 45 requests
6.8 MBYour homepage downloads 6.8 MB in 45 requests on a phone: media 5.7 MB (1), scripts 700 KiB (20) and fonts 207 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 1.9 g of CO₂ per visit
1.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.93 g of CO₂e: 231.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
38 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: 38 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
37 internal links, 6 external
The homepage links to 37 pages on clockwork.com.tr and 6 external pages.
8 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Tasarımın gücü, teknolojinin hızı ve hikâyenin duygusuyla markalar için unutulmaz dijital deneyimler. Clockwork: akıllı…”.
One H1 headline
Your main headline reads: “AKILLICA Bİ' FİKİR”.
Title: 30 characters
Your title is a healthy 30 characters: “Akıllıca Bi’ Fikir | Clockwork”.
Canonical URL set
The canonical URL is https://www.clockwork.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.clockwork.com.tr/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
2 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes /llms.txt (32 KiB, 214 links), a plain-text guide to the site for AI tools.
Other pages
2 pages with very little text
/markalar and /projeler/kuveyt-turk-yatirim have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
1 broken link to your own pages
1 link from your homepage to your own site is broken, for example https://www.clockwork.com.tr/cdn-cgi/l/email-protection (404).
No HSTS header
No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
5 checks passed
Served over HTTPS
The homepage is served over HTTPS (clockwork.com.tr).
Valid certificate (89 days left)
The certificate from Google Trust Services · WE1 verifies for clockwork.com.tr and is valid for another 89 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
http:// redirects to https
http://clockwork.com.tr redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
Domain and trust
No CAA record
clockwork.com.tr has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
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.
Local business without LocalBusiness data
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.
Only about 146 words
The homepage has only about 146 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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
4 checks passed
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 7 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Email authentication
Email authentication score: 90/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: quarantine
DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 a include:spf-westeu.emailsignatures365.com include:spf.mailjet.com include:spf.protection.outlook.com -all”.
DKIM signing found
A DKIM key is published (selector “selector1” and “selector2”), so receivers can verify mail really came from you.
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.
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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This free review found 22 issues on clockwork.com.tr, including 8 speed issues and 4 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.