Tools & Wizards About Us
mymobile.ir screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 41

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

mymobile.ir

گوشی های فروشی کاربران - خرید گوشی موبایل | mobile.ir - مرجع موبایل ایران

Page Load Speed

3 sec in total

First Response

1.1 sec

Resources Loaded

1.7 sec

Page Rendered

190 ms

mymobile.ir screenshot

About Website

Welcome to mymobile.ir homepage info - get ready to check My Mobile best content for Iran right away, or after learning these important things about mymobile.ir

خرید و فروش انواع گوشی موبایل نو و دسته دوم در مرجع موبایل ایران با امکان درج آگهی رایگان فروش گوشی موبایل

Visit mymobile.ir

Key Findings

We analyzed Mymobile.ir page load time and found that the first response time was 1.1 sec and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster. This domain responded with an error, which can significantly jeopardize Mymobile.ir rating and web reputation

Performance Metrics

mymobile.ir performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

mymobile.ir

1127 ms

common.css

137 ms

common_fa.css

138 ms

theme_mymobile.css

138 ms

theme_mymobile_fa.css

139 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 31% of them (8 requests) were addressed to the original Mymobile.ir, 69% (18 requests) were made to S.mobile.ir. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Mymobile.ir.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.8 kB (32%)

Content Size

101.8 kB

After Optimization

69.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mymobile.ir main page is 101.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. Only 10% of websites need less resources to load. Images take 64.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 10.6 kB

  • Original 13.1 kB
  • After minification 12.5 kB
  • After compression 2.5 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 10.6 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 6.9 kB

  • Original 64.8 kB
  • After minification 57.9 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, My Mobile needs image optimization as it can save up to 6.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 11.5 kB

  • Original 18.5 kB
  • After minification 18.0 kB
  • After compression 7.0 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 11.5 kB or 62% of the original size.

CSS Optimization

-70%

Potential reduce by 3.8 kB

  • Original 5.4 kB
  • After minification 4.1 kB
  • After compression 1.6 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. Mymobile.ir needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (13%)

Requests Now

24

After Optimization

21

  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My 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 CSS and as a result speed up the page load time.

Network Requests Diagram

mymobile.ir

mymobile.ir

1127 ms

common.css

common.css

137 ms

common_fa.css

common_fa.css

138 ms

theme_mymobile.css

theme_mymobile.css

138 ms

theme_mymobile_fa.css

theme_mymobile_fa.css

139 ms

mootools.release.83.js

mootools.release.83.js

206 ms

mymobile.ir.js

mymobile.ir.js

335 ms

cachefile_37411_2.jpg

cachefile_37411_2.jpg

220 ms

mobile_ir.gif

mobile_ir.gif

273 ms

cachefile_37586_2.jpg

cachefile_37586_2.jpg

230 ms

cachefile_37619_2.jpg

cachefile_37619_2.jpg

235 ms

cachefile_37242_2.jpg

cachefile_37242_2.jpg

210 ms

cachefile_37393_2.jpg

cachefile_37393_2.jpg

220 ms

cachefile_37690_2.jpg

cachefile_37690_2.jpg

234 ms

cachefile_37591_2.jpg

cachefile_37591_2.jpg

241 ms

cachefile_34759_2.jpg

cachefile_34759_2.jpg

289 ms

cachefile_34057_2.jpg

cachefile_34057_2.jpg

281 ms

cachefile_36189_2.jpg

cachefile_36189_2.jpg

320 ms

cachefile_33452_2.jpg

cachefile_33452_2.jpg

322 ms

cachefile_37898_2.jpg

cachefile_37898_2.jpg

319 ms

cachefile_37876_2.jpg

cachefile_37876_2.jpg

320 ms

cachefile_37339_2.jpg

cachefile_37339_2.jpg

361 ms

cachefile_37275_2.jpg

cachefile_37275_2.jpg

341 ms

cachefile_37873_2.jpg

cachefile_37873_2.jpg

364 ms

cachefile_37902_2.jpg

cachefile_37902_2.jpg

372 ms

cachefile_37257_2.jpg

cachefile_37257_2.jpg

361 ms

Accessibility Review

mymobile.ir accessibility score

41

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

mymobile.ir best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mymobile.ir SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mymobile.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 Mymobile.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.

Social Sharing Optimization

mymobile.ir

Open Graph description is not detected on the main page of My 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: