5.5 sec in total
1.9 sec
3.3 sec
314 ms
Click here to check amazing Fazil Say content for Turkey. Otherwise, check out these important facts you probably never knew about fazilsay.com
Fazil Say is not merely a pianist of genius; undoubtedly he will be one of the greatest artists of the twenty-first century. (Le Figaro, Paris)
Visit fazilsay.comWe analyzed Fazilsay.com page load time and found that the first response time was 1.9 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 60% of websites can load faster.
fazilsay.com performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value22.0 s
0/100
25%
Value30.4 s
0/100
10%
Value4,010 ms
1/100
30%
Value0.022
100/100
15%
Value31.3 s
0/100
10%
1899 ms
78 ms
25 ms
132 ms
139 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 74% of them (54 requests) were addressed to the original Fazilsay.com, 4% (3 requests) were made to Youtube.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fazilsay.com.
Page size can be reduced by 977.4 kB (39%)
2.5 MB
1.5 MB
In fact, the total size of Fazilsay.com main page is 2.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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 22.9 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 22.9 kB or 77% of the original size.
Potential reduce by 70.1 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. Fazil Say images are well optimized though.
Potential reduce by 481.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 481.7 kB or 67% of the original size.
Potential reduce by 402.8 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. Fazilsay.com needs all CSS files to be minified and compressed as it can save up to 402.8 kB or 83% of the original size.
Number of requests can be reduced by 48 (68%)
71
23
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fazil Say. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
fazilsay.com
1899 ms
language-selector.css
78 ms
css
25 ms
styles.css
132 ms
settings.css
139 ms
style.css
150 ms
navigation.css
151 ms
cms-navigation-base.css
153 ms
cms-navigation.css
150 ms
css
36 ms
normalize.css
196 ms
foundation.min.css
205 ms
prettyPhoto.css
275 ms
style.css
234 ms
flexslider.css
228 ms
perla.css
226 ms
shortcodes.css
285 ms
shortcodes_responsive.css
283 ms
app.css
301 ms
jquery.js
319 ms
jquery-migrate.min.js
310 ms
jquery.themepunch.tools.min.js
388 ms
jquery.themepunch.revolution.min.js
343 ms
modernizr-2.6.2.js
342 ms
js
25 ms
jquery.mb.YTPlayer.js
426 ms
custom-video.js
382 ms
jquery.form.min.js
436 ms
scripts.js
436 ms
jquery.hoverIntent.r7.min.js
437 ms
superfish-1.7.4.min.js
509 ms
jRespond.min.js
509 ms
jquery.jpanelmenu.min.js
509 ms
jquery.flexslider-2.1-min.js
509 ms
jquery.equalHeights.js
549 ms
jquery.fitvids.js
549 ms
jquery.prettyPhoto.js
569 ms
soundmanager2-nodebug-jsmin.js
549 ms
mp3-player-button.js
551 ms
scripts.js
549 ms
wp-embed.min.js
508 ms
sitepress.js
477 ms
wp-emoji-release.min.js
525 ms
analytics.js
23 ms
bottom-arrow.png
224 ms
Grand-Bazaar-1210x540.jpg
530 ms
Yeni-Sarkilar-Banner-1210x540.jpg
447 ms
Say-Plays-Say-Banner-Main.jpg
518 ms
banner-1-1210x540.jpg
510 ms
banner-5-1210x540.jpg
503 ms
banner-6-1210x540.jpg
451 ms
banner-7-1210x540.jpg
528 ms
banner-8-1210x540.jpg
599 ms
fazil-say-footer-logo.png
575 ms
all.js
306 ms
2334dvCgXS0
150 ms
bg_footer.png
569 ms
collect
9 ms
collect
186 ms
intervalsanspro-ultralight-webfont.woff
468 ms
2334dvCgXS0
117 ms
iframe_api
109 ms
www-embed-player-vflfNyN_r.css
62 ms
www-embed-player.js
82 ms
www-widgetapi.js
127 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
101 ms
ad_status.js
151 ms
156 ms
xd_arbiter.php
231 ms
xd_arbiter.php
446 ms
ping
40 ms
left2.png
77 ms
right2.png
76 ms
fazilsay.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fazilsay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fazilsay.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fazilsay.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fazilsay.com 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.
fazilsay.com
Open Graph data is detected on the main page of Fazil Say. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: