11.7 sec in total
1.6 sec
9.9 sec
304 ms
Welcome to rad24.ir homepage info - get ready to check Rad 24 best content for Iran right away, or after learning these important things about rad24.ir
Visit rad24.irWe analyzed Rad24.ir page load time and found that the first response time was 1.6 sec and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rad24.ir performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value11.9 s
0/100
25%
Value14.4 s
1/100
10%
Value2,540 ms
4/100
30%
Value0.377
28/100
15%
Value15.0 s
8/100
10%
1556 ms
284 ms
193 ms
286 ms
25 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 95% of them (168 requests) were addressed to the original Rad24.ir, 3% (6 requests) were made to Maps.googleapis.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Rad24.ir.
Page size can be reduced by 1.8 MB (47%)
3.8 MB
2.0 MB
In fact, the total size of Rad24.ir main page is 3.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.5 MB which makes up the majority of the site volume.
Potential reduce by 112.8 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 112.8 kB or 83% of the original size.
Potential reduce by 42.1 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. Rad 24 images are well optimized though.
Potential reduce by 933.1 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 933.1 kB or 72% of the original size.
Potential reduce by 720.5 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. Rad24.ir needs all CSS files to be minified and compressed as it can save up to 720.5 kB or 82% of the original size.
Number of requests can be reduced by 140 (81%)
172
32
The browser has sent 172 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rad 24. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 75 to 1 for JavaScripts and from 53 to 1 for CSS and as a result speed up the page load time.
rad24.ir
1556 ms
wp-emoji-release.min.js
284 ms
theme-my-login.css
193 ms
parallax.css
286 ms
css
25 ms
font-awesome.css
289 ms
style.css
383 ms
bootstrap.css
752 ms
bootstrap-theme.css
570 ms
loading-page.css
474 ms
bbpress.css
581 ms
bbpress-rtl.css
541 ms
styles.css
575 ms
styles-rtl.css
666 ms
style2-os.css
765 ms
lightbox.css
767 ms
font-awesome.css
867 ms
frontend_style.css
854 ms
jquery.fancybox-1.3.4.css
934 ms
buttons-rtl.min.css
942 ms
dashicons.min.css
1145 ms
mediaelementplayer.min.css
1047 ms
wp-mediaelement.css
1045 ms
media-views-rtl.min.css
1147 ms
imgareaselect.css
1121 ms
bbpress-rtl.css
1228 ms
bwg_frontend.css
1237 ms
sumoselect.css
1238 ms
font-awesome.css
1401 ms
jquery.mCustomScrollbar.css
1340 ms
owl.carousel.min.css
1338 ms
owl.theme.min.css
1424 ms
style.min.css
1428 ms
style.css
1430 ms
widgetize_menu_frontend_style.css
1535 ms
advwidgets_styles.css
1538 ms
js
28 ms
woocommerce-layout.css
1409 ms
woocommerce.css
1433 ms
jquery.autocomplete.css
1337 ms
polls-css.css
1335 ms
polls-css-rtl.css
1384 ms
main.min.css
1347 ms
admin-ajax.php
2025 ms
bootstrap.min.css
1655 ms
icomoon.css
1247 ms
font-awesome.min.css
1421 ms
frontend.css
1428 ms
wpgmza_style.css
1258 ms
dcverticalmegamenu.css
1270 ms
shailan-dropdown.min.css
1351 ms
web20.css
1422 ms
rtl-shortcodes.css
1445 ms
reset.css
1359 ms
jquery.js
1736 ms
jquery-migrate.min.js
1444 ms
hoverIntent.js
1445 ms
include.js
1341 ms
parallax.js
1345 ms
modernizr.js
1444 ms
carousel.js
1527 ms
tipsy.js
1443 ms
fields.js
1432 ms
jquery.scroll.pack.js
1452 ms
supersubs.js
1513 ms
superfish.js
1447 ms
buttons.js
1449 ms
ddslick.js
1449 ms
bootstrap.js
1620 ms
loading-bar.js
1455 ms
loading-page.js
1509 ms
jquery.mousewheel-3.0.4.pack.js
1435 ms
jquery.fancybox-1.3.4.pack.js
1439 ms
frontend_script.js
1444 ms
utils.min.js
1458 ms
plupload.full.min.js
1795 ms
jdate.js
1443 ms
bwg_frontend.js
1440 ms
jquery.sumoselect.min.js
1503 ms
jquery.mobile.js
1419 ms
jquery.mCustomScrollbar.concat.min.js
1435 ms
jquery.fullscreen-0.4.1.js
1352 ms
bwg_gallery_box.js
1354 ms
widgetize_menu_frontend_script.js
1430 ms
jquery.autocomplete.js
1329 ms
coolclock.js
1362 ms
tabs.js
1340 ms
main.js
1342 ms
gmap.js
1490 ms
editor.js
1236 ms
jquery.form.min.js
1240 ms
scripts.js
1351 ms
jquery.colorbox.js
1435 ms
gallery-all.js
1234 ms
jquery.hugeitmicro.min.js
1334 ms
underscore.min.js
1226 ms
shortcode.min.js
1294 ms
backbone.min.js
1359 ms
wp-util.min.js
1276 ms
wp-backbone.min.js
1320 ms
media-models.min.js
1264 ms
wp-plupload.min.js
1301 ms
core.min.js
1299 ms
widget.min.js
1240 ms
mouse.min.js
1316 ms
sortable.min.js
1363 ms
mediaelement-and-player.min.js
1515 ms
wp-mediaelement.js
1297 ms
media-views.min.js
1536 ms
media-editor.min.js
1255 ms
media-audiovideo.min.js
1313 ms
owl.carousel.min.js
1395 ms
add-to-cart.min.js
1329 ms
jquery.blockUI.min.js
1268 ms
woocommerce.min.js
1361 ms
jquery.cookie.min.js
1337 ms
cart-fragments.min.js
1333 ms
polls-js.js
1335 ms
bootstrap_frontend.min.js
1402 ms
css
14 ms
frontend.js
1329 ms
jquery.hoverIntent.minified.js
1332 ms
jquery.dcverticalmegamenu.1.3.js
1329 ms
common.js
11 ms
util.js
24 ms
geocoder.js
10 ms
fontawesome-webfont.woff
1390 ms
fontawesome-webfont.woff
1425 ms
fontawesome-webfont.woff
1440 ms
LOGONEW.png
1521 ms
idea1.jpg
1523 ms
font.jpg
1329 ms
tea2.jpg
1723 ms
responsive1.jpg
1463 ms
color3.png
1618 ms
left-ar.png
1420 ms
right-ar.png
1418 ms
site_design-744x233.jpg
1702 ms
what-is-seo.jpg
1617 ms
index.jpg
1444 ms
what-is-user-experience1.jpg
1720 ms
What-is-Responsive-Web-Design.jpg
1745 ms
rad24.ir
2028 ms
Reason-of-Diffrent-Web-Design-Cost.jpg
1569 ms
shadow.png
1565 ms
pattern_8.png
1617 ms
list-style.png
1719 ms
trans.png
1656 ms
menu-item.png
1623 ms
menu-item-after.png
1697 ms
widget-shadow.png
1700 ms
open.png
1722 ms
loading2.gif
2185 ms
btop.png
1658 ms
pattern_8.png
1709 ms
LOGONEW.png
1982 ms
menu-item.png
1807 ms
idea1.jpg
2096 ms
font.jpg
1979 ms
tea2.jpg
2108 ms
responsive1.jpg
1911 ms
color3.png
2271 ms
left-ar.png
1850 ms
right-ar.png
1795 ms
shadow.png
1776 ms
site_design-744x233.jpg
2005 ms
open.png
1809 ms
what-is-seo.jpg
1805 ms
index.jpg
1717 ms
what-is-user-experience1.jpg
1917 ms
What-is-Responsive-Web-Design.jpg
1996 ms
Reason-of-Diffrent-Web-Design-Cost.jpg
1792 ms
loading2.gif
2280 ms
stats.js
5 ms
AuthenticationService.Authenticate
266 ms
woocommerce-smallscreen.css
98 ms
rad24.ir 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
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
Image elements do not have [alt] attributes
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.
rad24.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
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 Rad24.ir 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 Rad24.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.
rad24.ir
Open Graph description is not detected on the main page of Rad 24. 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: