4.7 sec in total
424 ms
3.2 sec
1.1 sec
Welcome to faradars.org homepage info - get ready to check Faradars best content for Iran right away, or after learning these important things about faradars.org
بزرگ ترین پروژه آموزش آنلاین ایران - ارائه آموزشهای ویدئویی و فیلمهای آموزشی هوش مصنوعی، مهندسی کامپیوتر، برق، مکانیک، عمران، صنایع و سایر رشتههای مهندسی
Visit faradars.orgWe analyzed Faradars.org page load time and found that the first response time was 424 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
faradars.org performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value11.1 s
0/100
25%
Value11.7 s
4/100
10%
Value2,830 ms
3/100
30%
Value0.014
100/100
15%
Value16.7 s
5/100
10%
424 ms
186 ms
173 ms
28 ms
170 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 90% of them (130 requests) were addressed to the original Faradars.org, 3% (5 requests) were made to Google.com and 2% (3 requests) were made to V2.zopim.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Trustseal.enamad.ir.
Page size can be reduced by 587.0 kB (32%)
1.8 MB
1.2 MB
In fact, the total size of Faradars.org main page is 1.8 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 139.7 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 139.7 kB or 85% of the original size.
Potential reduce by 14.7 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. Faradars images are well optimized though.
Potential reduce by 275.5 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 275.5 kB or 71% of the original size.
Potential reduce by 157.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. Faradars.org needs all CSS files to be minified and compressed as it can save up to 157.1 kB or 85% of the original size.
Number of requests can be reduced by 49 (35%)
140
91
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faradars. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
faradars.org
424 ms
wp-emoji-release.min.js
186 ms
wgs.css
173 ms
css
28 ms
lightbox.css
170 ms
styles.css
173 ms
styles-rtl.css
191 ms
pagenavi-css.css
196 ms
prettyPhoto.css
255 ms
jquery.js
343 ms
jquery-migrate.min.js
256 ms
modernizr.js
284 ms
rtl.css
403 ms
media-queries_rtl.css
295 ms
custom.css
338 ms
google_cse_v2.js
262 ms
comment-reply.min.js
324 ms
jquery.form.min.js
357 ms
scripts.js
505 ms
qppr_frontend_script.min.js
505 ms
jquery.prettyPhoto.min.js
510 ms
jquery.prettyPhoto.init.min.js
512 ms
add-to-cart.min.js
512 ms
jquery.blockUI.min.js
514 ms
jquery.placeholder.min.js
515 ms
woocommerce.min.js
516 ms
jquery.cookie.min.js
517 ms
cart-fragments.min.js
518 ms
wp-embed.min.js
519 ms
respond.min.js
557 ms
js
27 ms
lightbox.js
569 ms
gmap3.min.js
571 ms
jquery.easing.1.3.js
572 ms
functions.js
606 ms
jquery.tweet.js
605 ms
easing.js
609 ms
jquery.ui.totop.js
604 ms
rtl-shortcodes.css
603 ms
jquery.cookie.js
522 ms
logo.aspx
1718 ms
close.png
784 ms
loading.gif
782 ms
prev.png
782 ms
next.png
782 ms
FaraDars-Header-A.png
783 ms
faradars-profile-picture.png
794 ms
icon-huge-packs.png
792 ms
icon-academic-writing.png
789 ms
icon-programming.png
786 ms
oloom.png
789 ms
hosh.png
786 ms
amar.png
792 ms
ga.js
158 ms
icon-ee.png
762 ms
icon-mech.png
759 ms
icon-civil.png
615 ms
icon-ctrl.png
609 ms
icon-or.png
610 ms
olumtajrobi.png
610 ms
icon-common.png
609 ms
modirat2.png
609 ms
icon-general.png
607 ms
icon-plus.png
607 ms
fvmec94082e-146x164.png
617 ms
fvh4c94061u-146x164.png
666 ms
fvh4c94061t-146x164.png
606 ms
cse.js
52 ms
Yekan.woff
645 ms
__utm.gif
25 ms
fvh4c94061d-146x164.png
570 ms
fvh4c94061c-146x164.png
577 ms
FVMEC105I-146x164.png
607 ms
cse.js
524 ms
FVMEC105E-146x164.png
641 ms
fvmth10212-146x164.png
682 ms
FVCMS9408-146x164.png
798 ms
FVWP93076-1-146x164.png
789 ms
FVCTR94082-146x164.png
787 ms
FVMEC94082-1-146x164.png
793 ms
faradars.org
853 ms
admin-ajax.php
1696 ms
fvh4c94061-1-146x164.png
307 ms
FVORC9410-1-146x164.png
305 ms
fvjs9406-a-146x164.png
306 ms
FVMEC105-146x164.png
410 ms
FVSFTE106-1-146x164.png
387 ms
FVSFTE105-146x164.png
390 ms
fvsfte104-146x164.png
395 ms
fvsft109-2-146x164.png
379 ms
Tick-mark-icon-png-66199.png
615 ms
fvrc101-3-146x164.png
615 ms
fvsql9311-1-146x164.png
615 ms
fvst9405-1-146x164.png
615 ms
FVDS9401-146x164.png
615 ms
MVRMA9202-aa-1-146x164.png
615 ms
fvrj101-1-146x164.png
615 ms
FVSIM94072-146x164.png
615 ms
fvee101-146x164.png
615 ms
mvrfz9105-1-146x164.png
619 ms
mvrimg91051-145x164.png
738 ms
mvrga9011-1-146x164.png
739 ms
FVXL9412-146x164.png
740 ms
jsapi
40 ms
FVASMB9410a-1-146x164.png
736 ms
FVPWR94113-1-146x164.png
730 ms
FVMEC106-146x164.png
724 ms
FVEE93111-146x164.png
716 ms
default+en.css
4 ms
shiny.css
45 ms
default+en.I.js
47 ms
FVEE94112-1-146x164.png
707 ms
FVSQL9411-146x164.png
739 ms
FVHM9411-146x164.png
717 ms
shiny.css
44 ms
FVCTR104-146x164.png
706 ms
FVWB9411-146x164.png
591 ms
FVR9412-146x164.png
697 ms
FVACC9412-146x164.png
607 ms
iran.png
606 ms
roozafarin.png
609 ms
netstart1.png
681 ms
FaraDars-Logo.png
690 ms
nashr.png
696 ms
behpardakht.png
617 ms
pec-logo.png
1281 ms
sep-logo11.png
1279 ms
email.png
1269 ms
twitter.png
1263 ms
widget_v2.132.js
21 ms
__$$__stringtable_lang_fa.js
43 ms
facebook.png
1047 ms
google.png
1051 ms
vimeo.png
1047 ms
youtube.png
1047 ms
telegram.png
1045 ms
insta.jpg
1047 ms
cart.png
1046 ms
enlarge.png
1045 ms
open.png
1043 ms
star.png
923 ms
bullet_arrow_social.png
920 ms
ajax-loader.gif
920 ms
to_top.png
920 ms
avatar_simple_visitor.png
316 ms
faradars.org 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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.
faradars.org 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
Page has valid source maps
faradars.org 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
N/A
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faradars.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Persian. Our system also found out that Faradars.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.
faradars.org
Open Graph data is detected on the main page of Faradars. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: