Tools & Wizards About Us
diyarbakir.yerelnet.org.tr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

diyarbakir.yerelnet.org.tr

Diyarbakır - YerelNET

Page Load Speed

24.9 sec in total

First Response

1.2 sec

Resources Loaded

23.3 sec

Page Rendered

313 ms

diyarbakir.yerelnet.org.tr screenshot

About Website

Welcome to diyarbakir.yerelnet.org.tr homepage info - get ready to check Diyarbakir YerelNET best content for Turkey right away, or after learning these important things about diyarbakir.yerelnet.org.tr

Diyarbakır, Türkiye'nin doğusundan bulunan bölgenin en büyük nüfusuna sahip şehirdir. 2019 Yılı verilerine göre 1.756.353 kişilik nüfusa sahiptir. Diyarbakır'ın yüzölçümü ise 15.272 km2&#039...

Visit diyarbakir.yerelnet.org.tr

Key Findings

We analyzed Diyarbakir.yerelnet.org.tr page load time and found that the first response time was 1.2 sec and then it took 23.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

diyarbakir.yerelnet.org.tr performance score

0

Network Requests Diagram

diyarbakir.yerelnet.org.tr

1247 ms

bootstrap.css

1949 ms

icoMoon.css

1031 ms

superfish.css

571 ms

prettyPhoto.css

1523 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Diyarbakir.yerelnet.org.tr, 55% (59 requests) were made to Yerelnet.org.tr and 15% (16 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (12.3 sec) relates to the external source Yerelnet.org.tr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (62%)

Content Size

1.8 MB

After Optimization

684.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Diyarbakir.yerelnet.org.tr main page is 1.8 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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 60.5 kB

  • Original 73.5 kB
  • After minification 64.9 kB
  • After compression 12.9 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 8.5 kB, which is 12% 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 60.5 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 13.9 kB

  • Original 325.6 kB
  • After minification 311.7 kB

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. Diyarbakir YerelNET images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 706.3 kB

  • Original 1.0 MB
  • After minification 916.8 kB
  • After compression 303.6 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 706.3 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 347.0 kB

  • Original 403.5 kB
  • After minification 328.1 kB
  • After compression 56.6 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. Diyarbakir.yerelnet.org.tr needs all CSS files to be minified and compressed as it can save up to 347.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (65%)

Requests Now

92

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

diyarbakir.yerelnet.org.tr

diyarbakir.yerelnet.org.tr

1247 ms

bootstrap.css

bootstrap.css

1949 ms

icoMoon.css

icoMoon.css

1031 ms

superfish.css

superfish.css

571 ms

prettyPhoto.css

prettyPhoto.css

1523 ms

flexslider.css

flexslider.css

565 ms

awesome-weather.css

awesome-weather.css

1210 ms

style.css

style.css

1965 ms

bootstrap-responsive.css

bootstrap-responsive.css

1524 ms

docs.min.css

docs.min.css

2032 ms

thumbnail-gallery.css

thumbnail-gallery.css

2070 ms

responsive.css

responsive.css

3300 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

3189 ms

colorbox.css

colorbox.css

2408 ms

jquery.colorbox.js

jquery.colorbox.js

2636 ms

modernizr.custom.js

modernizr.custom.js

3197 ms

jsapi

jsapi

39 ms

superfish.js

superfish.js

5589 ms

retina.js

retina.js

4192 ms

bootstrap.js

bootstrap.js

4985 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

4665 ms

jquery.carouFredSel-6.0.4-packed.js

jquery.carouFredSel-6.0.4-packed.js

5821 ms

jflickrfeed.min.js

jflickrfeed.min.js

5119 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

4762 ms

tweetable.jquery.js

tweetable.jquery.js

5010 ms

jquery.timeago.js

jquery.timeago.js

5081 ms

jquery.validate.min.js

jquery.validate.min.js

5787 ms

jquery.form.js

jquery.form.js

10658 ms

jquery.mCustomScrollbar.js

jquery.mCustomScrollbar.js

6090 ms

modernizr-transitions.js

modernizr-transitions.js

9704 ms

jquery.isotope.min.js

jquery.isotope.min.js

8632 ms

custom.js

custom.js

8992 ms

css

css

33 ms

highslide-with-gallery.js

highslide-with-gallery.js

12328 ms

highslide.css

highslide.css

7347 ms

js

js

24 ms

swfobject.js

swfobject.js

7352 ms

jquery.newsTicker.js

jquery.newsTicker.js

7701 ms

css

css

70 ms

125492_11_35_23.jpg

125492_11_35_23.jpg

342 ms

glyphicons-halflings.png

glyphicons-halflings.png

337 ms

logo.png

logo.png

652 ms

search-icon.png

search-icon.png

334 ms

eposta_yaz.php

eposta_yaz.php

2485 ms

21.gif

21.gif

339 ms

nk_m03.png

nk_m03.png

2116 ms

saydam.gif

saydam.gif

2240 ms

banner_seminer.jpg

banner_seminer.jpg

958 ms

banner_anket.png

banner_anket.png

9656 ms

logo2.png

logo2.png

955 ms

keyinternetlogo.gif

keyinternetlogo.gif

1273 ms

saydam.gif

saydam.gif

350 ms

spacer.gif

spacer.gif

351 ms

y351.jpg

y351.jpg

2579 ms

y332.jpg

y332.jpg

345 ms

y313.jpg

y313.jpg

2376 ms

weather-icon.png

weather-icon.png

2015 ms

bg-header-title-1.png

bg-header-title-1.png

1552 ms

bg-header-title-2.png

bg-header-title-2.png

1872 ms

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

48 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

93 ms

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

92 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

95 ms

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf

94 ms

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

93 ms

EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf

EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf

93 ms

icomoon.woff

icomoon.woff

6678 ms

ie_bg.png

ie_bg.png

2564 ms

analytics.js

analytics.js

59 ms

havadurumu.php

havadurumu.php

2495 ms

overlay.png

overlay.png

2164 ms

collect

collect

46 ms

common.js

common.js

39 ms

util.js

util.js

90 ms

stats.js

stats.js

82 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

285 ms

rounded-white.png

rounded-white.png

319 ms

map.js

map.js

4 ms

loader.white.gif

loader.white.gif

306 ms

zoomout.cur

zoomout.cur

310 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

109 ms

onion.js

onion.js

16 ms

openhand_8_8.cur

openhand_8_8.cur

22 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

74 ms

controls.js

controls.js

9 ms

transparent.png

transparent.png

36 ms

css

css

55 ms

google4.png

google4.png

55 ms

infowindow.js

infowindow.js

51 ms

marker.js

marker.js

45 ms

mapcnt6.png

mapcnt6.png

54 ms

sv5.png

sv5.png

56 ms

tmapctrl.png

tmapctrl.png

19 ms

cb_scout5.png

cb_scout5.png

22 ms

tmapctrl4.png

tmapctrl4.png

52 ms

imgs8.png

imgs8.png

56 ms

vt

vt

48 ms

vt

vt

47 ms

vt

vt

48 ms

vt

vt

46 ms

vt

vt

49 ms

vt

vt

47 ms

vt

vt

79 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

7 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

8 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

40 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

8 ms

SEO Factors

diyarbakir.yerelnet.org.tr SEO score

0

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    TR

  • Encoding

    ISO-8859-9

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diyarbakir.yerelnet.org.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 Diyarbakir.yerelnet.org.tr main page’s claimed encoding is iso-8859-9. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

diyarbakir.yerelnet.org.tr

Open Graph description is not detected on the main page of Diyarbakir YerelNET. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: