Access fcr.com.tr. FCR YAYIN | Fecr ~ Eskiyeni ~ Bilay ~ Meneviş ~ Kitabe

fcr.com.tr screenshot

26

Performance

Renders faster than
46% of other websites
73

Accessibility

Visual factors better than
that of 39% of websites
83

Best Practices

More advanced features
available than in
56% of websites
99

SEO

Google-friendlier than
93% of websites

First Response

2.4 sec

Resources Loaded

11.8 sec

Page Rendered

1.5 sec

fcr.com.tr screenshot

About Website

Click here to check amazing FCR content for Turkey. Otherwise, check out these important facts you probably never knew about fcr.com.tr

FCR | 1986 yılında yayın hayatına başlayan ve bugüne kadar 700'den fazla eser yayımlayan şirketimiz bünyesinde beş markaya yer vermektedir ...

Visit fcr.com.tr

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.445

21/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

fcr.com.tr

2436 ms

AC_RunActiveContent.js

477 ms

reset.css

307 ms

bootstrap.css

1187 ms

bootstrap-responsive.css

796 ms

Our browser made a total of 168 requests to load all elements on the main page. We found that 99% of them (166 requests) were addressed to the original Fcr.com.tr, 1% (2 requests) were made to Skypeassets.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Fcr.com.tr.

Content Size

18.5 MB

After Optimization

11.0 MB

In fact, the total size of Fcr.com.tr main page is 18.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 17.3 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 206.0 kB

Original 227.8 kB
After minification 171.6 kB
After compression 21.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 56.2 kB, which is 25% 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 206.0 kB or 90% of the original size.

Image Optimization

-38%

Potential reduce by 6.6 MB

Original 17.3 MB
After minification 10.7 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, FCR needs image optimization as it can save up to 6.6 MB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 562.3 kB

Original 730.7 kB
After minification 593.9 kB
After compression 168.4 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 562.3 kB or 77% of the original size.

CSS Optimization

-85%

Potential reduce by 210.8 kB

Original 247.1 kB
After minification 195.6 kB
After compression 36.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. Fcr.com.tr needs all CSS files to be minified and compressed as it can save up to 210.8 kB or 85% of the original size.

Requests Now

164

After Optimization

137

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

TR
Language Claimed

TR
Encoding

ISO-8859-9

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fcr.com.tr 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 Fcr.com.tr main page’s claimed encoding is iso-8859-9. 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

fcr.com.tr

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