3.4 sec in total
263 ms
2.7 sec
500 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 263 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
mobile.ir performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value6.3 s
11/100
25%
Value4.8 s
67/100
10%
Value150 ms
94/100
30%
Value0.162
72/100
15%
Value5.9 s
66/100
10%
263 ms
337 ms
523 ms
52 ms
485 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 11% of them (7 requests) were addressed to the original Mobile.ir, 87% (54 requests) were made to S.mobile.ir and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (673 ms) relates to the external source S.mobile.ir.
Page size can be reduced by 125.7 kB (30%)
426.1 kB
300.3 kB
In fact, the total size of Mobile.ir main page is 426.1 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. 25% of websites need less resources to load. Images take 137.3 kB which makes up the majority of the site volume.
Potential reduce by 107.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 15.4 kB, which is 12% 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 107.6 kB or 87% of the original size.
Potential reduce by 15.2 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 needs image optimization as it can save up to 15.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 365 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 2.5 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 has all CSS files already compressed.
Number of requests can be reduced by 7 (12%)
59
52
The browser has sent 59 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 and as a result speed up the page load time.
mobile.ir
263 ms
mobile.ir
337 ms
www.mobile.ir
523 ms
js
52 ms
style_common_133584028290000000.css
485 ms
style_player_132142537600000000.css
355 ms
script_common_133584028290000000.js
593 ms
script_player_132142537600000000.js
371 ms
1.gif
87 ms
3.gif
218 ms
4.gif
314 ms
5.gif
351 ms
allsprites.png
88 ms
40138_0.jpg
214 ms
40321_0.jpg
85 ms
40190_0.jpg
86 ms
39965_0.jpg
214 ms
19kala_129.gif
311 ms
lemoj_02.gif
216 ms
40418_1.jpg
217 ms
40417_1.jpg
311 ms
40416_1.jpg
311 ms
40404_1.jpg
312 ms
5381_1.jpg
347 ms
5382_1.jpg
346 ms
5379_1.jpg
346 ms
5378_1.jpg
347 ms
5377_0.jpg
428 ms
5380_0.jpg
429 ms
5375_0.jpg
423 ms
5376_0.jpg
420 ms
5374_0.jpg
420 ms
5371_0.jpg
424 ms
5370_0.jpg
494 ms
5373_0.jpg
495 ms
5360-VGbjy8eiOCY_120_0.jpg
498 ms
5345-nrlcAY6BVFs_120_0.jpg
505 ms
5330-tjag0wwY25I_120_0.jpg
507 ms
5327-FUCazvfaavg_120_0.jpg
507 ms
short-VGbjy8eiOCY_180_0.jpg
569 ms
short-2QPKq6_cMNI_180_0.jpg
569 ms
short-6GDgZ2SWH8k_180_0.jpg
574 ms
short-1oxgdG00XO0_180_0.jpg
584 ms
short-BbPc0FEfpbY_180_0.jpg
588 ms
39404_0.jpg
590 ms
40202_0.jpg
643 ms
38035_0.jpg
644 ms
38627_0.jpg
646 ms
38264_0.jpg
587 ms
technolife_b1_57.gif
673 ms
kasra_01.gif
636 ms
40322_50_0.jpg
515 ms
40276_50_0.jpg
513 ms
40216_50_0.jpg
520 ms
40189_50_0.jpg
534 ms
39402_-1.jpg
492 ms
39953_-1.jpg
492 ms
39105_-1.jpg
501 ms
39404_-1.jpg
519 ms
40357_-1.jpg
495 ms
Digikala_Samsung-Galaxy-A55_468x60.jpg
530 ms
icons.sprite.png
532 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
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: