Tools & Wizards About Us
yerlidizi.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

yerlidizi.org

Page Load Speed

4.7 sec in total

First Response

931 ms

Resources Loaded

3.6 sec

Page Rendered

150 ms

yerlidizi.org screenshot

About Website

Click here to check amazing Yerlidizi content for Turkey. Otherwise, check out these important facts you probably never knew about yerlidizi.org

Visit yerlidizi.org

Key Findings

We analyzed Yerlidizi.org page load time and found that the first response time was 931 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

yerlidizi.org performance score

0

Network Requests Diagram

index.php

931 ms

app.css

835 ms

css

28 ms

css

40 ms

04.jpg

958 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Yerlidizi.org, 46% (12 requests) were made to Sts.alanadlari.com and 35% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Sts.alanadlari.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.1 kB (11%)

Content Size

177.2 kB

After Optimization

157.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Yerlidizi.org main page is 177.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 151.8 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 12.2 kB

  • Original 17.4 kB
  • After minification 15.4 kB
  • After compression 5.2 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 2.0 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 12.2 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 1.2 kB

  • Original 151.8 kB
  • After minification 150.6 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. Yerlidizi images are well optimized though.

JavaScript Optimization

-84%

Potential reduce by 6.7 kB

  • Original 8.0 kB
  • After minification 3.4 kB
  • After compression 1.3 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 6.7 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yerlidizi. According to our analytics all requests are already optimized.

Network Requests Diagram

index.php

index.php

931 ms

app.css

app.css

835 ms

css

css

28 ms

css

css

40 ms

04.jpg

04.jpg

958 ms

logo.png

logo.png

645 ms

app.js

app.js

1271 ms

jwplayer.js

jwplayer.js

1322 ms

binalar.png

binalar.png

184 ms

sprite.png

sprite.png

185 ms

footerLogo.png

footerLogo.png

208 ms

hataIcon.png

hataIcon.png

304 ms

u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff

u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff

33 ms

DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff

DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff

45 ms

MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff

MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff

67 ms

k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff

k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff

68 ms

EInbV5DfGHOiMmvb1Xr-hha1RVmPjeKy21_GQJaLlJI.woff

EInbV5DfGHOiMmvb1Xr-hha1RVmPjeKy21_GQJaLlJI.woff

68 ms

nsLtvfQoT-rVwGTHHnkeJj8E0i7KZn-EPnyo3HZu7kw.woff

nsLtvfQoT-rVwGTHHnkeJj8E0i7KZn-EPnyo3HZu7kw.woff

84 ms

gMhvhm-nVj1086DvGgmzBz8E0i7KZn-EPnyo3HZu7kw.woff

gMhvhm-nVj1086DvGgmzBz8E0i7KZn-EPnyo3HZu7kw.woff

85 ms

hHs22WBTTzMhSqc5uBBDKg.woff

hHs22WBTTzMhSqc5uBBDKg.woff

68 ms

WtcvfJHWXKxx4x0kuS1koT8E0i7KZn-EPnyo3HZu7kw.woff

WtcvfJHWXKxx4x0kuS1koT8E0i7KZn-EPnyo3HZu7kw.woff

126 ms

gapro-2.js

gapro-2.js

318 ms

api.php

api.php

554 ms

logo.png

logo.png

54 ms

video.jpg

video.jpg

601 ms

security.php

security.php

156 ms

SEO Factors

yerlidizi.org SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    TR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yerlidizi.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Turkish. Our system also found out that Yerlidizi.org 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

yerlidizi.org

Open Graph description is not detected on the main page of Yerlidizi. 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: