28.1 sec in total
522 ms
27.4 sec
223 ms
Visit irandh.com now to see the best up-to-date Irandh content for Iran and also check out these interesting facts you probably never knew about irandh.com
دستگاه های دفع حشرات صنعتی ایران دی اچ برای دفع حشرات از هتل، دفع حشرات از رستوران و مغازه ها و دفع حشرات بیمارستان و شرکت ها
Visit irandh.comWe analyzed Irandh.com page load time and found that the first response time was 522 ms and then it took 27.6 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
irandh.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value11.2 s
0/100
25%
Value19.6 s
0/100
10%
Value890 ms
32/100
30%
Value0.011
100/100
15%
Value10.2 s
25/100
10%
522 ms
5067 ms
165 ms
327 ms
490 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 95% of them (109 requests) were addressed to the original Irandh.com, 2% (2 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Trustseal.enamad.ir.
Page size can be reduced by 212.4 kB (16%)
1.3 MB
1.1 MB
In fact, the total size of Irandh.com main page is 1.3 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. 70% of websites need less resources to load. Javascripts take 523.2 kB which makes up the majority of the site volume.
Potential reduce by 116.9 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 116.9 kB or 83% of the original size.
Potential reduce by 49.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. Obviously, Irandh needs image optimization as it can save up to 49.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 43.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. Irandh.com needs all CSS files to be minified and compressed as it can save up to 43.5 kB or 14% of the original size.
Number of requests can be reduced by 78 (74%)
106
28
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Irandh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
irandh.com
522 ms
irandh.com
5067 ms
wp-emoji-release.min.js
165 ms
layerslider.css
327 ms
wc-blocks-vendors-style.css
490 ms
wc-blocks-style-rtl.css
682 ms
styles.css
510 ms
styles-rtl.css
516 ms
go_pricing_styles.css
520 ms
Defaults.css
523 ms
icomoon-material-24x24.css
652 ms
icomoon-icomoonfree-16x16.css
677 ms
icomoon-elegent-line-icons-32x32.css
687 ms
icomoon-numbers-32x32.css
690 ms
icomoon-pixeden-stroke-32x32.css
693 ms
js_composer_front_custom.css
983 ms
css
35 ms
main.min.css
1018 ms
icomoon-the7-font.min.css
847 ms
all.min.css
854 ms
back-compat.min.css
860 ms
custom-scrollbar.min.css
864 ms
wpbakery.min.css
1014 ms
post-type.min.css
1034 ms
css-vars.css
1037 ms
custom.css
1213 ms
wc-dt-custom.css
1149 ms
media.css
1186 ms
mega-menu.css
1182 ms
the7-elements-albums-portfolio.css
1194 ms
post-type-dynamic.css
1201 ms
style.css
1311 ms
style-rtl.min.css
1350 ms
headings-rtl.min.css
1349 ms
jquery.min.js
1534 ms
jquery-migrate.min.js
1371 ms
jquery.cookie.js
1382 ms
language-cookie.js
1472 ms
TweenMax.min.js
35 ms
css
31 ms
rtl.css
1514 ms
animate.min.css
1361 ms
background-style-rtl.min.css
1226 ms
rs6.css
1078 ms
greensock.js
1136 ms
layerslider.kreaturamedia.jquery.js
1347 ms
layerslider.transitions.js
1170 ms
rbtools.min.js
1193 ms
rs6.min.js
1480 ms
jquery.blockUI.min.js
1062 ms
add-to-cart.min.js
1123 ms
woocommerce-add-to-cart.js
1171 ms
above-the-fold.min.js
1213 ms
woocommerce.min.js
1218 ms
ultimate-params.min.js
1123 ms
headings.min.js
1166 ms
main.min.js
1357 ms
wp-polyfill.min.js
1267 ms
i18n.min.js
1120 ms
lodash.min.js
1152 ms
url.min.js
1185 ms
hooks.min.js
1240 ms
api-fetch.min.js
1240 ms
index.js
1118 ms
go_pricing_scripts.js
1142 ms
js.cookie.min.js
1169 ms
woocommerce.min.js
1174 ms
cart-fragments.min.js
1194 ms
jquery-mousewheel.min.js
1176 ms
custom-scrollbar.min.js
1114 ms
post-type.min.js
1113 ms
wp-embed.min.js
1162 ms
js_composer_front.min.js
1165 ms
vc-waypoints.min.js
1184 ms
jquery-appear.min.js
1105 ms
ultimate_bg.min.js
1079 ms
custom.min.js
1109 ms
logo.aspx
19719 ms
logo.aspx
772 ms
dh-57-57px.png
640 ms
favicon-32x32-1.png
652 ms
dummy.png
687 ms
%D9%88%D9%84%DB%8C%D8%B9%D8%B5%D8%B1-300x240.jpg
697 ms
%D8%A2%D9%86%DB%8C-%D8%AF%D8%B1%D9%85%D8%A7%D9%86-1-300x240.jpg
718 ms
%D9%86%D8%A7%D9%85%DB%8C-%D9%86%D9%88-300x240.jpg
739 ms
%D8%A8%D8%A7%D9%86%DA%A9-%D8%B3%D8%B1%D9%85%D8%A7%DB%8C%D9%87-300x240.jpg
808 ms
%D8%AA%DA%A9-300x240.jpg
818 ms
%D8%A8%D8%A7%D9%86%DA%A9-%DA%A9%D8%B4%D8%A7%D9%88%D8%B1%D8%B2%DB%8C-300x240.jpg
857 ms
%D8%B2%D8%B1-300x240.jpg
867 ms
%D8%A8%D8%A7%D9%86%DA%A9-%D8%B3%D9%BE%D9%87-300x240.jpg
889 ms
yas-300x240.jpg
901 ms
1-1-300x240.jpg
977 ms
2-300x240.jpg
911 ms
download-1-150x150.jpg
953 ms
download-5-150x150.jpg
961 ms
download-4-150x150.jpg
984 ms
font
37 ms
icomoon-the7-font.ttf
953 ms
IRANSansWeb(FaNum).woff
981 ms
IRANSansWeb(FaNum)_Bold.woff
1019 ms
iranyekanwebregularfanum.woff
992 ms
iranyekanwebboldfanum.woff
992 ms
download-6-150x150.jpg
1008 ms
wp-polyfill-fetch.min.js
968 ms
wp-polyfill-dom-rect.min.js
1008 ms
wp-polyfill-url.min.js
1009 ms
wp-polyfill-formdata.min.js
1027 ms
wp-polyfill-element-closest.min.js
1028 ms
download-150x150.jpg
1286 ms
download-3-150x150.jpg
1249 ms
download-2-150x150.jpg
1186 ms
WhatsApp-Image-2022-01-30-at-10.30.21-AM-150x150.jpeg
1176 ms
SSL-PNG-Wolkengrazer-01.png
1145 ms
%D9%84%D9%88%DA%AF%D9%88-%D8%A8%D8%A7%D9%86%DA%A9-%D9%87%D8%A73-01-300x300.png
1135 ms
irandh.com
1077 ms
irandh.com 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.
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.
irandh.com 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
irandh.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Irandh.com 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 Irandh.com 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.
irandh.com
Open Graph description is not detected on the main page of Irandh. 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: