Tools & Wizards About Us
kanitlar.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

kanitlar.com

Page Load Speed

10.4 sec in total

First Response

2.2 sec

Resources Loaded

6.6 sec

Page Rendered

1.6 sec

kanitlar.com screenshot

About Website

Welcome to kanitlar.com homepage info - get ready to check Kanitlar best content for Turkey right away, or after learning these important things about kanitlar.com

Visit kanitlar.com

Key Findings

We analyzed Kanitlar.com page load time and found that the first response time was 2.2 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

kanitlar.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

www.kanitlar.com

2202 ms

css

23 ms

validationEngine.jquery.css

204 ms

fb-comments-hidewpcomments.css

207 ms

grid.css

193 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 57% of them (35 requests) were addressed to the original Kanitlar.com, 16% (10 requests) were made to Static.xx.fbcdn.net and 11% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Kanitlar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 939.7 kB (80%)

Content Size

1.2 MB

After Optimization

239.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kanitlar.com main page is 1.2 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. 50% of websites need less resources to load. CSS take 475.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 275.6 kB

  • Original 315.7 kB
  • After minification 310.3 kB
  • After compression 40.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 275.6 kB or 87% of the original size.

Image Optimization

-8%

Potential reduce by 3.5 kB

  • Original 45.8 kB
  • After minification 42.4 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. Kanitlar images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 252.4 kB

  • Original 341.9 kB
  • After minification 297.1 kB
  • After compression 89.5 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 252.4 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 408.2 kB

  • Original 475.6 kB
  • After minification 402.1 kB
  • After compression 67.4 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. Kanitlar.com needs all CSS files to be minified and compressed as it can save up to 408.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (68%)

Requests Now

56

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.kanitlar.com

www.kanitlar.com

2202 ms

css

css

23 ms

validationEngine.jquery.css

validationEngine.jquery.css

204 ms

fb-comments-hidewpcomments.css

fb-comments-hidewpcomments.css

207 ms

grid.css

grid.css

193 ms

base.css

base.css

178 ms

layout.css

layout.css

240 ms

shortcodes.css

shortcodes.css

259 ms

magnific-popup.css

magnific-popup.css

268 ms

mediaelementplayer.css

mediaelementplayer.css

288 ms

enfold_child.css

enfold_child.css

384 ms

custom.css

custom.css

283 ms

style.css

style.css

308 ms

jquery.js

jquery.js

408 ms

jquery-migrate.min.js

jquery-migrate.min.js

431 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

426 ms

jquery.cookie.js

jquery.cookie.js

426 ms

jquery.dcjqaccordion.2.9.js

jquery.dcjqaccordion.2.9.js

424 ms

avia-compat.js

avia-compat.js

458 ms

skin.php

skin.php

645 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

550 ms

avia.js

avia.js

602 ms

shortcodes.js

shortcodes.js

601 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

476 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

524 ms

wp-mediaelement.js

wp-mediaelement.js

601 ms

comment-reply.min.js

comment-reply.min.js

601 ms

wp-embed.min.js

wp-embed.min.js

629 ms

jquery.validationEngine-tr.js

jquery.validationEngine-tr.js

664 ms

jquery.validationEngine.js

jquery.validationEngine.js

663 ms

front-subscribers.js

front-subscribers.js

667 ms

kanitlar-logo.jpg

kanitlar-logo.jpg

1268 ms

qdgUG4U09HnJwhYI-uK18wLUuEpTyoUstqEm5AMlJo4.woff

qdgUG4U09HnJwhYI-uK18wLUuEpTyoUstqEm5AMlJo4.woff

11 ms

qIIYRU-oROkIk8vfvxw6QvesZW2xOQ-xsNqO47m55DA.woff

qIIYRU-oROkIk8vfvxw6QvesZW2xOQ-xsNqO47m55DA.woff

35 ms

kcf5uOXucLcbFOydGU24WALUuEpTyoUstqEm5AMlJo4.woff

kcf5uOXucLcbFOydGU24WALUuEpTyoUstqEm5AMlJo4.woff

34 ms

sdk.js

sdk.js

74 ms

entypo-fontello.woff

entypo-fontello.woff

1021 ms

bg_grey.png

bg_grey.png

188 ms

arrow_grey_right.png

arrow_grey_right.png

188 ms

194 ms

xd_arbiter.php

xd_arbiter.php

195 ms

xd_arbiter.php

xd_arbiter.php

257 ms

print.css

print.css

93 ms

page.php

page.php

134 ms

4n08FrZmW0I.css

4n08FrZmW0I.css

86 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

138 ms

YvxwM8R7ol8.js

YvxwM8R7ol8.js

172 ms

ihptErjAmMX.js

ihptErjAmMX.js

163 ms

577551_236698103097141_967508154_n.jpg

577551_236698103097141_967508154_n.jpg

249 ms

292119_236696019764016_659376203_n.jpg

292119_236696019764016_659376203_n.jpg

81 ms

11001823_341659276026856_1448271969200768369_n.jpg

11001823_341659276026856_1448271969200768369_n.jpg

65 ms

12804732_1089714101091748_2023174885814106915_n.jpg

12804732_1089714101091748_2023174885814106915_n.jpg

68 ms

12654510_10207020137439908_1243553329733846493_n.jpg

12654510_10207020137439908_1243553329733846493_n.jpg

133 ms

319602_4253963021374_1705137689_n.jpg

319602_4253963021374_1705137689_n.jpg

69 ms

12308679_496144873879913_6488015789428521524_n.jpg

12308679_496144873879913_6488015789428521524_n.jpg

216 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

22 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

21 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

20 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

22 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

22 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

36 ms

Accessibility Review

kanitlar.com accessibility score

85

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

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

kanitlar.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

kanitlar.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    EN

  • Language Claimed

    TR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kanitlar.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Turkish language. Our system also found out that Kanitlar.com 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

kanitlar.com

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