Report Summary

  • 7

    Performance

    Renders faster than
    21% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 46

    SEO

    Google-friendlier than
    18% of websites

22dakika.org

22dakika.org | Hayatın anlamını dizilerde arayanların sitesi

Page Load Speed

4.9 sec in total

First Response

1.3 sec

Resources Loaded

2.7 sec

Page Rendered

876 ms

22dakika.org screenshot

About Website

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

Hayatın anlamını dizilerde arayanların sitesi

Visit 22dakika.org

Key Findings

We analyzed 22dakika.org page load time and found that the first response time was 1.3 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

22dakika.org performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value1.001

2/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

22dakika.org

1313 ms

style.css

180 ms

common.css

182 ms

22dakika.css

188 ms

modernizr-2.5.3.min.js

186 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 66% of them (68 requests) were addressed to the original 22dakika.org, 14% (14 requests) were made to Ajax.googleapis.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain 22dakika.org.

Page Optimization Overview & Recommendations

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

Content Size

3.0 MB

After Optimization

1.9 MB

In fact, the total size of 22dakika.org main page is 3.0 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 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 84.4 kB

  • Original 104.9 kB
  • After minification 98.0 kB
  • After compression 20.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. 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 84.4 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 76.4 kB

  • Original 1.6 MB
  • After minification 1.6 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. 22 Dakika images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 742.1 kB

  • Original 1.0 MB
  • After minification 814.2 kB
  • After compression 265.0 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 742.1 kB or 74% of the original size.

CSS Optimization

-74%

Potential reduce by 188.5 kB

  • Original 255.8 kB
  • After minification 224.5 kB
  • After compression 67.3 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. 22dakika.org needs all CSS files to be minified and compressed as it can save up to 188.5 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 61 (61%)

Requests Now

100

After Optimization

39

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

Accessibility Review

22dakika.org accessibility score

82

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

22dakika.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

22dakika.org SEO score

46

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

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 22dakika.org can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 22dakika.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 data is detected on the main page of 22 Dakika. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: