Tools & Wizards About Us
kartepe.bel.tr screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

kartepe.bel.tr

Kartepe Belediye Başkanlığı

Page Load Speed

4.7 sec in total

First Response

526 ms

Resources Loaded

3.6 sec

Page Rendered

560 ms

kartepe.bel.tr screenshot

About Website

Visit kartepe.bel.tr now to see the best up-to-date Kartepe content for Turkey and also check out these interesting facts you probably never knew about kartepe.bel.tr

Kartepe Belediyesi

Visit kartepe.bel.tr

Key Findings

We analyzed Kartepe.bel.tr page load time and found that the first response time was 526 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

kartepe.bel.tr performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.272

45/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

kartepe.bel.tr

526 ms

kartepe.bel.tr

686 ms

normalize.css

929 ms

bootstrap.min.css

1070 ms

owl.carousel.min.css

945 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 66% of them (42 requests) were addressed to the original Kartepe.bel.tr, 6% (4 requests) were made to Fonts.googleapis.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Kartepe.bel.tr.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.8 kB (7%)

Content Size

3.5 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kartepe.bel.tr main page is 3.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 61.3 kB

  • Original 75.6 kB
  • After minification 60.2 kB
  • After compression 14.3 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 15.4 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 61.3 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 130.2 kB

  • Original 2.8 MB
  • After minification 2.7 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Kartepe images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 35.4 kB

  • Original 439.6 kB
  • After minification 439.6 kB
  • After compression 404.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 927 B

  • Original 112.2 kB
  • After minification 112.2 kB
  • After compression 111.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Kartepe.bel.tr has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (69%)

Requests Now

54

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kartepe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

kartepe.bel.tr

kartepe.bel.tr

526 ms

kartepe.bel.tr

kartepe.bel.tr

686 ms

normalize.css

normalize.css

929 ms

bootstrap.min.css

bootstrap.min.css

1070 ms

owl.carousel.min.css

owl.carousel.min.css

945 ms

all.css

all.css

948 ms

css

css

51 ms

css

css

71 ms

style.php

style.php

964 ms

iziModal.min.css

iziModal.min.css

960 ms

flag-icon.min.css

flag-icon.min.css

934 ms

search.css

search.css

956 ms

plyr.css

plyr.css

957 ms

loader.css

loader.css

1063 ms

fancybox.css

fancybox.css

1080 ms

swipebox.css

swipebox.css

1084 ms

api.js

api.js

54 ms

font-awesome5.min.css

font-awesome5.min.css

1088 ms

all.css

all.css

1227 ms

jquery.min.js

jquery.min.js

1092 ms

sweetalert2.all.min.js

sweetalert2.all.min.js

1323 ms

sweetalert2.min.js

sweetalert2.min.js

1206 ms

cookieconsent.min.css

cookieconsent.min.css

44 ms

jquery.cookie.min.js

jquery.cookie.min.js

41 ms

bootstrap.min.js

bootstrap.min.js

1387 ms

owl.carousel.min.js

owl.carousel.min.js

1219 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

1216 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

1385 ms

plyr.min.js

plyr.min.js

1441 ms

jquery.swipebox.js

jquery.swipebox.js

1442 ms

fancybox.js

fancybox.js

1441 ms

iziModal.min.js

iziModal.min.js

1483 ms

main.js

main.js

1485 ms

cookieconsent.min.js

cookieconsent.min.js

48 ms

recaptcha__en.js

recaptcha__en.js

31 ms

css

css

20 ms

analytics.js

analytics.js

119 ms

ALTIN-LOGO-STANDART-Ozel.png

ALTIN-LOGO-STANDART-Ozel.png

201 ms

ARKAPLAN1_1.jpg

ARKAPLAN1_1.jpg

578 ms

23422.jpg

23422.jpg

650 ms

BELED.jpg

BELED.jpg

1007 ms

DJI_0536-Buyuk.jpg

DJI_0536-Buyuk.jpg

898 ms

logo-footer-sag-1_1.png

logo-footer-sag-1_1.png

305 ms

embed

embed

254 ms

456_1.jpg

456_1.jpg

481 ms

section-cover.jpg

section-cover.jpg

851 ms

fa-brands-400.woff

fa-brands-400.woff

536 ms

fa-brands-400.woff

fa-brands-400.woff

576 ms

fa-brands-400.woff

fa-brands-400.woff

652 ms

font

font

169 ms

font

font

170 ms

fa-solid-900.woff

fa-solid-900.woff

677 ms

fa-regular-400.woff

fa-regular-400.woff

716 ms

fa-light-300.woff

fa-light-300.woff

915 ms

font

font

319 ms

collect

collect

155 ms

fallback

fallback

110 ms

js

js

91 ms

collect

collect

83 ms

js

js

87 ms

fallback__ltr.css

fallback__ltr.css

38 ms

css

css

25 ms

logo_48.png

logo_48.png

16 ms

font

font

64 ms

Accessibility Review

kartepe.bel.tr accessibility score

71

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

kartepe.bel.tr best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

kartepe.bel.tr SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    TR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kartepe.bel.tr can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and it matches the claimed language. Our system also found out that Kartepe.bel.tr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

kartepe.bel.tr

Open Graph data is detected on the main page of Kartepe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: