Website review, no card needed
fga.com.tr website review
Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 85 checks
This review found 39 issues worth fixing on fga.com.tr, 11 of them high impact, across 85 checks. The most urgent: page weight: 15.8 MB in 101 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
75C- #76,783 of 116,321 reviewed websitesbeats 30%
- #49,513 of 66,758 online storesbeats 22%
- #1,283 of 2,660 WooCommerce storesbeats 45%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.0 s |
| May 2, 2026 | 3.9 s |
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 158 ms |
| May 2, 2026 | 156 ms |
| May 9, 2026 | 145 ms |
| May 16, 2026 | 139 ms |
| May 23, 2026 | 140 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 165 ms |
| Jun 20, 2026 | 180 ms |
| Jun 27, 2026 | 198 ms |
| Jul 4, 2026 | 191 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 157 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 157 ms |
| Aug 15, 2026 | 160 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 168 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 169 ms |
| Sep 19, 2026 | 175 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 164 ms |
| Oct 10, 2026 | 172 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
Use efficient cache lifetimes
300 ms · 956 KiB78 files are served with short cache lifetimes, so returning visitors download them again (956 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.1 MB and 916 ms of main-thread time.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 71). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 563 KiBAbout 563 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Google Tag Manager adds 410 ms
410 msGoogle Tag Manager costs a phone 410 ms of main-thread work and 492 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.
Reduce unused CSS
300 ms · 124 KiBAbout 124 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Legacy JavaScript
300 ms · 48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
340 KiB2 images could be 340 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Facebook adds 307 ms
307 msFacebook costs a phone 307 ms of main-thread work and 224 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: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,788 HTML elements
The page has 2,788 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 129 ms
129 msGoogle CDN costs a phone 129 ms of main-thread work and 347 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 226 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Render-blocking requests
50 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 50 ms.
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: 542 ms
542 msYour server sent the HTML in 542 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 FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 13.6 s
13.6 sThe page becomes fully interactive after 13.6 s. Good is under 3.8 s.
Largest Contentful Paint: 4.8 s
4.8 sYour largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 612 ms
612 msScripts block taps and scrolling for 612 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 158 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.0 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0.057
0.057The layout barely moves while loading (CLS 0.057, good is under 0.1).
Images and page weight
Page weight: 15.8 MB in 101 requests
15.8 MBYour homepage downloads 15.8 MB in 101 requests on a phone: media 12.5 MB (2), images 1.5 MB (19) and scripts 1.4 MB (48). Under 2 MB keeps phones on slow connections fast.
About 4.5 g of CO₂ per visit
4.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.47 g of CO₂e: 536.2 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 44 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Article, BreadcrumbList, ImageObject and ItemList) but with 1 problem, for example “Organization: sameAs is an empty list”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
290 internal links, 14 external
The homepage links to 290 pages on fga.com.tr and 14 external pages.
6 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Mimarlık, Mühendislik, İnşaat ve Medya Sektörünün Yazılım, Destek ve Eğitim Çözüm Ortağı. SketchUp / Lumion / Archicad …”.
One H1 headline
Your main headline reads: “Mimarlık, Mühendislik ve Medya Sektörünün Yazılım Çözüm Ortağı”.
Title: 52 characters
Your title is a healthy 52 characters: “FGA Mimarlık | 1997'den Beri Yazılım Çözüm Ortağınız”.
Canonical URL set
The canonical URL is https://fga.com.tr/.
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://fga.com.tr/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: 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 (1,031 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fga.com.tr/llms.txt (5 KiB, 47 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://fga.com.tr/youtube has no <title>, so Google invents the link text in results.
3 pages without a meta description
https://fga.com.tr/youtube, https://fga.com.tr/kategori/yazilim/pluginler and https://fga.com.tr/kategori/yazilim/gorsellestirme have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://fga.com.tr/youtube, https://fga.com.tr/urunler, https://fga.com.tr/kategori/yazilim/mimarlik-muhendislik, https://fga.com.tr/marka/archicad, https://fga.com.tr/marka/sketchup and https://fga.com.tr/marka/scia and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://fga.com.tr/marka/archicad, https://fga.com.tr/marka/idea-statica, https://fga.com.tr/marka/bluebeam, https://fga.com.tr/kategori/yazilim/pluginler, https://fga.com.tr/kategori/yazilim/gorsellestirme and https://fga.com.tr/marka/v-ray 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.
4 pages slow to respond
https://fga.com.tr/urunler, https://fga.com.tr/kategori/yazilim/mimarlik-muhendislik, https://fga.com.tr/marka/sketchup and https://fga.com.tr/marka/bluebeam took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 65 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
19 small tap targets
19 of 66 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
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 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.
Thin social proof
Social proof on the homepage: 48 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 471 words of copy
The homepage carries about 471 words of visible text.
4 checks passed
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
15 other companies contacted
Loading the homepage contacts 15 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 fga.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
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
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 fga.com.tr, including 19 speed issues, 2 SEO 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.