22.8 sec in total
4.8 sec
17.4 sec
531 ms
Click here to check amazing Rcast content. Otherwise, check out these important facts you probably never knew about rcast.ac.ir
Visit rcast.ac.irWe analyzed Rcast.ac.ir page load time and found that the first response time was 4.8 sec and then it took 18 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
rcast.ac.ir performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value3.9 s
52/100
25%
Value8.0 s
22/100
10%
Value130 ms
97/100
30%
Value0.29
42/100
15%
Value7.0 s
53/100
10%
4825 ms
1069 ms
26 ms
459 ms
464 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 88% of them (59 requests) were addressed to the original Rcast.ac.ir, 4% (3 requests) were made to 0.gravatar.com and 3% (2 requests) were made to 1.gravatar.com. The less responsive or slowest element that took the longest time to load (9.8 sec) belongs to the original domain Rcast.ac.ir.
Page size can be reduced by 624.8 kB (30%)
2.1 MB
1.4 MB
In fact, the total size of Rcast.ac.ir main page is 2.1 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. 40% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 141.3 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 141.3 kB or 84% of the original size.
Potential reduce by 114.6 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. Rcast images are well optimized though.
Potential reduce by 175.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 175.0 kB or 70% of the original size.
Potential reduce by 193.9 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. Rcast.ac.ir needs all CSS files to be minified and compressed as it can save up to 193.9 kB or 86% of the original size.
Number of requests can be reduced by 15 (23%)
64
49
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rcast. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.rcast.ac.ir
4825 ms
style.css
1069 ms
css
26 ms
styles.css
459 ms
styles-rtl.css
464 ms
animate.min.css
931 ms
jquery.js
1198 ms
jquery-migrate.min.js
684 ms
tie-scripts.js
1155 ms
rtl.css
916 ms
c.aspx
186 ms
jquery.bxslider.css
182 ms
jquery.form.min.js
361 ms
scripts.js
443 ms
public.min.js
1246 ms
wp-embed.min.js
568 ms
jquery.bxslider.js
717 ms
bxslider.setup.js
672 ms
wp-emoji-release.min.js
278 ms
6a845b72a3351fbc0b0473cd5cb52aa1
132 ms
48b9cddeb9b6acad8698ce664a995d42
122 ms
6f3de21f5759217507e8e4acb2f65465
235 ms
feda075c3f707fb98a25103232e86708
245 ms
d3e448ce45accb3566e1e79046581927
220 ms
body-bg5.png
244 ms
logo-5252.png
959 ms
main-menu-bg.png
362 ms
home.png
374 ms
loading1.gif
369 ms
13.jpg
1237 ms
15.jpg
2185 ms
16.jpg
957 ms
12.jpg
1527 ms
11.jpg
9781 ms
139412141116251917266904-150x150.jpg
954 ms
etelaEye-150x150.jpg
1076 ms
thumb2_219466-150x150.jpg
1111 ms
240564_631-e1448185962964-150x150.jpg
1268 ms
IMG_0852-150x150.jpg
1322 ms
IMG_0765-150x150.jpg
1485 ms
rahbari-93.jpg
1450 ms
riasatjomhoori.jpg
1500 ms
vezarat.jpg
1628 ms
IMG_%DB%B2%DB%B0%DB%B1%DB%B4%DB%B1%DB%B2%DB%B2%DB%B9_%DB%B0%DB%B9%DB%B2%DB%B8%DB%B5%DB%B1-55x55.jpg
1724 ms
etelaEye-55x55.jpg
1679 ms
1Ezx-55x55.jpg
1759 ms
Ashoora1-55x55.jpg
1808 ms
IMG_0765-55x55.jpg
1858 ms
139412141116251917266904-55x55.jpg
1964 ms
thumb2_219466-55x55.jpg
1991 ms
240564_631-e1448185962964-55x55.jpg
1986 ms
139412141116251917266904-290x195.jpg
2038 ms
etelaEye-290x195.jpg
2203 ms
thumb2_219466-285x195.jpg
2164 ms
12345.jpg
2429 ms
yekan.woff
2200 ms
xstat.aspx
216 ms
tiefontello.svg
2227 ms
tiefontello.woff
2482 ms
logo.png
2276 ms
arrows.simple.png
2198 ms
stripe.png
2180 ms
black-loader.gif
2309 ms
sidebar-bullet.png
2348 ms
admin-ajax.php
3625 ms
Telegram-1-5.jpg
712 ms
close.png
182 ms
rcast.ac.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
rcast.ac.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
rcast.ac.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
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
EN
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rcast.ac.ir can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Persian language. Our system also found out that Rcast.ac.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.
rcast.ac.ir
Open Graph description is not detected on the main page of Rcast. 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: