13 sec in total
1.7 sec
11 sec
288 ms
Welcome to nano.ir homepage info - get ready to check Nano best content for Iran right away, or after learning these important things about nano.ir
ایده بکر مبین
Visit nano.irWe analyzed Nano.ir page load time and found that the first response time was 1.7 sec and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
nano.ir performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value13.7 s
0/100
25%
Value17.4 s
0/100
10%
Value820 ms
35/100
30%
Value0.037
100/100
15%
Value16.0 s
6/100
10%
1700 ms
382 ms
383 ms
903 ms
453 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 40% of them (49 requests) were addressed to the original Nano.ir, 55% (67 requests) were made to Irannano.org and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source Irannano.org.
Page size can be reduced by 1.0 MB (21%)
4.9 MB
3.9 MB
In fact, the total size of Nano.ir main page is 4.9 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 3.6 MB which makes up the majority of the site volume.
Potential reduce by 62.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. 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 62.5 kB or 84% of the original size.
Potential reduce by 63.2 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. Nano images are well optimized though.
Potential reduce by 735.6 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 735.6 kB or 72% of the original size.
Potential reduce by 160.1 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. Nano.ir needs all CSS files to be minified and compressed as it can save up to 160.1 kB or 84% of the original size.
Number of requests can be reduced by 41 (34%)
120
79
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nano. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
nano.ir
1700 ms
reset.css
382 ms
nassim.css
383 ms
font_icon.css
903 ms
tablesorter.css
453 ms
style.css
1158 ms
style-rtl.css
572 ms
jquery-ui-1.8.22.custom.css
953 ms
customize-rtl.css
679 ms
jquery-1.7.2.min.js
1144 ms
jquery-ui-1.8.22.custom.min.js
2089 ms
jquery-migrate-1.1.1.js
1130 ms
jquery.cookie.js
1129 ms
jquery.raty.js
1146 ms
customize.js
1356 ms
jquery.ui.datepicker-cc.all.min.js
2033 ms
password_meter.js
1337 ms
script.js
2284 ms
jquery.tablesorter.min.js
2081 ms
jwplayer.js
2302 ms
perfect-scrollbar.css
1583 ms
jquery.mousewheel.min.js
1811 ms
perfect-scrollbar.js
2264 ms
highcharts.js
3839 ms
highcharts-more.js
2545 ms
exporting.js
2279 ms
fileuploader.js
2947 ms
mediaelement-and-player.min.js
2852 ms
mediaelementplayer.css
2663 ms
menu.css
2485 ms
google_analytics.js
929 ms
center_loder.gif
384 ms
filereader.php
720 ms
tile.png
195 ms
strip.png
457 ms
inic.png
196 ms
setting.png
240 ms
rss.png
197 ms
subject.png
229 ms
prev.png
387 ms
pause.png
387 ms
next.png
388 ms
loader.gif
456 ms
filereader.php
799 ms
filereader.php
808 ms
filereader.php
624 ms
filereader.php
1141 ms
filereader.php
948 ms
filereader.php
1236 ms
filereader.php
1420 ms
filereader.php
1208 ms
filereader.php
1223 ms
filereader.php
1424 ms
filereader.php
1824 ms
filereader.php
1826 ms
filereader.php
1827 ms
filereader.php
1650 ms
filereader.php
2132 ms
filereader.php
2146 ms
filereader.php
2625 ms
filereader.php
2513 ms
filereader.php
2239 ms
filereader.php
2440 ms
filereader.php
2380 ms
filereader.php
2401 ms
filereader.php
2450 ms
filereader.php
2627 ms
filereader.php
2650 ms
filereader.php
2658 ms
filereader.php
3153 ms
filereader.php
2749 ms
filereader.php
2851 ms
filereader.php
2883 ms
filereader.php
2889 ms
filereader.php
2868 ms
filereader.php
4799 ms
filereader.php
3269 ms
filereader.php
3879 ms
nassim-regular.woff
1146 ms
nassim-bold.woff
937 ms
analytics.js
130 ms
up.png
446 ms
close.png
446 ms
save.png
548 ms
setting_b.png
549 ms
ext_link.png
639 ms
eNamadLogo.htm
635 ms
linkid.js
11 ms
collect
12 ms
filereader.php
2521 ms
filereader.php
2445 ms
symbol.aspx
382 ms
filereader.php
3292 ms
filereader.php
3051 ms
thumbnail_9711b50fc32af4d70d448f1c82c90b9c.jpg
2806 ms
thumbnail_ec65f0efda9ab16b5c82bcf14db7fea7.jpg
2749 ms
namad1.png
553 ms
thumbnail_13e9e0028a76316706c64871af6c1575.jpg
3137 ms
thumbnail_69982e22b5abb61e28bf55328de68487814.jpg
3106 ms
thumbnail_c4ca4238a0b923820dcc509a6f75849b630.jpg
3243 ms
thumbnail_c81e728d9d4c2f636f067f89cc14862c422.jpg
2878 ms
thumbnail_eccbc87e4b5ce2fe28308fd9f2a7baf3433.jpg
3133 ms
thumbnail_a87ff679a2f3e71d9181a67b7542122c219456.jpg
3054 ms
thumbnail_e4da3b7fbbce2345d7772b0674a318d5124.jpg
2971 ms
thumbnail_1679091c5a880faf6fb5e6087eb1b2dc670.jpg
2917 ms
thumbnail_8f14e45fceea167a5a36dedd4bea2543638.jpg
3246 ms
thumbnail_96a3be3cf272e017046d1b2674a52bd3532.jpg
2893 ms
thumbnail_d72d187df41e10ea7d9fcdc7f5909205873.jpg
3161 ms
thumbnail_751d31dd6b56b26b29dac2c0e1839e34130.jpg
2906 ms
thumbnail_faeac4e1eef307c2ab7b0a3821e6c667310.jpg
2660 ms
thumbnail_c20ad4d76fe97759aa27a0c99bff6710249.jpg
2848 ms
thumbnail_c51ce410c124a10e0db5e4b97fc2af39926434.jpg
3050 ms
thumbnail_9bf31c7ff062936a96d3c8bd1f8f2ff3726.jpg
3058 ms
thumbnail_c74d97b01eae257e44aa9d5bade97baf906.jpg
2957 ms
thumbnail_98f13708210194c475687be6106a3b84537281.jpg
2915 ms
thumbnail_37693cfc748049e45d87b8c7d8b9aacd870.jpg
3077 ms
thumbnail_1ff1de774005f8da13f42943881c655f752.jpg
3062 ms
thumbnail_1c383cd30b7c298ab50293adfecb7b18669.jpg
3208 ms
thumbnail_d67d8ab4f4c10bf22aa353e27879133c286.jpg
3210 ms
thumbnail_e369853df766fa44e1ed0ff613f563bd168.jpg
3116 ms
thumbnail_d645920e395fedad7bbbed0eca3fe2e0940.jpg
3069 ms
nano.ir 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.
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
nano.ir 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
Browser errors were logged to the console
Page has valid source maps
nano.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nano.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian 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 Nano.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.
nano.ir
Open Graph description is not detected on the main page of Nano. 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: