Website review, no card needed

sekersigorta.com.tr logo

sekersigorta.com.tr website review

Visit site (opens in a new tab)Reviewed 22 October 202642 issues · 84 checks

This review found 42 issues worth fixing on sekersigorta.com.tr, 15 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
3.5 s2.8 sJun 6Aug 293.2 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20263.5 s
Jun 27, 20263.2 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
173 ms136 msAug 8Aug 29169 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026140 ms
Aug 15, 2026169 ms
Aug 22, 2026166 ms
Aug 29, 2026169 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 sekersigorta.com.tr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sekersigorta.com.tr at 1.8 s1.8 s
  2. sekersigorta.com.tr at 3.6 s3.6 s
  3. sekersigorta.com.tr at 5.3 s5.3 s
  4. sekersigorta.com.tr at 7.1 s7.1 s
  5. sekersigorta.com.tr at 8.9 s8.9 s
  6. sekersigorta.com.tr at 10.7 s10.7 s
  7. sekersigorta.com.tr at 12.5 s12.5 s
  8. sekersigorta.com.tr at 14.2 s14.2 s

Speed

5 to fix38
  • Render-blocking requests

    3.9 s

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

  • Font display

    1.0 s

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

  • Mobile performance score: 38

    38/100

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

  • Reduce unused CSS

    450 ms · 52 KiB

    About 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Improve image delivery

    298 KiB

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

  • Use efficient cache lifetimes

    150 ms · 18 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (18 KiB).

  • Legacy JavaScript

    150 ms · 9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.

  • Minify JavaScript

    20 KiB

    20 KiB could be saved by minifying JavaScript.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 142 KiB and 0 ms of main-thread time.

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

    A phone's processor spends 0.7 s on main-thread work while loading, 102 ms of it running JavaScript. That is comfortably low.

  • Server response: 146 ms

    146 ms

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

Core Web Vitals

6 to fix41
  • Cumulative Layout Shift: 0.927

    0.927

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

  • Speed Index: 12.6 s

    12.6 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (3.9 s).

  • Time to Interactive: 5.5 s

    5.5 s

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

  • 14 images without width and height

    14 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix90
  • 3 images far larger than shown

    139 KiB

    3 images are downloaded at several times the size a phone draws them, for example f05c089c-8505-42d2-a0b7-e562b1124880_slider_1.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 139 KiB.

  • 3 images in older formats

    3 images (222 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.

  • 4 images below the first screen load straight away

    4 images further down the page (91 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.4 g of CO₂ per visit

    0.36 g

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

1 checks passed
  • Page weight: 1.3 MB in 78 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 78 requests on a phone: images 811 KiB (44), fonts 155 KiB (5) and scripts 124 KiB (12). That is a lean page.

Accessibility

14 to fixGoogle 6780
  • 11 buttons without a name

    11 buttons have no accessible name, so screen readers announce just “button”.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • <object> elements must have alternative text (1 element)

    <object> elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

  • 23 images without alt text

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

  • All page content should be contained by landmarks (12 elements)

    All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

7 to fixGoogle 8363
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (29 characters)

    Your title is only 29 characters: “Şeker Sigorta'ya Hoş Geldiniz”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (327 characters)

    Your meta description is 327 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at sekersigorta.com.tr/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 33 internal links, 11 external

    The homepage links to 33 pages on sekersigorta.com.tr and 11 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://sekersigorta.com.tr/sitemap.xml.

AI search readiness

1 to fix81
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://sekersigorta.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
  • Text is in the HTML

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

Other pages

4 to fix81
  • 2 pages share a title

    https://sekersigorta.com.tr/urunlerimiz/ferdi-kaza-sigortalariniz and https://sekersigorta.com.tr/urunlerimiz/nakliyat-sigortalariniz all use the title “| Şeker Sigorta”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://sekersigorta.com.tr/Urun/AcenteSorgula, https://sekersigorta.com.tr/Urun/YetkiliServisSorgula and https://sekersigorta.com.tr/Urun/TamamlayiciSigorta have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages share a meta description

    https://sekersigorta.com.tr/urunlerimiz/tum-urunler, https://sekersigorta.com.tr/iletisim/iletisim-formu, https://sekersigorta.com.tr/urunlerimiz/araclariniz, https://sekersigorta.com.tr/urunlerimiz/muhendislik-sigortalariniz, https://sekersigorta.com.tr/urunlerimiz/tarim-sigortalariniz and https://sekersigorta.com.tr/urunlerimiz/eviniz and 6 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://sekersigorta.com.tr/urunlerimiz/tum-urunler, https://sekersigorta.com.tr/iletisim/iletisim-formu, https://sekersigorta.com.tr/urunlerimiz/araclariniz, https://sekersigorta.com.tr/urunlerimiz/muhendislik-sigortalariniz, https://sekersigorta.com.tr/urunlerimiz/tarim-sigortalariniz and https://sekersigorta.com.tr/urunlerimiz/eviniz and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://sekersigorta.com.tr/urunlerimiz/tum-urunler, https://sekersigorta.com.tr/iletisim/iletisim-formu, https://sekersigorta.com.tr/urunlerimiz/araclariniz, https://sekersigorta.com.tr/urunlerimiz/muhendislik-sigortalariniz, https://sekersigorta.com.tr/urunlerimiz/tarim-sigortalariniz and https://sekersigorta.com.tr/urunlerimiz/eviniz and 9 others 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 22 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.

  • 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 410 words of copy

    The homepage carries about 410 words of visible text.

2 checks passed
  • 1 short form

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

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 0 email links.

Privacy and tracking

  • 1 cookie set on arrival

    1

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 sekersigorta.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 © 2019.

Stack

Framework
jQuery

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 sekersigorta.com.tr, including 11 speed issues, 7 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

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