2.9 sec in total
153 ms
2.5 sec
263 ms
Visit say.ac now to see the best up-to-date Say content for Turkey and also check out these interesting facts you probably never knew about say.ac
Ziyaretçi analiz yazılımı ile sitenizin ziyaretçi profili hakkında bilgi sahibi olmak ister misiniz?
Visit say.acWe analyzed Say.ac page load time and found that the first response time was 153 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
say.ac performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value11.3 s
0/100
25%
Value7.7 s
25/100
10%
Value390 ms
69/100
30%
Value0.036
100/100
15%
Value11.5 s
18/100
10%
153 ms
22 ms
35 ms
44 ms
83 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 36% of them (37 requests) were addressed to the original Say.ac, 14% (14 requests) were made to Gravatar.com and 12% (12 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Gravatar.com.
Page size can be reduced by 1.1 MB (60%)
1.8 MB
712.5 kB
In fact, the total size of Say.ac main page is 1.8 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. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 46.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 7.7 kB, which is 13% 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 46.8 kB or 82% of the original size.
Potential reduce by 13.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. Say images are well optimized though.
Potential reduce by 840.5 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 840.5 kB or 70% of the original size.
Potential reduce by 160.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. Say.ac needs all CSS files to be minified and compressed as it can save up to 160.3 kB or 82% of the original size.
Number of requests can be reduced by 69 (74%)
93
24
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 39 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
en
153 ms
css
22 ms
css
35 ms
css
44 ms
site.css
83 ms
advertisement.js
151 ms
jquery.min.js
377 ms
jquery-ui.min.css
154 ms
jquery-ui.min.js
609 ms
tipsy.css
155 ms
jquery.tipsy.js
160 ms
jquery.alerts.css
225 ms
jquery.alerts.js
231 ms
bootstrap.min.css
309 ms
bootstrap.min.js
320 ms
font-awesome.min.css
305 ms
moment-with-locales.min.js
686 ms
bootstrap-datetimepicker.min.js
455 ms
bootstrap-datetimepicker.min.css
390 ms
jquery.noty.packaged.min.js
400 ms
jquery.form.min.js
41 ms
swfobject.js
450 ms
jquery.countTo.js
461 ms
adsbygoogle.js
19 ms
react-with-addons.min.js
722 ms
react-dom.min.js
525 ms
angular.min.js
680 ms
all.min.js
537 ms
bootstrap_fix.css
600 ms
fix2.css
653 ms
uygulama.js
676 ms
genel.js
680 ms
genel.js
715 ms
v2.php
760 ms
api.js
19 ms
watch.js
242 ms
recaptcha__en.js
187 ms
ba2aedb93089852438863aa6dfa9f982
345 ms
logo.png
104 ms
yukleniyor.gif
103 ms
google-play.png
103 ms
jquery-mobile.png
101 ms
tr.gif
453 ms
en.gif
452 ms
5a34afe2313fed55c20e22327cc0c72b
454 ms
515110003825274b3d8fa6a45652466b
476 ms
c9f4b848d295b12babaa73074a1450ac
450 ms
2a3fae75b092acf989039075da46d1e1
464 ms
a1b2f403986468474e2c0cc03dd568af
474 ms
f01003d207d5d830c5387a00d4f0d5ed
1079 ms
cf07b447c9704643d56f063ec1bd2b72
1086 ms
264b73b64c7e9e6149df55471808c924
684 ms
9eb46053e47ec4b7711112eb2f8f213a
1086 ms
69f03180912a12a7b048b3d2fa7f755d
1084 ms
75ee4f60afc309c99bf66f640b804c29
704 ms
12ef85698071858a2b522162e232c8c2
703 ms
da62c4639c984fd84311cfc55d7a6f6b
1082 ms
sdk.js
256 ms
bg.jpg
244 ms
pFZGRS3ywNfpSqkEIed1Ww.ttf
156 ms
gMhvhm-nVj1086DvGgmzB6CWcynf_cDxXwCLxiixG1c.ttf
212 ms
WtcvfJHWXKxx4x0kuS1koaCWcynf_cDxXwCLxiixG1c.ttf
214 ms
nsLtvfQoT-rVwGTHHnkeJqCWcynf_cDxXwCLxiixG1c.ttf
214 ms
fontawesome-webfont.woff
243 ms
ca-pub-3355496249787731.js
113 ms
zrt_lookup.html
145 ms
show_ads_impl.js
69 ms
AWM5wXtMJeRP-AcRTgT4qQ.ttf
196 ms
l1cOQ90roY9yC7voEhngDKCWcynf_cDxXwCLxiixG1c.ttf
196 ms
dI-qzxlKVQA6TUC5RKSb36CWcynf_cDxXwCLxiixG1c.ttf
196 ms
widgets.js
62 ms
j8TTE1lYwZNO3dMi2V8X6g.js
618 ms
ads
321 ms
osd.js
36 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
88 ms
ads
257 ms
watch.js
857 ms
ads
441 ms
syndication
175 ms
640212785457180672
404 ms
178 ms
xd_arbiter.php
163 ms
xd_arbiter.php
386 ms
widget_v2.132.js
17 ms
__$$__stringtable_lang_tr.js
31 ms
suggestion_autolayout_V2_8.css
33 ms
suggestion_autolayout_V2_8.js
36 ms
layout_engine.js
43 ms
abg.js
119 ms
suggestion_autolayout_V2_7.css
152 ms
suggestion_autolayout_V2_7.js
38 ms
googlelogo_color_112x36dp.png
189 ms
15430157330071937739
134 ms
8415006107672227591
187 ms
s
126 ms
x_button_blue2.png
120 ms
12650949246296599418
73 ms
m_js_controller.js
42 ms
feedback-tab.png
366 ms
nessie_icon_tiamat_white.png
324 ms
avatar_simple_visitor.png
92 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
40 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
42 ms
say.ac accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
say.ac best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
say.ac SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
TR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Say.ac 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 Say.ac 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.
say.ac
Open Graph description is not detected on the main page of Say. 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: