5.1 sec in total
395 ms
4.4 sec
288 ms
Visit ihoosh.ir now to see the best up-to-date Ihoosh content for Iran and also check out these interesting facts you probably never knew about ihoosh.ir
هوش، تست هوش، معمای هوش، iq، ریاضی، معمای ریاضی، زندگینامه ریاضیدانان، پرورش خلاقیت کودک
Visit ihoosh.irWe analyzed Ihoosh.ir page load time and found that the first response time was 395 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ihoosh.ir performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value7.3 s
4/100
25%
Value6.0 s
46/100
10%
Value220 ms
87/100
30%
Value0.536
14/100
15%
Value6.9 s
54/100
10%
395 ms
2429 ms
275 ms
305 ms
302 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 97% of them (73 requests) were addressed to the original Ihoosh.ir, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ihoosh.ir.
Page size can be reduced by 750.8 kB (34%)
2.2 MB
1.4 MB
In fact, the total size of Ihoosh.ir main page is 2.2 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.4 MB which makes up the majority of the site volume.
Potential reduce by 61.6 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 10.8 kB, which is 15% 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 61.6 kB or 87% of the original size.
Potential reduce by 124.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. Ihoosh images are well optimized though.
Potential reduce by 306.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 306.0 kB or 75% of the original size.
Potential reduce by 258.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. Ihoosh.ir needs all CSS files to be minified and compressed as it can save up to 258.6 kB or 88% of the original size.
Number of requests can be reduced by 18 (25%)
71
53
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ihoosh. 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 7 to 1 for CSS and as a result speed up the page load time.
ihoosh.ir
395 ms
www.ihoosh.ir
2429 ms
bootstrap.css
275 ms
font-awesome.css
305 ms
animate.css
302 ms
PNassim.css
191 ms
ihoosh.css
376 ms
owl.carousel.css
194 ms
owl.transitions.css
305 ms
news02011.jpg
509 ms
news04201.jpg
481 ms
news13063.jpg
709 ms
news09582.jpg
585 ms
news57441.jpg
691 ms
news24211.jpg
691 ms
article3451.png
584 ms
article4717.jpg
602 ms
article4929.jpg
690 ms
article0354.jpg
706 ms
article34512.png
823 ms
article2310.jpg
796 ms
article3759.jpg
776 ms
article34301.jpg
776 ms
Pages4247.png
823 ms
jquery.min.js
725 ms
jquery.easing.1.3.js
790 ms
bootstrap.js
788 ms
wow.min.js
809 ms
jquery.ticker.js
846 ms
owl.carousel.js
828 ms
jquery.scrollUp.js
828 ms
jquery.nicescroll.js
883 ms
jquery.nicescroll.plus.js
884 ms
enquire.js
904 ms
ihoosh.js
905 ms
google-analytics.js
923 ms
news0201.jpg
997 ms
news4804.jpg
998 ms
news5011.jpg
911 ms
news1435.jpg
936 ms
news0310.jpg
833 ms
Pages4231.png
849 ms
article5924.jpg
849 ms
article3214.jpg
864 ms
PNassim.woff
794 ms
fontawesome-webfont.woff
807 ms
article4636.jpg
730 ms
article1643.png
661 ms
article15393.jpg
646 ms
article34515.png
837 ms
article4109.jpg
584 ms
article1720.jpg
620 ms
article3541.jpg
641 ms
article0812.png
751 ms
article0258.jpg
647 ms
article4608.jpg
608 ms
article3244.jpg
605 ms
article0406.jpg
616 ms
article5854.jpg
637 ms
article4413.jpg
656 ms
article56411.jpg
661 ms
article34517.png
664 ms
article34511.png
662 ms
article34519.png
644 ms
article34518.png
647 ms
article34513.png
650 ms
article345112.png
654 ms
article34516.png
663 ms
article345111.png
658 ms
article345110.png
658 ms
logo_salamat118_45.png
673 ms
analytics.js
75 ms
logo.png
621 ms
top.png
602 ms
collect
26 ms
ihoosh.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Buttons do not have an accessible name
Links do not have a discernible name
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
ihoosh.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
ihoosh.ir 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ihoosh.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 Ihoosh.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.
ihoosh.ir
Open Graph description is not detected on the main page of Ihoosh. 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: