25.6 sec in total
2.9 sec
21.9 sec
721 ms
Click here to check amazing Mtmobile content for Iran. Otherwise, check out these important facts you probably never knew about mtmobile.ir
مرجع تخصصی موبایل برای ایرانیان ... هر آنچه از یک سایت موبایل انتظار دارید
Visit mtmobile.irWe analyzed Mtmobile.ir page load time and found that the first response time was 2.9 sec and then it took 22.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.
mtmobile.ir performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.0 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
2913 ms
63 ms
79 ms
82 ms
81 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 74% of them (49 requests) were addressed to the original Mtmobile.ir, 8% (5 requests) were made to Feed.zarshop.biz and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (15 sec) relates to the external source Neginkala.co.
Page size can be reduced by 316.9 kB (22%)
1.4 MB
1.1 MB
In fact, the total size of Mtmobile.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. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 55.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 55.9 kB or 82% of the original size.
Potential reduce by 90.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. Mtmobile images are well optimized though.
Potential reduce by 145.9 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 145.9 kB or 61% of the original size.
Potential reduce by 24.8 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. Mtmobile.ir needs all CSS files to be minified and compressed as it can save up to 24.8 kB or 83% of the original size.
Number of requests can be reduced by 9 (16%)
55
46
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mtmobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
mtmobile.ir
2913 ms
style.css
63 ms
tab-style.css
79 ms
jquery.js
82 ms
organictabs.js
81 ms
styles.css
77 ms
styles-rtl.css
80 ms
jquery.js
139 ms
jquery-migrate.min.js
128 ms
feedwithcode.aspx
454 ms
feedwithcode.aspx
454 ms
feedwithcode.aspx
454 ms
FeedNegin.aspx
453 ms
feedwithcode.aspx
464 ms
jquery.form.min.js
123 ms
scripts.js
122 ms
ga.js
21 ms
__utm.gif
12 ms
__utm.gif
4 ms
120_240.gif
183 ms
background-body.png
132 ms
background-all.png
39 ms
li.png
24 ms
search-bg.png
24 ms
search.png
23 ms
btn-search.png
81 ms
header.png
181 ms
ads-wide.png
59 ms
Calendar-93-Taghvim-1393-year-300x176.jpg
58 ms
icon-read%20more.png
78 ms
1392091805.jpg
78 ms
0098charge.ir_-6-175x300.jpg
78 ms
sms-fetr2.jpg
124 ms
fetr-92-MTMOBILE.IR_.jpg
113 ms
35338333-14_610x435.jpg
253 ms
MTDesign.ir.png
112 ms
BYekan.woff
55 ms
feedwithcode.aspx
3706 ms
feedwithcode.aspx
560 ms
FeedNegin.aspx
437 ms
feedwithcode.aspx
2593 ms
feedwithcode.aspx
606 ms
1394060114411Baner1.gif
1214 ms
13930829093754Hmonopad.gif
1433 ms
markD.gif
15011 ms
background-nav.png
43 ms
head-right-ads.png
22 ms
head-right-category.png
130 ms
list.png
22 ms
head-status.png
132 ms
head-left-ads.png
130 ms
head-left-lastpost.png
116 ms
list-last-post.png
116 ms
head-left-archive.png
118 ms
list-hover.png
116 ms
text-ads-head.png
118 ms
header-post.png
118 ms
catogery-content.png
118 ms
icon-pencil.png
119 ms
calender.png
121 ms
icon-comment.png
120 ms
icon-veiwe.png
120 ms
footer.png
131 ms
BHoma.woff
130 ms
syekan.woff
136 ms
bsinabd.woff
136 ms
mtmobile.ir accessibility score
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
Document doesn't have a <title> element
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
mtmobile.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
mtmobile.ir SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mtmobile.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 Mtmobile.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.
mtmobile.ir
Open Graph description is not detected on the main page of Mtmobile. 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: