12.1 sec in total
1.2 sec
10.6 sec
354 ms
Visit mobile.aqr.ir now to see the best up-to-date Mobile Aqr content for Iran and also check out these interesting facts you probably never knew about mobile.aqr.ir
درگاه اصلی آستان قدس رضوی پورتال جامع، درگاه اصلی آستان قدس رضوی شامل بروزترین اخبار حرم مطهر امام رضا(ع)، خدماتی برای زائر و مجاور رضوی و زندگی رضوی
Visit mobile.aqr.irWe analyzed Mobile.aqr.ir page load time and found that the first response time was 1.2 sec and then it took 10.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.
mobile.aqr.ir performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value10.8 s
0/100
25%
Value14.2 s
1/100
10%
Value640 ms
46/100
30%
Value0.005
100/100
15%
Value11.1 s
20/100
10%
1195 ms
2814 ms
418 ms
823 ms
424 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 87% of them (103 requests) were addressed to the original Mobile.aqr.ir, 13% (16 requests) were made to Aqr.ir. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Mobile.aqr.ir.
Page size can be reduced by 267.1 kB (41%)
658.8 kB
391.6 kB
In fact, the total size of Mobile.aqr.ir main page is 658.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 369.6 kB which makes up the majority of the site volume.
Potential reduce by 57.4 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 57.4 kB or 70% of the original size.
Potential reduce by 58.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. Obviously, Mobile Aqr needs image optimization as it can save up to 58.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 114.8 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 114.8 kB or 71% of the original size.
Potential reduce by 36.9 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. Mobile.aqr.ir needs all CSS files to be minified and compressed as it can save up to 36.9 kB or 81% of the original size.
Number of requests can be reduced by 32 (31%)
103
71
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Aqr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
mobile.aqr.ir
1195 ms
Default.aspx
2814 ms
Portal.css
418 ms
jquery-latest.min.js
823 ms
Style.aspx
424 ms
LinkMenu.js
422 ms
WebResource.axd
669 ms
template-min.css
467 ms
first-page-template.css
428 ms
js.js
451 ms
jquery.cookie.js
668 ms
ShowFile.aspx
715 ms
EditForm.js
477 ms
script.js
471 ms
style.css
611 ms
awstats_misc_tracker.js
655 ms
m6.png
268 ms
m5.png
408 ms
m4.png
268 ms
m3.png
283 ms
m2.png
408 ms
m1.png
407 ms
spacer.gif
446 ms
ShowObjectPicture.aspx
510 ms
ShowObjectPicture.aspx
1033 ms
ShowObjectPicture.aspx
661 ms
ShowObjectPicture.aspx
1555 ms
ShowObjectPicture.aspx
1384 ms
ShowObjectPicture.aspx
1312 ms
wall.gif
716 ms
header2-menu-item1-1.gif
862 ms
header2-menu-item1-2.gif
946 ms
header2-menu-item2-1.gif
1068 ms
header2-menu-item2-2.gif
1167 ms
header2-menu-item3-1.gif
1233 ms
header2-menu-item3-2.gif
1296 ms
header2-menu-item4-1.gif
1733 ms
header2-menu-item4-2.gif
1439 ms
header2-menu-item5-1.gif
1518 ms
header2-menu-item5-2.gif
1520 ms
header2-menu-item6-1.gif
1584 ms
header2-menu-item6-2.gif
1643 ms
ShowObjectPicture.aspx
1744 ms
ShowObjectPicture.aspx
2471 ms
ShowObjectPicture.aspx
1793 ms
ShowObjectPicture.aspx
2480 ms
ShowObjectPicture.aspx
1872 ms
ShowObjectPicture.aspx
2404 ms
ShowObjectPicture.aspx
1963 ms
ShowObjectPicture.aspx
2007 ms
BYekan.woff
624 ms
acordion-header1.png
567 ms
BYekan.woff
1884 ms
body3-part2-list.gif
442 ms
body3-part3-list.gif
446 ms
slider-b2.png
449 ms
body2-item1-text1.gif
449 ms
body2-item2-text1.gif
646 ms
body2-item3-text1.gif
646 ms
nassim-regular.woff
2384 ms
ShowObjectPicture.aspx
2089 ms
ShowObjectPicture.aspx
2617 ms
ShowObjectPicture.aspx
2304 ms
ShowObjectPicture.aspx
2478 ms
rss.gif
2281 ms
ShowObjectPicture.aspx
2324 ms
ShowObjectPicture.aspx
2607 ms
ShowObjectPicture.aspx
2783 ms
ShowObjectPicture.aspx
2689 ms
body3-part2-list.gif
1269 ms
body3-part3-list.gif
1120 ms
BYekan.woff
1692 ms
acordion-header1.png
1119 ms
slider-b2.png
1262 ms
body2-item1-text1.gif
1264 ms
ShowObjectPicture.aspx
2247 ms
ShowObjectPicture.aspx
2247 ms
body2-item2-text1.gif
1121 ms
body2-item3-text1.gif
1123 ms
ShowObjectPicture.aspx
2676 ms
ShowObjectPicture.aspx
2172 ms
ShowObjectPicture.aspx
2210 ms
ShowObjectPicture.aspx
2187 ms
ShowObjectPicture.aspx
2192 ms
ShowObjectPicture.aspx
2742 ms
ShowObjectPicture.aspx
2208 ms
ShowObjectPicture.aspx
2186 ms
ShowObjectPicture.aspx
2672 ms
ShowObjectPicture.aspx
2130 ms
ShowObjectPicture.aspx
2426 ms
ShowObjectPicture.aspx
2242 ms
Regulation2.gif
2240 ms
header.jpg
2630 ms
logo.jpg
2269 ms
header1.png
3344 ms
search.png
2359 ms
ShowPicture.aspx
4226 ms
body1-title.gif
2251 ms
body1-space.gif
2253 ms
body2-list1.gif
2260 ms
mobile2.png
2107 ms
body2-list2.gif
2057 ms
body2-list3.gif
2060 ms
body2-bottom.png
3120 ms
body3-title.gif
2081 ms
RSS.gif
2057 ms
body3-space.gif
2061 ms
body3-part2.png
2777 ms
space1.gif
2055 ms
footer.gif
2119 ms
logo.png
2380 ms
repeat.png
2219 ms
img.png
2194 ms
awstats_misc_tracker.js
2281 ms
search.png
2230 ms
slider-mobile.png
2469 ms
slider-text.png
2343 ms
slider-b1.png
2354 ms
slider-title.png
2286 ms
mobile.aqr.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-hidden="true"] elements contain focusable descendents
[aria-*] attributes do not have valid values
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
mobile.aqr.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
Browser errors were logged to the console
Page has valid source maps
mobile.aqr.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 Mobile.aqr.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 Mobile.aqr.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.
mobile.aqr.ir
Open Graph description is not detected on the main page of Mobile Aqr. 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: