Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

tff.org

Türkiye Futbol Federasyonu Resmi İnternet Sitesi Ana Sayfa TFF

Page Load Speed

23.4 sec in total

First Response

1.5 sec

Resources Loaded

21 sec

Page Rendered

892 ms

tff.org screenshot

About Website

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

Türkiye Futbol Federasyonu Resmi İnternet Sitesi

Visit tff.org

Key Findings

We analyzed Tff.org page load time and found that the first response time was 1.5 sec and then it took 21.9 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

tff.org performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.264

46/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

default.aspx

1472 ms

popupImg.js

266 ms

smart-app-banner.css

401 ms

smart-app-banner.js

538 ms

css2

35 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 91% of them (72 requests) were addressed to the original Tff.org, 5% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (17.9 sec) belongs to the original domain Tff.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (19%)

Content Size

6.9 MB

After Optimization

5.6 MB

In fact, the total size of Tff.org main page is 6.9 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. 55% of websites need less resources to load. Images take 6.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 68.0 kB

  • Original 80.8 kB
  • After minification 69.0 kB
  • After compression 12.8 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 11.8 kB, which is 15% 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 68.0 kB or 84% of the original size.

Image Optimization

-19%

Potential reduce by 1.3 MB

  • Original 6.7 MB
  • After minification 5.4 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. Obviously, TFF needs image optimization as it can save up to 1.3 MB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 4.7 kB

  • Original 100.4 kB
  • After minification 100.4 kB
  • After compression 95.7 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.

CSS Optimization

-18%

Potential reduce by 5.3 kB

  • Original 29.8 kB
  • After minification 29.8 kB
  • After compression 24.5 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. Tff.org needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 18% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

42

The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TFF. 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 13 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

tff.org accessibility score

67

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.

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

High

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

Best Practices

tff.org best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tff.org SEO score

90

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

    WINDOWS-1254

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tff.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 Tff.org main page’s claimed encoding is windows-1254. 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

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