10.2 sec in total
3 sec
6.9 sec
307 ms
Click here to check amazing Haznevi content for Turkey. Otherwise, check out these important facts you probably never knew about haznevi.net
Visit haznevi.netWe analyzed Haznevi.net page load time and found that the first response time was 3 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
haznevi.net performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.7 s
1/100
25%
Value8.7 s
16/100
10%
Value630 ms
47/100
30%
Value0.015
100/100
15%
Value5.9 s
66/100
10%
3014 ms
260 ms
263 ms
420 ms
24 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 95% of them (90 requests) were addressed to the original Haznevi.net, 4% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Haznevi.net.
Page size can be reduced by 605.1 kB (37%)
1.6 MB
1.0 MB
In fact, the total size of Haznevi.net main page is 1.6 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. 50% of websites need less resources to load. Images take 894.0 kB which makes up the majority of the site volume.
Potential reduce by 77.5 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 14.5 kB, which is 16% 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 77.5 kB or 86% of the original size.
Potential reduce by 39.4 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. Haznevi images are well optimized though.
Potential reduce by 314.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 314.0 kB or 70% of the original size.
Potential reduce by 174.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. Haznevi.net needs all CSS files to be minified and compressed as it can save up to 174.3 kB or 85% of the original size.
Number of requests can be reduced by 19 (21%)
90
71
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Haznevi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.haznevi.net
3014 ms
wp-emoji-release.min.js
260 ms
styles.css
263 ms
settings.css
420 ms
css
24 ms
style.css
434 ms
responsive.css
294 ms
prettyPhoto.css
389 ms
font-awesome.min.css
391 ms
www.haznevi.net
2142 ms
jquery.js
654 ms
jquery-migrate.min.js
522 ms
jquery.themepunch.tools.min.js
707 ms
jquery.themepunch.revolution.min.js
721 ms
jquery.prettyPhoto.js
655 ms
comment-reply.min.js
158 ms
jquery.form.min.js
132 ms
scripts.js
133 ms
retina.min.js
145 ms
bunyad-theme.js
280 ms
jquery.flexslider-min.js
262 ms
jquery.sticky-sidebar.min.js
263 ms
10021-702x336.jpg
755 ms
10011-702x336.jpg
329 ms
10001-702x336.jpg
386 ms
10001-702x336.jpg
389 ms
1003-702x336.jpg
567 ms
1002-702x336.jpg
558 ms
1001-702x336.jpg
729 ms
10031-351x185.jpg
637 ms
1001-168x137.jpg
536 ms
10001-168x137.jpg
651 ms
50084-214x140.jpg
832 ms
10154-214x140.jpg
850 ms
2000-214x140.jpg
768 ms
10092-351x185.jpg
906 ms
10082-110x96.jpg
858 ms
10072-110x96.jpg
876 ms
10062-110x96.jpg
897 ms
400810-351x185.jpg
1110 ms
400711-110x96.jpg
992 ms
400613-110x96.jpg
1011 ms
400414-110x96.jpg
1020 ms
10061-351x185.jpg
1150 ms
100133-110x96.jpg
1036 ms
10055-110x96.jpg
1135 ms
10044-110x96.jpg
1165 ms
5016-351x185.jpg
1308 ms
40201-110x96.jpg
1167 ms
4019-110x96.jpg
1252 ms
4018-110x96.jpg
1278 ms
1010-351x185.jpeg
1531 ms
10142-110x96.jpg
1316 ms
10132-110x96.jpg
1298 ms
10116-110x96.jpg
1392 ms
10104-110x96.jpg
1422 ms
50051-351x185.jpg
1559 ms
50041-110x96.jpg
1452 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
25 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
67 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
68 ms
y7lebkjgREBJK96VQi37ZobN6UDyHWBl620a-IRfuBk.woff
69 ms
fontawesome-webfont.woff
1452 ms
50032-110x96.jpg
1153 ms
50022-110x96.jpg
1185 ms
50012-110x96.jpg
1059 ms
5021-351x185.gif
1239 ms
5020-110x96.gif
1118 ms
50191-110x96.gif
1057 ms
50181-110x96.gif
1066 ms
10021-110x96.jpg
1051 ms
1003-110x96.jpg
1094 ms
10232-110x96.jpg
1054 ms
10221-110x96.jpg
1029 ms
10213-110x96.jpg
1053 ms
hz-110x96.jpg
1072 ms
1011-110x96.jpg
1044 ms
1176151_296534047155295_144175860_n-110x96.jpg
1056 ms
1015-110x96.jpg
1056 ms
1016-110x96.jpg
1011 ms
4015-110x96.jpeg
1036 ms
40137-110x96.jpg
1028 ms
40128-110x96.jpg
1045 ms
40117-110x96.jpg
973 ms
40098-110x96.jpg
965 ms
10051-110x96.jpg
997 ms
10041-110x96.jpg
1026 ms
1003-110x96.jpg
1010 ms
10001-110x96.jpg
979 ms
10101-110x96.jpg
933 ms
46-110x96.jpg
941 ms
1492048_10152129406318676_1054583137_o-110x96.jpg
982 ms
5053-110x96.jpg
988 ms
5023-110x96.jpg
944 ms
5021-110x96.jpg
919 ms
haznevi.net 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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
haznevi.net 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
haznevi.net SEO score
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
TR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haznevi.net 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 Haznevi.net 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.
haznevi.net
Open Graph description is not detected on the main page of Haznevi. 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: