8 sec in total
898 ms
6.7 sec
325 ms
Click here to check amazing Ric content for Iran. Otherwise, check out these important facts you probably never knew about ric.ir
سایت رسمی کارخانجات کابلسازی، شرکت تعاونی اسلامی مجتمع صنعتی رفسنجان، کابل فیبر نوری رفسنجان، کابل مخابراتی مسی رفسنجان، RIC CABLE
Visit ric.irWe analyzed Ric.ir page load time and found that the first response time was 898 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ric.ir performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value10.2 s
0/100
25%
Value13.9 s
1/100
10%
Value310 ms
77/100
30%
Value1.593
0/100
15%
Value14.5 s
9/100
10%
898 ms
1585 ms
62 ms
229 ms
104 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ric.ir, 89% (51 requests) were made to Ric-co.ir and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Ric-co.ir.
Page size can be reduced by 82.6 kB (3%)
2.8 MB
2.7 MB
In fact, the total size of Ric.ir main page is 2.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. 60% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 45.2 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 6.0 kB, which is 11% 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 45.2 kB or 83% of the original size.
Potential reduce by 10.4 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. Ric images are well optimized though.
Potential reduce by 21.4 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 21.4 kB or 19% of the original size.
Potential reduce by 5.6 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. Ric.ir needs all CSS files to be minified and compressed as it can save up to 5.6 kB or 11% of the original size.
Number of requests can be reduced by 23 (47%)
49
26
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ric. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
ric.ir
898 ms
ric-co.ir
1585 ms
js
62 ms
Diba_rtl.css
229 ms
js
104 ms
custom.css
398 ms
jquery.dibatabs.js
592 ms
jssor.js
911 ms
jssor.slider.js
911 ms
custom.js
735 ms
tools.js
736 ms
scripts.js
768 ms
Menu_Custom_1_rtl.css
791 ms
Menu_Custom_2_rtl.css
920 ms
tpro2.js
919 ms
js
103 ms
analytics.js
94 ms
font.css
957 ms
collect
11 ms
jquery-1.9.1.min.js
200 ms
jquery-migrate-1.2.1.js
186 ms
logo-FA.jpg
201 ms
image1.png
202 ms
ric_c2957f_1691576131.jpg
953 ms
ric_8dabb4_1689676330.jpg
750 ms
ric_d9fb90_1652693253.jpg
1306 ms
ric_d00899_1615796703.jpg
1452 ms
ric_825dba_1534743625.jpg
1557 ms
ric_31395d_1460542332.jpg
1679 ms
ric_e3a078_1460542223.jpg
2044 ms
image.php
1155 ms
image.php
1351 ms
image.php
1498 ms
image.php
1547 ms
image.php
1638 ms
image.php
1687 ms
image.php
1740 ms
image.php
1755 ms
Yekan.woff
1803 ms
ric_3a62b3_1459608702.png
1839 ms
menu-1x.png
1849 ms
a21.png
1904 ms
image22.png
1922 ms
ric_572727_1534747396.jpg
2342 ms
bg1.jpg
2211 ms
ric_bfabd2_1456917619.woff
1999 ms
IRANSans-UltraLight.woff
2258 ms
social_icons.png
2263 ms
a1.png
2149 ms
a2.png
2167 ms
a3.png
2335 ms
a4.png
2343 ms
a5.png
2354 ms
a6.png
2431 ms
Menu_Custom_2_rtl.css
2423 ms
ric_2d5255_1456918506.woff
2434 ms
fa-brands-400.woff
2669 ms
ric.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
Form elements do not have associated labels
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
ric.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
Issues were logged in the Issues panel in Chrome Devtools
ric.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ric.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 Ric.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.
ric.ir
Open Graph description is not detected on the main page of Ric. 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: