Report Summary

  • 29

    Performance

    Renders faster than
    48% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

kanver.org

Kan Hizmetleri - AnaSayfa

Page Load Speed

5.7 sec in total

First Response

544 ms

Resources Loaded

4.8 sec

Page Rendered

397 ms

kanver.org screenshot

About Website

Visit kanver.org now to see the best up-to-date Kan Ver content for Turkey and also check out these interesting facts you probably never knew about kanver.org

Türk Kızılayı'na kan bağışı yaparak umut olun, hayat kurtarın. Kan vermek için bilgileri ve Kan Bağışı noktalarını Kanver.org'da bulabilirsiniz.

Visit kanver.org

Key Findings

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

Performance Metrics

kanver.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value17.3 s

0/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.564

12/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

kanver.org

544 ms

www.kanver.org

1130 ms

css

36 ms

bootstrap.min.css

452 ms

essentials.css

1288 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 87% of them (61 requests) were addressed to the original Kanver.org, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Kanver.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.7 kB (57%)

Content Size

68.2 kB

After Optimization

29.5 kB

In fact, the total size of Kanver.org main page is 68.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. 60% of websites need less resources to load. HTML takes 47.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 38.7 kB

  • Original 47.2 kB
  • After minification 37.7 kB
  • After compression 8.5 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 9.5 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 38.7 kB or 82% of the original size.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

Number of requests can be reduced by 19 (31%)

Requests Now

62

After Optimization

43

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

Accessibility Review

kanver.org accessibility score

67

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

Image elements do not have [alt] attributes

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kanver.org best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

kanver.org SEO score

88

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Kanver.org 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 Kanver.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

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