1.6 sec in total
198 ms
1.1 sec
265 ms
Visit mobile.ir now to see the best up-to-date Mobile content for Iran and also check out these interesting facts you probably never knew about mobile.ir
مرجع موبایل ایران مرکز اطلاعات گوشی موبایل (نوکیا، سامسونگ، سونی اریکسون، ال جی, آیفون، موتورولا، ...)، خرید و فروش گوشی موبایل، سیم کارت و خط رند، فروشگاه های موبایل، خدمات و گارانتی های موبایل، آگهی...
Visit mobile.irWe analyzed Mobile.ir page load time and found that the first response time was 198 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
mobile.ir performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value6.7 s
7/100
25%
Value5.3 s
58/100
10%
Value490 ms
59/100
30%
Value0.216
58/100
15%
Value6.1 s
63/100
10%
198 ms
140 ms
238 ms
157 ms
301 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 13% of them (10 requests) were addressed to the original Mobile.ir, 76% (60 requests) were made to S.mobile.ir and 8% (6 requests) were made to Static.mobile.ir. The less responsive or slowest element that took the longest time to load (301 ms) relates to the external source S.mobile.ir.
Page size can be reduced by 680.6 kB (55%)
1.2 MB
568.0 kB
In fact, the total size of Mobile.ir main page is 1.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. 40% of websites need less resources to load. Images take 431.0 kB which makes up the majority of the site volume.
Potential reduce by 143.3 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 40.5 kB, which is 25% 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 143.3 kB or 89% of the original size.
Potential reduce by 40.5 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. Mobile images are well optimized though.
Potential reduce by 231.7 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 231.7 kB or 66% of the original size.
Potential reduce by 265.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. Mobile.ir needs all CSS files to be minified and compressed as it can save up to 265.1 kB or 86% of the original size.
Number of requests can be reduced by 12 (16%)
75
63
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
mobile.ir
198 ms
www.mobile.ir
140 ms
cachefile_style_common_130888541769921868.css
238 ms
cachefile_style_player_130513018740000000.css
157 ms
cachefile_script_common_130888541769921868.js
301 ms
cachefile_script_player_130513018740000000.js
214 ms
google-plus.png
32 ms
digikala_37.gif
222 ms
yahoo.png
84 ms
1.gif
84 ms
3.gif
83 ms
2.gif
85 ms
4.gif
84 ms
amitis_03.gif
218 ms
hamraheaval_12.gif
274 ms
header.logo.gif
78 ms
allsprites.png
152 ms
icons.sprite.png
79 ms
cachefile_917_0.jpg
78 ms
cachefile_235_0.jpg
83 ms
cachefile_2436_0.jpg
86 ms
cachefile_154_0.jpg
84 ms
FG-125x125.gif
150 ms
cachefile_37918_1.jpg
86 ms
cachefile_37908_1.jpg
148 ms
cachefile_37909_1.jpg
148 ms
cachefile_37912_1.jpg
149 ms
cachefile_1346_1.jpg
150 ms
cachefile_1344_1.jpg
152 ms
cachefile_1343_1.jpg
151 ms
cachefile_1335_0.jpg
151 ms
cachefile_1334_0.jpg
152 ms
cachefile_1333_0.jpg
152 ms
cachefile_1332_0.jpg
153 ms
cachefile_1330_0.jpg
154 ms
cachefile_1329_0.jpg
152 ms
cachefile_10_5.jpg
152 ms
cachefile_3_5.jpg
159 ms
cachefile_6_5.jpg
158 ms
cachefile_12_5.jpg
160 ms
cachefile_5_5.jpg
163 ms
cachefile_13_5.jpg
162 ms
cachefile_36791_0.jpg
163 ms
cachefile_34075_0.jpg
181 ms
cachefile_37058_0.jpg
182 ms
cachefile_37494_0.jpg
182 ms
cachefile_36821_0.jpg
205 ms
cachefile_37723_0.jpg
205 ms
cachefile_37709_0.jpg
206 ms
cachefile_37762_0.jpg
206 ms
bamilo-header53.gif
257 ms
cachefile_37628_0.jpg
203 ms
Galaxy_A2016.png
128 ms
gooshishop-120x240_04.gif
201 ms
cachefile_37856_-1.jpg
193 ms
cachefile_37776_-1.jpg
192 ms
cachefile_37736_-1.jpg
192 ms
cachefile_37855_-1.jpg
187 ms
cachefile_37613_-1.jpg
187 ms
jiring_02.gif
187 ms
meghdad_01.gif
126 ms
esam06.gif
132 ms
nescafe_03.gif
132 ms
default.image.jpg
125 ms
default.image.jpg
147 ms
default.image.jpg
165 ms
allsprites.png
130 ms
playerbtn-home.png
130 ms
icons.sprite.png
164 ms
icons.sprite.png
165 ms
icons.sprite.png
165 ms
NassimBold.woff
183 ms
Nassim.woff
269 ms
atramart_06.gif
86 ms
trigger.gif
59 ms
icons.sprite.png
67 ms
analytics.js
22 ms
linkid.js
12 ms
collect
13 ms
mobile.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.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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>).
mobile.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
mobile.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
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.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 Mobile.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.ir
Open Graph description is not detected on the main page of Mobile. 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: