Tools & Wizards About Us
frekans.net screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 38

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

frekans.net

Frekans Web Tasarım - Yapım - Sosyal Medya - SEO

Page Load Speed

1.6 sec in total

First Response

133 ms

Resources Loaded

1.3 sec

Page Rendered

176 ms

frekans.net screenshot

About Website

Click here to check amazing Frekans content. Otherwise, check out these important facts you probably never knew about frekans.net

Günümüz web standartlarına uygun, dinamik, güçlü, kolay kullanımlı, e-ticaret, kurumsal, kişisel web tasarımı. Arayın görüşelim, sizin için en uygun internet sitesini birlikte seçelim.

Visit frekans.net

Key Findings

We analyzed Frekans.net page load time and found that the first response time was 133 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

frekans.net performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

frekans.net

133 ms

www.frekans.com

284 ms

genel.css

37 ms

jquery-ui-1.8.24.custom.css

63 ms

jquery-1.8.2.min.js

96 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Frekans.net, 95% (61 requests) were made to Frekans.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (575 ms) relates to the external source Frekans.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 431.5 kB (29%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frekans.net main page is 1.5 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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 28.9 kB

  • Original 34.6 kB
  • After minification 21.3 kB
  • After compression 5.7 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 13.3 kB, which is 39% 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 28.9 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 78.4 kB

  • Original 1.0 MB
  • After minification 929.3 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. Frekans images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 213.8 kB

  • Original 320.5 kB
  • After minification 320.3 kB
  • After compression 106.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 213.8 kB or 67% of the original size.

CSS Optimization

-87%

Potential reduce by 110.3 kB

  • Original 126.3 kB
  • After minification 94.7 kB
  • After compression 16.0 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. Frekans.net needs all CSS files to be minified and compressed as it can save up to 110.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (7%)

Requests Now

61

After Optimization

57

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frekans.net

frekans.net

133 ms

www.frekans.com

www.frekans.com

284 ms

genel.css

genel.css

37 ms

jquery-ui-1.8.24.custom.css

jquery-ui-1.8.24.custom.css

63 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

96 ms

jquery-ui-1.8.24.custom.min.js

jquery-ui-1.8.24.custom.min.js

129 ms

genel.js

genel.js

59 ms

functions.js

functions.js

92 ms

analytics.js

analytics.js

57 ms

loader.gif

loader.gif

31 ms

logo-mask.jpg

logo-mask.jpg

60 ms

pane-controls.png

pane-controls.png

90 ms

anaslider.jpg

anaslider.jpg

185 ms

striped-background.png

striped-background.png

31 ms

icon-sprite.png

icon-sprite.png

113 ms

section-shadow.png

section-shadow.png

93 ms

web_tasarimi.jpg

web_tasarimi.jpg

130 ms

misafir_yerliler.png

misafir_yerliler.png

238 ms

web-tasarim-nob.jpg

web-tasarim-nob.jpg

575 ms

sosial_logos.jpg

sosial_logos.jpg

203 ms

hr.png

hr.png

351 ms

corner-badge-sprite.png

corner-badge-sprite.png

353 ms

35_k.jpg

35_k.jpg

341 ms

37_k.jpg

37_k.jpg

343 ms

36_k.jpg

36_k.jpg

343 ms

34_k.jpg

34_k.jpg

393 ms

32_k.jpg

32_k.jpg

411 ms

31_k.jpg

31_k.jpg

427 ms

38_k.jpg

38_k.jpg

393 ms

40_k.jpg

40_k.jpg

418 ms

30_k.jpg

30_k.jpg

466 ms

4_k.jpg

4_k.jpg

450 ms

5_k.jpg

5_k.jpg

474 ms

6_k.jpg

6_k.jpg

449 ms

13_k.jpg

13_k.jpg

481 ms

7_k.jpg

7_k.jpg

479 ms

28_k.jpg

28_k.jpg

480 ms

9_k.jpg

9_k.jpg

507 ms

10_k.jpg

10_k.jpg

501 ms

19_k.jpg

19_k.jpg

536 ms

11_k.jpg

11_k.jpg

552 ms

8_k.jpg

8_k.jpg

533 ms

14_k.jpg

14_k.jpg

544 ms

15_k.jpg

15_k.jpg

551 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

562 ms

collect

collect

13 ms

17_k.jpg

17_k.jpg

547 ms

18_k.jpg

18_k.jpg

554 ms

20_k.jpg

20_k.jpg

541 ms

21_k.jpg

21_k.jpg

502 ms

23_k.jpg

23_k.jpg

508 ms

16_k.jpg

16_k.jpg

496 ms

24_k.jpg

24_k.jpg

474 ms

22_k.jpg

22_k.jpg

431 ms

25_k.jpg

25_k.jpg

416 ms

26_k.jpg

26_k.jpg

396 ms

27_k.jpg

27_k.jpg

297 ms

29_k.jpg

29_k.jpg

291 ms

speechmark.png

speechmark.png

293 ms

footer-gradient.png

footer-gradient.png

293 ms

footer-image-top.png

footer-image-top.png

318 ms

firma_logolari.png

firma_logolari.png

268 ms

icon-ee.png

icon-ee.png

277 ms

icon-arrow-white.png

icon-arrow-white.png

266 ms

Accessibility Review

frekans.net accessibility score

38

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

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

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

frekans.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

frekans.net SEO score

85

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

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

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 Frekans.net 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 Frekans.net 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

frekans.net

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