4.2 sec in total
412 ms
3.1 sec
616 ms
Visit farzand.net now to see the best up-to-date Farzand content for Iran and also check out these interesting facts you probably never knew about farzand.net
کلیه اطلاعات پیرامون بارداری، سلامت خانواده و نگهداری از کودکان. به همراه اطلاعات تکمیلی پیرامون رشد و تربیت کودکان.
Visit farzand.netWe analyzed Farzand.net page load time and found that the first response time was 412 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
farzand.net performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value8.8 s
1/100
25%
Value10.3 s
8/100
10%
Value480 ms
59/100
30%
Value0.004
100/100
15%
Value9.6 s
29/100
10%
412 ms
400 ms
183 ms
72 ms
166 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 13% of them (9 requests) were addressed to the original Farzand.net, 24% (17 requests) were made to Static.farzand.net and 18% (13 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Static.farzand.net.
Page size can be reduced by 146.2 kB (35%)
418.7 kB
272.5 kB
In fact, the total size of Farzand.net main page is 418.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. 60% of websites need less resources to load. Images take 208.7 kB which makes up the majority of the site volume.
Potential reduce by 85.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 35.9 kB, which is 36% 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 85.5 kB or 85% of the original size.
Potential reduce by 9.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. Farzand images are well optimized though.
Potential reduce by 51.2 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 51.2 kB or 47% of the original size.
Potential reduce by 309 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. Farzand.net needs all CSS files to be minified and compressed as it can save up to 309 B or 67% of the original size.
Number of requests can be reduced by 21 (36%)
59
38
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Farzand. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
farzand.net
412 ms
sitecss
400 ms
head
183 ms
jquery.min.js
72 ms
glb
166 ms
pregnancy-calendar.gif
1086 ms
sprite.png
292 ms
02.png
291 ms
hmtab-parts.jpg
290 ms
tlg.channel.a.gif
1174 ms
201602241620.jpg
1175 ms
201602151140.jpg
1302 ms
201602071754.jpg
1215 ms
201601291028.jpg
1186 ms
201601241039.jpg
1296 ms
tlg.channel.c1.gif
1215 ms
ppy-cgMwbT.jpg
1230 ms
10.jpg
1283 ms
7.jpg
1281 ms
6.jpg
1281 ms
sB3JQ1MwYN.jpg
1276 ms
uH9VSoswWi.jpg
1354 ms
platform.js
195 ms
analytics.js
121 ms
js15_as.js
120 ms
88x31.png
112 ms
NotoNaskhArabic-Regular.woff
185 ms
fontawesome-webfont.woff
227 ms
NotoKufiArabic-Regular.woff
220 ms
fontawesomeextend.woff
336 ms
0.php
77 ms
linkid.js
27 ms
get_camp.php
695 ms
collect
37 ms
collect
153 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
66 ms
fastbutton
243 ms
page
383 ms
postmessageRelay
171 ms
cb=gapi.loaded_0
72 ms
cb=gapi.loaded_1
69 ms
api.js
136 ms
core:rpc:shindig.random:shindig.sha1.js
267 ms
2536007149-postmessagerelay.js
148 ms
rs=AGLTcCO-ugZ8INW0vzyfuKiOAJm2TrasaA
90 ms
rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA
108 ms
rs=AGLTcCNlWHV_AUuWkPObcnyVkHi9LgmdYQ
213 ms
photo.jpg
266 ms
rs=AGLTcCNlWHV_AUuWkPObcnyVkHi9LgmdYQ
27 ms
grlryt2bdKIyfMSOhzd1eA.woff
51 ms
d-QWLnp4didxos_6urzFtg.woff
153 ms
vxNK-E6B13CyehuDCmvQvw.woff
150 ms
rs=AGLTcCNlWHV_AUuWkPObcnyVkHi9LgmdYQ
41 ms
showcamp.php
405 ms
ppy-cgmwbt.jpg
147 ms
sb3jq1mwyn.jpg
100 ms
jsEngine.js
390 ms
font.css
398 ms
show.js
134 ms
uh9vsoswwi.jpg
91 ms
227 ms
5239.gif
799 ms
fp.js
129 ms
banner_saba_logo_small.png
199 ms
Yekan.woff
395 ms
show.php
324 ms
clickyab-tiny.png
103 ms
conversion.js
18 ms
7658206-3-shanbe-soori-728-90.gif
283 ms
36 ms
34 ms
farzand.net 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
farzand.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
farzand.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Farzand.net 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 Farzand.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.
farzand.net
Open Graph data is detected on the main page of Farzand. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: