52.8 sec in total
14.4 sec
37.4 sec
1 sec
Click here to check amazing Nasleshahvar content for Iran. Otherwise, check out these important facts you probably never knew about nasleshahvar.ir
Visit nasleshahvar.irWe analyzed Nasleshahvar.ir page load time and found that the first response time was 14.4 sec and then it took 38.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
nasleshahvar.ir performance score
14379 ms
2289 ms
8616 ms
10545 ms
1153 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 98% of them (93 requests) were addressed to the original Nasleshahvar.ir, 1% (1 request) were made to Google-analytics.com and 1% (1 request) were made to Meraatnews.com. The less responsive or slowest element that took the longest time to load (19.7 sec) belongs to the original domain Nasleshahvar.ir.
Page size can be reduced by 385.8 kB (46%)
840.7 kB
455.0 kB
In fact, the total size of Nasleshahvar.ir main page is 840.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. 25% of websites need less resources to load. Images take 373.3 kB which makes up the majority of the site volume.
Potential reduce by 168.0 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 168.0 kB or 69% of the original size.
Potential reduce by 38.0 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. Nasleshahvar images are well optimized though.
Potential reduce by 32.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 32.0 kB or 60% of the original size.
Potential reduce by 147.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. Nasleshahvar.ir needs all CSS files to be minified and compressed as it can save up to 147.8 kB or 87% of the original size.
Number of requests can be reduced by 3 (3%)
92
89
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nasleshahvar. 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 CSS and as a result speed up the page load time.
nasleshahvar.ir
14379 ms
0040839bbe1450cbb469cd377bdfa7f9.css
2289 ms
css_240b9041cdfa79539b99287bd07bcc95.css
8616 ms
js_188091183d8fb19f2ecb57786cbdb188.js
10545 ms
style.css
1153 ms
sam.png
511 ms
header.png
8789 ms
MenuSep.png
512 ms
search.png
768 ms
searchbtn.png
509 ms
body.jpg
1054 ms
g1_body.jpg
1050 ms
105_31.jpg
2408 ms
116_21.jpg
2363 ms
104_34.jpg
2475 ms
3_321.jpg
4004 ms
2_331.jpg
2767 ms
41_60.jpg
2827 ms
15_259.jpg
2892 ms
101_43.jpg
2937 ms
100_37.jpg
3249 ms
35_108.jpg
3281 ms
104_33.jpg
3327 ms
85_27.jpg
3446 ms
109_22.jpg
3737 ms
93_36.jpg
3770 ms
107_31.jpg
3933 ms
87_33.jpg
3963 ms
82_41.jpg
5226 ms
80_8.gif
4760 ms
80_7.gif
6356 ms
80_5.gif
4952 ms
80_4.gif
4953 ms
80_3.gif
6005 ms
80_2.gif
7522 ms
80_0.gif
6924 ms
117_24.jpg
6475 ms
3_320.jpg
6492 ms
2_330.jpg
6828 ms
55_61.jpg
6886 ms
1_422.jpg
6456 ms
21_229.jpg
6803 ms
20_243.jpg
7811 ms
19_233.jpg
6674 ms
analytics.js
520 ms
piwik.js
2884 ms
18_241.jpg
6544 ms
17_243.jpg
6721 ms
17_245.jpg
6840 ms
105_29.jpg
5532 ms
99.1_0.jpg
5550 ms
201_16.jpg
5754 ms
3.3_5.jpg
5604 ms
54_48.jpg
5542 ms
6_283.jpg
5516 ms
96_29.jpg
5796 ms
0.0_2.jpg
5626 ms
2_318.jpg
5649 ms
83_33.jpg
5615 ms
88_28.jpg
6985 ms
114_20.jpg
5608 ms
113_25.jpg
5659 ms
nasleshahvar.ir
19651 ms
112_19.jpg
5625 ms
108_25.jpg
5834 ms
106_28.jpg
5116 ms
103_37.jpg
4956 ms
101_44.jpg
5043 ms
100_40.jpg
5050 ms
99_31.jpg
4325 ms
98_32.jpg
3990 ms
95_32.jpg
3943 ms
94_31.jpg
4246 ms
slider_header.jpg
4026 ms
slider_footer.jpg
3964 ms
headnews.6.png
3940 ms
headnews_body.jpg
4272 ms
headnews_seperator.jpg
4033 ms
headnews_footer.jpg
3923 ms
headnews.5.png
3922 ms
headnews.4.png
4145 ms
headnews.3.png
4059 ms
headnews.2.png
3949 ms
headnews.1.png
3968 ms
news_headerdff.jpg
3906 ms
news_footer.png
3917 ms
box_header.png
3996 ms
box_body.png
3982 ms
icon_bolt_16.png
3966 ms
box_footer.png
3928 ms
32_98.jpg
3871 ms
31_99.jpg
4360 ms
footer.png
4267 ms
footer_gotop.png
4212 ms
css_938d26cfae9d2c770ef1e07a5c24e1f7.css
292 ms
nasleshahvar.ir SEO score
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nasleshahvar.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Nasleshahvar.ir 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.
nasleshahvar.ir
Open Graph description is not detected on the main page of Nasleshahvar. 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: