Website review, no card needed
gurmar.com.tr website review
Visit site (opens in a new tab)Reviewed 23 October 202649 issues · 89 checks
This review found 49 issues worth fixing on gurmar.com.tr, 24 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
55FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.3 s |
| May 9, 2026 | 4.1 s |
| May 16, 2026 | 4.1 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.5 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 5.1 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 5.3 s |
| Sep 26, 2026 | 5.3 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 4.9 s |
| Oct 17, 2026 | 5.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 485 ms |
| May 9, 2026 | 475 ms |
| May 16, 2026 | 440 ms |
| May 23, 2026 | 425 ms |
| May 30, 2026 | 361 ms |
| Jun 6, 2026 | 372 ms |
| Jun 13, 2026 | 371 ms |
| Jun 20, 2026 | 396 ms |
| Jun 27, 2026 | 394 ms |
| Jul 4, 2026 | 389 ms |
| Jul 11, 2026 | 393 ms |
| Jul 18, 2026 | 328 ms |
| Jul 25, 2026 | 322 ms |
| Aug 1, 2026 | 310 ms |
| Aug 8, 2026 | 294 ms |
| Aug 15, 2026 | 299 ms |
| Aug 22, 2026 | 293 ms |
| Aug 29, 2026 | 284 ms |
| Sep 5, 2026 | 284 ms |
| Sep 12, 2026 | 267 ms |
| Sep 19, 2026 | 256 ms |
| Sep 26, 2026 | 264 ms |
| Oct 3, 2026 | 267 ms |
| Oct 10, 2026 | 277 ms |
| Oct 17, 2026 | 277 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
1.9 s
3.7 s
5.6 s
7.5 s
9.3 s
11.2 s
13.1 s
14.9 s
Speed
Use efficient cache lifetimes
2.0 s · 15.0 MB367 files are served with short cache lifetimes, so returning visitors download them again (15.0 MB).
Reduce unused JavaScript
6.1 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.1 s faster on a phone.
Document request latency
2.0 s · 421 KiBThe HTML itself could arrive about 2.0 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
2.0 sReduce initial server response time. Google estimates savings of 2.0 s on a phone.
13,157 HTML elements
The page has 13,157 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 12.4 s
A phone's processor spends 12.4 s on main-thread work while loading, 7.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 18
18/100Your mobile performance score is 18. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Server response: 2.1 s
2.1 sYour server takes 2.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Improve image delivery
350 ms · 3.2 MB39 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 2.2 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google/Doubleclick Ads and others), adding 15.3 MB and 532 ms of main-thread time.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 14.8 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
490 ms · 144 KiBAbout 144 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 490 ms faster on a phone.
Google Tag Manager adds 342 ms
342 msGoogle Tag Manager costs a phone 342 ms of main-thread work and 196 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.
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
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.4 s
4.4 sReal visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 13.3 s
13.3 sThe first text or image appears after 13.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 20.1 s
20.1 sYour largest element takes 20.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CampaignImage”. Most of its time is resource load delay (10.8 s).
Speed Index: 23.5 s
23.5 sVisually, the page fills in at 23.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 7.6 s
7.6 sScripts block taps and scrolling for 7.6 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 22.1 s
22.1 sThe page becomes fully interactive after 22.1 s. Good is under 3.8 s.
Real-user INP: 277 ms
277 msReal visitors wait 277 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.166
0.166The layout shifts by 0.166 while loading, so content jumps under the reader's thumb. Good is under 0.1.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.3 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user TTFB: 673 ms
673 msReal visitors wait 673 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 42% faster for real visitors
-42%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 485 ms to 277 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 17.6 MB in 415 requests
17.6 MBYour homepage downloads 17.6 MB in 415 requests on a phone: images 14.8 MB (372), scripts 2.0 MB (12) and HTML 630 KiB (1). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (34 KiB) is 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.
About 5.0 g of CO₂ per visit
4.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.99 g of CO₂e: 598.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
350 buttons without a name
350 buttons have no accessible name, so screen readers announce just “button”.
49 text elements with low contrast
49 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
26 tap targets too small
26 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 232 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
305 internal links, 0 external
The homepage links to 305 pages on gurmar.com.tr and 0 external pages.
7 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Gürmar Online, online market alışverişinde taze ürünleri hızlı teslimat ve avantajlı fiyatlarla sunar. Sanal market alı…”.
One H1 headline
Your main headline reads: “Gürmar Online | Sanal Market Alışverişi”.
Title: 39 characters
Your title is a healthy 39 characters: “Gürmar Online | Sanal Market Alışverişi”.
Canonical URL set
The canonical URL is https://gurmar.com.tr/.
Structured data in place
Structured data found: Organization and WebSite.
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://d2gyz7bkxfiwzi.cloudfront.net/seo/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
45%The HTML your server sends has 1,507 of the 3,329 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://gurmar.com.tr/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 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.
Other pages
6 pages slow to respond
https://gurmar.com.tr/clear-men-500-ml-cool-sport-fifa-sampuan-40069-p, https://gurmar.com.tr/clear-men-ronaldo-500-ml-sampuan-40068-p, https://gurmar.com.tr/colgate-gentle-clean-dis-fircasi-2-1-38866-p, https://gurmar.com.tr/parex-klasik-yesil-duz-bulasik-sungeri-5li-20968-p, https://gurmar.com.tr/bulasik-sungeri-oluklu-5-adet-20986-p and https://gurmar.com.tr/fairy-bulasik-makinesi-fresh-tablet-30-adet-40364-p took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 150 found) and read each the way a search engine does.
7 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
29 small tap targets
29 of 131 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: the server responded with a status of 404 ()”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
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.
Thin social proof
Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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.
About 3,329 words of copy
The homepage carries about 3,329 words of visible text.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
5 cookies set on arrival
5Opening the homepage sets 5 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 gurmar.com.tr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on gurmar.com.tr, including 27 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.