17.1 sec in total
1.1 sec
15.1 sec
966 ms
Visit avayefarhangi.ir now to see the best up-to-date Avayefarhangi content for Iran and also check out these interesting facts you probably never knew about avayefarhangi.ir
Visit avayefarhangi.irWe analyzed Avayefarhangi.ir page load time and found that the first response time was 1.1 sec and then it took 16.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
avayefarhangi.ir performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value8.7 s
1/100
25%
Value15.5 s
0/100
10%
Value260 ms
84/100
30%
Value0.017
100/100
15%
Value10.9 s
21/100
10%
1079 ms
180 ms
278 ms
293 ms
195 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 66% of them (68 requests) were addressed to the original Avayefarhangi.ir, 14% (14 requests) were made to Aparat.com and 8% (8 requests) were made to Weather.toolsir.com. The less responsive or slowest element that took the longest time to load (13.6 sec) relates to the external source S5.picofile.com.
Page size can be reduced by 746.9 kB (28%)
2.7 MB
1.9 MB
In fact, the total size of Avayefarhangi.ir main page is 2.7 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 1.7 MB which makes up the majority of the site volume.
Potential reduce by 78.1 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 78.1 kB or 84% of the original size.
Potential reduce by 62.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. Avayefarhangi images are well optimized though.
Potential reduce by 448.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 448.4 kB or 69% of the original size.
Potential reduce by 158.1 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. Avayefarhangi.ir needs all CSS files to be minified and compressed as it can save up to 158.1 kB or 81% of the original size.
Number of requests can be reduced by 34 (35%)
97
63
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Avayefarhangi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
avayefarhangi.ir
1079 ms
style.css
180 ms
bootstrap.css
278 ms
jquery.js
293 ms
bootstrap.min.js
195 ms
inewsticker.js
192 ms
jquery.immersive-slider.js
194 ms
styles.css
269 ms
styles-rtl.css
293 ms
polls-css.css
296 ms
polls-css-rtl.css
295 ms
jquery.js
455 ms
jquery-migrate.min.js
367 ms
jquery.form.min.js
370 ms
scripts.js
377 ms
polls-js.js
379 ms
badge.php
430 ms
c.aspx
138 ms
myfonts.css
205 ms
wp-emoji-release.min.js
121 ms
71 ms
69 ms
71 ms
avaye_farhangi_rayane.gif
13609 ms
66.gif
3694 ms
bg.png
116 ms
logo.png
243 ms
IMG_8660.jpg
371 ms
%D8%A8%DB%8C%D9%85%D9%87-%D8%B7%D9%84%D8%A7%DB%8C%DB%8C.jpg
241 ms
%D9%85%D8%AF%DB%8C%D8%B1%D8%A7%D9%86-%D8%A8%DB%8C-%D8%B6%D8%A7%D8%A8%D8%B7%D9%87.jpg
356 ms
%DA%A9%D9%84%D8%A7%D8%B3-%D8%A7%D9%88%D9%84%DB%8C-%D9%87%D8%A7.jpg
603 ms
%D8%B9%D8%B3%DA%A9%D8%B1%DB%8C-300x259.jpg
241 ms
%D8%A7%D9%88%D8%B3%D8%B7-%D9%87%D8%A7%D8%B4%D9%85%DB%8C.jpg
354 ms
%D9%85%D8%B9%DB%8C%D8%B4%D8%AA-%D9%81%D8%B1%D9%87%D9%86%DA%AF%DB%8C%D8%A7%D9%86-300x210.jpg
355 ms
%D8%A7%D8%A8%D8%AA%D8%AF%D8%A7%DB%8C%DB%8C-300x200.jpg
355 ms
%D8%A8%DB%8C%D9%85%D9%87-%D8%B7%D9%84%D8%A7%DB%8C%DB%8C-300x159.jpg
367 ms
%D8%AA%D8%AC%D9%84%DB%8C%D9%84-150x150.jpg
370 ms
789456-150x150.jpg
374 ms
%D8%B9%D8%B3%DA%A9%D8%B1%DB%8C-150x150.jpg
376 ms
IMG_20160229_140141-150x150.jpg
459 ms
%D8%AA%D8%A8%D8%B9%DB%8C%D8%B6-150x150.jpg
456 ms
%D8%A8%D9%88%D8%AF%D8%AC%D9%87-%D8%A2%D9%85%D9%88%D8%B2%D8%B4-%D9%88-%D9%BE%D8%B1%D9%88%D8%B1%D8%B4-150x150.jpg
459 ms
%D9%86%D8%B5%D8%B1%D8%A7%D9%84%D9%87-%D8%AE%D9%84%DB%8C%D9%84%DB%8C-150x150.jpg
465 ms
4564-150x150.jpg
467 ms
%D8%A7%D8%B3%D8%AA%D8%AE%D8%AF%D8%A7%D9%85-150x150.jpg
549 ms
%DA%A9%D9%88%DA%86%DA%A9%DB%8C-%D9%86%DA%98%D8%A7%D8%AF-150x150.jpg
549 ms
%D9%81%D8%A7%D9%86%DB%8C-150x150.jpg
549 ms
%D8%A8%DB%8C%D8%A7%D9%86%DB%8C%D9%87-150x150.jpg
557 ms
%D8%B4%D9%81%DB%8C%D8%B9%DB%8C-150x150.jpg
561 ms
%D8%A8%D8%AE%D8%B4%D9%86%D8%A7%D9%85%D9%87-150x150.jpg
639 ms
%D9%81%D8%A7%D9%86%DB%8C1-150x150.jpg
638 ms
456123-150x150.jpg
639 ms
IMG_8660-150x150.jpg
656 ms
IMG_8565-150x150.jpg
657 ms
9-150x150.jpg
690 ms
loading.gif
745 ms
%D8%A8%D9%86%D8%B1-%D8%A7%D8%B3%DA%A9%D8%A7%D8%AF.gif
1386 ms
%D8%B9%D8%B1%DB%8C%D8%B6%D9%87.gif
927 ms
%D8%A2%D9%88%D8%A7%DB%8C-%D9%81%D8%B1%D9%87%D9%86%DA%AF%DB%8C.gif
838 ms
%D9%86%D8%AF%D8%A7%DB%8C_%D9%81%D8%B1%D9%87%D9%86%DA%AF%DB%8C.png
4556 ms
%D8%B9%D8%B1%DB%8C%D8%B6%D9%87.gif
1022 ms
karami.gif
729 ms
frame
461 ms
nassim-bold.ttf
1012 ms
%D8%AA%D8%A8%D9%84%DB%8C%D8%BA.gif
886 ms
%D8%AE%D8%A8%D8%B1%D9%86%DA%AF%D8%A7%D8%B1%D8%A2%D9%88%D8%A7%DB%8C-%D9%81%D8%B1%D9%87%D9%86%DA%AF%DB%8C.gif
801 ms
glyphicons-halflings-regular.woff
787 ms
weather.php
322 ms
stat1.gif
137 ms
xstat.aspx
151 ms
1%D8%A2%D9%88%D8%A7%DB%8C-%D9%81%D8%B1%D9%87%D9%86%DA%AF%DB%8C.gif
773 ms
%D8%A2%D9%88%D8%A7%DB%8C-%D9%81%D8%B1%D9%87%D9%86%DA%AF%DB%8C11.gif
1163 ms
%D8%B9%D8%B1%DB%8C%D8%B6%D9%87-1.gif
1162 ms
%D9%81%D8%B1%D9%88%D8%B4%DA%AF%D8%A7%D9%87-%D8%A7%D8%B3%DA%A9%D8%A7%D8%AF.gif
1272 ms
1452.gif
981 ms
blue_header1.jpg
1150 ms
upbg.png
1146 ms
navbg.png
1145 ms
ttl-bg.png
1173 ms
undefined
1092 ms
jquery.min.js
673 ms
g.main.v8.js
400 ms
video-js-0.5.min.css
670 ms
videojs.watermark.css
404 ms
videojs-aparat-0.1.min.css
407 ms
video-custom.min.js
811 ms
videojs.watermark-0.1.min.js
668 ms
videojs-aparat-0.5.min.js
669 ms
videojs.persistvolume.js
669 ms
fa.js
795 ms
aparatplayer.ext.js
804 ms
style.css
88 ms
down.gif
873 ms
up.gif
180 ms
spacer.gif
952 ms
badge.png
1592 ms
31n.png
898 ms
video.min.css
207 ms
replay.png
1092 ms
ga.js
26 ms
3845200-7708-b__205789444.jpg
1009 ms
vjs-icons.woff
208 ms
__utm.gif
23 ms
avayefarhangi.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.
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
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>).
avayefarhangi.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
avayefarhangi.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 doesn't use 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 Avayefarhangi.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 Avayefarhangi.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.
avayefarhangi.ir
Open Graph description is not detected on the main page of Avayefarhangi. 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: