Website review, no card needed

penguen.com.tr logo

penguen.com.tr website review

Visit site (opens in a new tab)Reviewed 21 October 202642 issues · 87 checks

This review found 42 issues worth fixing on penguen.com.tr, 17 of them high impact, across 87 checks. The most urgent: avoid multiple page redirects. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.3 s2.5 sMay 2Oct 175.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.0 s
May 9, 20262.9 s
May 16, 20263.1 s
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.3 s
Jun 13, 20264.1 s
Jun 20, 20264.7 s
Jun 27, 20265.1 s
Jul 4, 20265.3 s
Jul 11, 20265.4 s
Jul 18, 20265.4 s
Jul 25, 20265.4 s
Aug 1, 20265.5 s
Aug 8, 20265.4 s
Aug 15, 20265.7 s
Aug 22, 20265.8 s
Aug 29, 20265.7 s
Sep 5, 20265.7 s
Sep 12, 20265.5 s
Sep 19, 20265.3 s
Sep 26, 20265.4 s
Oct 3, 20265.4 s
Oct 10, 20265.4 s
Oct 17, 20265.5 s
Real-visitor tap response (INP)75th percentile, phones
177 ms117 msMay 2Oct 17155 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026134 ms
May 9, 2026124 ms
May 16, 2026142 ms
May 23, 2026154 ms
May 30, 2026157 ms
Jun 6, 2026170 ms
Jun 13, 2026142 ms
Jun 20, 2026151 ms
Jun 27, 2026156 ms
Jul 4, 2026158 ms
Jul 11, 2026161 ms
Jul 18, 2026144 ms
Jul 25, 2026147 ms
Aug 1, 2026158 ms
Aug 8, 2026153 ms
Aug 15, 2026165 ms
Aug 22, 2026155 ms
Aug 29, 2026139 ms
Sep 5, 2026148 ms
Sep 12, 2026150 ms
Sep 19, 2026138 ms
Sep 26, 2026145 ms
Oct 3, 2026136 ms
Oct 10, 2026155 ms
Oct 17, 2026155 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

Full-page screenshot of penguen.com.tr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. penguen.com.tr at 1.4 s1.4 s
  2. penguen.com.tr at 2.8 s2.8 s
  3. penguen.com.tr at 4.2 s4.2 s
  4. penguen.com.tr at 5.6 s5.6 s
  5. penguen.com.tr at 7.0 s7.0 s
  6. penguen.com.tr at 8.3 s8.3 s
  7. penguen.com.tr at 9.7 s9.7 s
  8. penguen.com.tr at 11.1 s11.1 s

Speed

6 to fix44
  • Avoid multiple page redirects

    19.8 s

    The page goes through 1 redirect before it starts loading, costing about 19.8 s. Link and advertise the final URL directly.

  • Reduce unused JavaScript

    7.7 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.7 s faster on a phone.

  • Render-blocking requests

    5.7 s

    54 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.7 s.

  • Font display

    1.6 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.6 s).

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 3.5 s

    A phone's processor spends 3.5 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Facebook, Google Tag Manager and Google Analytics and others), adding 778 KiB and 317 ms of main-thread time.

  • Use efficient cache lifetimes

    204 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (204 KiB).

  • Minify CSS

    150 ms · 10 KiB

    10 KiB could be saved by minifying CSS.

  • 14 long tasks on the main thread

    14 long tasks block the main thread while loading, the longest for 129 ms. During a long task the page ignores taps.

  • Improve image delivery

    88 KiB

    3 images could be 88 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    47 KiB

    Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

  • 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.

1 checks passed
  • Server response: 148 ms

    148 ms

    Your server sent the HTML in 148 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • 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: 5.4 s

    5.4 s

    Real visitors wait 5.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 4.3 s

    4.3 s

    Real visitors see the first content after 4.3 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 12.7 s

    12.7 s

    The first text or image appears after 12.7 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 31.7 s

    31.7 s

    Your largest element takes 31.7 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Speed Index: 15.9 s

    15.9 s

    Visually, the page fills in at 15.9 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 35.6 s

    35.6 s

    The page becomes fully interactive after 35.6 s. Good is under 3.8 s.

  • Tap response (INP) got 20% slower for real visitors

    +20%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 134 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 82% slower for real visitors

    +82%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.0 s to 5.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.204

    0.204

    The layout shifts by 0.204 while loading, so content jumps under the reader's thumb. Good is under 0.1.

3 checks passed
  • Real-user INP: 109 ms

    109 ms

    Real visitors wait 109 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 135 ms

    135 ms

    Scripts block the page for only 135 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 8.7 MB in 310 requests

    8.7 MB

    Your homepage downloads 8.7 MB in 310 requests on a phone: images 4.4 MB (64), scripts 2.6 MB (112) and fonts 992 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    saglikli-768x129.jpg 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).

  • 10 images in older formats

    10 images (866 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.

  • About 2.5 g of CO₂ per visit

    2.47 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.47 g of CO₂e: 296.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 7688
  • Certain ARIA roles must be contained by particular parents (2 elements)

    Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

  • 16 images without alt text

    16 images have no alt text, which hurts accessibility and image search.

  • 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.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails 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 main landmark (1 element)

    Document should not have more than one main 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.

  • 79 form fields without a label

    79 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8586
  • Title is short (18 characters)

    Your title is only 18 characters: “Anasayfa - Penguen”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (25 characters)

    Your meta description is only 25 characters: “Penguen Dünyasına katılın”. 70 to 160 characters is enough to sell the click.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 61 internal links, 5 external

    The homepage links to 61 pages on penguen.com.tr and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Lezzet, Sağlık ve Güven”.

  • Canonical URL set

    The canonical URL is https://www.penguen.com.tr/.

  • Structured data in place

    Structured data found: Article, FoodEstablishment, ImageObject, 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.penguen.com.tr/sitemap_index.xml.

AI search readiness

100
3 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (230 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://www.penguen.com.tr/home/ozel-markali-uretim and https://www.penguen.com.tr/yatirimci-iliskileri are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.penguen.com.tr/donmus-saglikli and https://www.penguen.com.tr/home/private-label-2 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://www.penguen.com.tr/sirketimiz, https://www.penguen.com.tr/tum-urunler, https://www.penguen.com.tr/tum-urunler/soslar-ve-ezmeler, https://www.penguen.com.tr/tum-urunler/tursular, https://www.penguen.com.tr/tum-urunler/receller and https://www.penguen.com.tr/tum-urunler/dondurulmus-meyveler and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://www.penguen.com.tr/tum-urunler/soslar-ve-ezmeler, https://www.penguen.com.tr/tum-urunler/tursular, https://www.penguen.com.tr/tum-urunler/receller, https://www.penguen.com.tr/tum-urunler/dondurulmus-meyveler, https://www.penguen.com.tr/donmus-saglikli and https://www.penguen.com.tr/home/private-label-2 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.

  • 5 pages slow to respond

    https://www.penguen.com.tr/sirketimiz, https://www.penguen.com.tr/tum-urunler, https://www.penguen.com.tr/tum-urunler/tursular, https://www.penguen.com.tr/tum-urunler/receller and https://www.penguen.com.tr/home/private-label-2 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 25 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    12 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7393
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed
  • Tap targets are thumb-sized

    12 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix65
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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.

  • Only about 160 words

    The homepage has only about 160 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Opening hours shown

    Your opening hours are on the homepage.

  • 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 to fix
  • 4 trackers load before any consent

    4

    Before 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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 penguen.com.tr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2021.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on penguen.com.tr, including 16 speed issues, 3 SEO issues 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25