Access faralya.org. Faralya Emlak Fethiye | Faralya Gayrimenkul Fethiye Emlak

name

value

score

weighting

FCP (First Contentful Paint)

Value10.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value2,070 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.346

32/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

faralya.org

347 ms

faralya.org

2642 ms

js

254 ms

css

51 ms

css

160 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 45% of them (44 requests) were addressed to the original Faralya.org, 30% (29 requests) were made to Cdnc.re-os.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Faralya.org.

Content Size

632.8 kB

After Optimization

342.9 kB

In fact, the total size of Faralya.org main page is 632.8 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. 70% of websites need less resources to load. Javascripts take 374.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 130.3 kB

Original 148.9 kB
After minification 112.7 kB
After compression 18.6 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 36.2 kB, which is 24% 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 130.3 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 1.1 kB

Original 38.8 kB
After minification 37.8 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. Faralya images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 131.4 kB

Original 374.5 kB
After minification 374.5 kB
After compression 243.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 131.4 kB or 35% of the original size.

CSS Optimization

-38%

Potential reduce by 27.1 kB

Original 70.6 kB
After minification 70.6 kB
After compression 43.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. Faralya.org needs all CSS files to be minified and compressed as it can save up to 27.1 kB or 38% of the original size.

Requests Now

After Optimization

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faralya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faralya.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 Faralya.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

faralya.org

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Faralya Emlak Fethiye | Faralya Gayrimenkul Fethiye Emlak

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

faralya.org

faralya.org

js

css

css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

faralya.org

faralya.org

js

css

css

font-awesome.min.css

bootstrap-select.min.css

fileinput.min.css

nv.d3.min.css

owl.carousel.css

realsite.css

validationEngine.jquery.css

jquery.js

jquery.transit.js

modernizr-2.8.1.min.js

bootstrap.min.js

collapse.js

bootstrap-select.min.js

fileinput.min.js

jquery.autosize.js

isotope.pkgd.min.js

owl.carousel.min.js

jquery.scrollTo.min.js

infobox.js

markerclusterer.js

jquery-google-map.js

mapbox-gl.js

mapbox-gl.css

mapbox-gl-geocoder.min.js

mapbox-gl-geocoder.css

mapbox-gl-language.js

mapbox-common.js

d3.v3.js

nv.d3.min.js

realsite.js

charts.js

map.js

validationEngine.js

validationEngine-tr.js

jquery.maskedinput.js

autoNumeric.min.js

home.index.js

js