11.1 sec in total
1.1 sec
7.2 sec
2.8 sec
Visit hamandishi.ir now to see the best up-to-date Hamandishi content for Iran and also check out these interesting facts you probably never knew about hamandishi.ir
هم انديشی میكوشد «محتوای ارزشی و انقلابی» را با سه شاخص مهم «سرعت»، «اختصار» و «جذابیت» منتشر نمايد.
Visit hamandishi.irWe analyzed Hamandishi.ir page load time and found that the first response time was 1.1 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hamandishi.ir performance score
name
value
score
weighting
Value3.2 s
45/100
10%
Value4.9 s
28/100
25%
Value7.2 s
30/100
10%
Value70 ms
99/100
30%
Value0.284
42/100
15%
Value3.5 s
92/100
10%
1106 ms
871 ms
33 ms
494 ms
507 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 98% of them (82 requests) were addressed to the original Hamandishi.ir, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Ssz89969.s9.3sz.ir. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Hamandishi.ir.
Page size can be reduced by 721.5 kB (53%)
1.4 MB
631.9 kB
In fact, the total size of Hamandishi.ir main page is 1.4 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. 55% of websites need less resources to load. Javascripts take 500.0 kB which makes up the majority of the site volume.
Potential reduce by 315.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 315.7 kB or 86% of the original size.
Potential reduce by 4.8 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. Hamandishi images are well optimized though.
Potential reduce by 922 B
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 400.2 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. Hamandishi.ir needs all CSS files to be minified and compressed as it can save up to 400.2 kB or 99% of the original size.
Number of requests can be reduced by 63 (83%)
76
13
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hamandishi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
hamandishi.ir
1106 ms
2d8fe8676506add81fd79a556ca7c1ca.css
871 ms
css
33 ms
post-269.css
494 ms
post-13.css
507 ms
post-967.css
509 ms
post-2567.css
513 ms
add-to-cart.min.js
518 ms
js.cookie.min.js
654 ms
woocommerce.min.js
672 ms
jarallax.js
674 ms
helper.js
680 ms
elementor-frontend.js
688 ms
device.min.js
816 ms
select2.full.min.js
1032 ms
index.js
836 ms
index.js
844 ms
sourcebuster.min.js
853 ms
order-attribution.min.js
864 ms
tracker.js
865 ms
cute-alert.js
866 ms
frontend-script.js
865 ms
widget-scripts.js
983 ms
anime.js
984 ms
parallax-frontend-scripts.js
1049 ms
jquery.magnific-popup.min.js
1050 ms
jed.js
1050 ms
login-form-popup.js
1050 ms
webpack-pro.runtime.min.js
1123 ms
webpack.runtime.min.js
1136 ms
frontend-modules.min.js
1255 ms
wp-polyfill-inert.min.js
1256 ms
regenerator-runtime.min.js
1255 ms
wp-polyfill.min.js
1256 ms
hooks.min.js
1270 ms
i18n.min.js
1295 ms
frontend.min.js
1337 ms
waypoints.min.js
1337 ms
core.min.js
1033 ms
frontend.min.js
1035 ms
elements-handlers.min.js
1105 ms
animate-circle.min.js
1117 ms
elementor.js
1161 ms
elementor.js
1025 ms
swiper.min.js
1192 ms
elementskit-sticky-content.js
1038 ms
elementskit-reset-button.js
1107 ms
parallax-admin-scripts.js
1103 ms
underscore.min.js
1037 ms
wp-util.min.js
1006 ms
frontend.min.js
1033 ms
imagesloaded.min.js
1103 ms
combine.min.js
1091 ms
mediaelement-and-player.min.js
988 ms
mediaelement-migrate.min.js
992 ms
wp-mediaelement.min.js
999 ms
script.min.js
1253 ms
smush-lazy-load.min.js
1058 ms
libphonenumber-max.js
1034 ms
scrollTo.js
1067 ms
main.min.js
1066 ms
login.min.js
1146 ms
jquery.smartmenus.min.js
1145 ms
rttpg.js
1073 ms
autocomplete.min.js
1072 ms
cart-fragments.min.js
1042 ms
IRANSansWebFaNum.ttf
855 ms
fa-solid-900.woff
1151 ms
fa-solid-900.ttf
1712 ms
fa-regular-400.woff
1059 ms
fa-regular-400.ttf
1136 ms
fa-v4compatibility.ttf
1135 ms
fa-brands-400.ttf
1579 ms
jeg-empty.png
1229 ms
captcha.php
1228 ms
captcha.php
1215 ms
Untitled-1-1.png
1199 ms
preloader.gif
1222 ms
logopng.png
734 ms
jahesh.png
742 ms
ScreenHunter-130-350x250.jpg
171 ms
ScreenHunter-28-350x250.jpg
233 ms
1-9394-120x86.jpg
264 ms
1-9329-120x86.jpg
363 ms
hamandishi.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
hamandishi.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
hamandishi.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 Hamandishi.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 Hamandishi.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.
hamandishi.ir
Open Graph description is not detected on the main page of Hamandishi. 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: