5.3 sec in total
314 ms
4.7 sec
312 ms
Welcome to zazaki.org homepage info - get ready to check Zazaki best content right away, or after learning these important things about zazaki.org
Zazaki.NET keyepelê arşîvkerdiş, seveknayîş û geşkerdişê kirmanckî (kirdkî, zazakî, dimilkî) yo: Xeberî, meqaleyî, hîkayeyî, şîîrî, fiqrayî, sanikî, fotografî, vîdeoyî...
Visit zazaki.orgWe analyzed Zazaki.org page load time and found that the first response time was 314 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
zazaki.org performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value14.9 s
0/100
25%
Value5.6 s
53/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value3.7 s
91/100
10%
314 ms
878 ms
130 ms
259 ms
257 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Zazaki.org, 97% (94 requests) were made to Zazaki.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Zazaki.net.
Page size can be reduced by 78.5 kB (12%)
642.7 kB
564.2 kB
In fact, the total size of Zazaki.org main page is 642.7 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. 35% of websites need less resources to load. Images take 564.0 kB which makes up the majority of the site volume.
Potential reduce by 44.1 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 44.1 kB or 82% of the original size.
Potential reduce by 33.5 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. Zazaki images are well optimized though.
Potential reduce by 592 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 277 B
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. Zazaki.org has all CSS files already compressed.
Number of requests can be reduced by 33 (35%)
94
61
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zazaki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
zazaki.org
314 ms
www.zazaki.net
878 ms
style.css
130 ms
index.css
259 ms
function.js
257 ms
banner.js
263 ms
ticker.js
285 ms
body_bck.gif
130 ms
main_container_bck.gif
139 ms
logo.gif
131 ms
last_min_bck.png
129 ms
ehmed-xas-2407.jpg
268 ms
usman-efendyo-babij-2324.jpg
383 ms
malmsanij-598.jpg
507 ms
2864.jpg
860 ms
1451.jpg
267 ms
1828.jpg
272 ms
2257.jpg
401 ms
1596.jpg
401 ms
3310.jpg
408 ms
3302.jpg
505 ms
2969.jpg
531 ms
2164.jpg
532 ms
2055.jpg
544 ms
3277.jpg
629 ms
1372.jpg
632 ms
newepel1.jpg
796 ms
1x1.gif
1035 ms
rosna1.jpg
680 ms
1_s.jpg
755 ms
3_s.jpg
759 ms
9_s.jpg
817 ms
11_s.jpg
881 ms
10_s.jpg
886 ms
13_s.jpg
928 ms
5_s.jpg
954 ms
12_s.jpg
1417 ms
14_s.jpg
1007 ms
sewcila1.jpg
1139 ms
3294.jpg
1226 ms
3210.jpg
1092 ms
25_s.jpg
1130 ms
24_s.jpg
1149 ms
ga.js
7 ms
__utm.gif
11 ms
131.jpg
1825 ms
wesanxanevate2.jpg
1145 ms
grubavate2.jpg
1149 ms
kovaravate2.jpg
1175 ms
kitabxane1.jpg
1104 ms
kitabxane2a.jpg
1130 ms
ferheng.jpg
1133 ms
1.jpg
1063 ms
sewcila-14.jpg
1101 ms
sewcila-13.jpg
1248 ms
sewcila-12.jpg
1123 ms
sewcila-11.jpg
1346 ms
sewcila-10.jpg
1202 ms
sewcila-9.jpg
1104 ms
sewcila-8.jpg
1126 ms
sewcila-7.jpg
1225 ms
sewcila-6.jpg
1271 ms
sewcila-5.jpg
1738 ms
sewcila-4.jpg
1427 ms
sewcila3.jpg
1145 ms
sewcila02.jpg
1515 ms
sewcila01.jpg
1358 ms
search_field_bck.png
1216 ms
search_submit_bck.png
1231 ms
quick_launch_bck.png
1287 ms
quick_launch_sep.png
1336 ms
quick_launch_item_happy.png
1313 ms
top_part_3_bck.png
1325 ms
top_nav_bck.png
1293 ms
top_nav_sep.png
1325 ms
base_bck.gif
1282 ms
currency_bck.png
1266 ms
currency_oops.gif
1595 ms
currency_up.gif
1269 ms
index_box_news_bck.png
1653 ms
cat_news_header_bck.png
1231 ms
cat_news_header_ender_bck.png
1243 ms
cat_news_header_inner_bck.png
1233 ms
icon_02.gif
1208 ms
right_caption_bck_3.png
1233 ms
right_content_bck.png
1248 ms
3321.jpg
1246 ms
right_bottom_bck.png
1268 ms
right_caption_bck.png
1255 ms
author_name_bck.png
1255 ms
right_caption_bck_book.png
1552 ms
icon_07.gif
1194 ms
icon_01.gif
1210 ms
main_video_items_bck.png
1178 ms
gazette_bck.png
1150 ms
footer_nav_bck.png
1130 ms
footer_nav_sep.png
1093 ms
zazaki.org accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
<object> elements do not have alternate text
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
zazaki.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
zazaki.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document uses plugins
TR
TR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zazaki.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 Zazaki.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.
zazaki.org
Open Graph description is not detected on the main page of Zazaki. 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: