8 sec in total
1.2 sec
6.2 sec
696 ms
Click here to check amazing Mobone content for Iran. Otherwise, check out these important facts you probably never knew about mobone.ir
رام,فا یل فلش,برنامه,تم,بازی,اخبار,آموزش
Visit mobone.irWe analyzed Mobone.ir page load time and found that the first response time was 1.2 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Mobone.ir rating and web reputation
mobone.ir performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value9.4 s
1/100
25%
Value6.6 s
38/100
10%
Value820 ms
36/100
30%
Value1.283
1/100
15%
Value9.1 s
33/100
10%
1153 ms
1766 ms
228 ms
223 ms
226 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 88% of them (94 requests) were addressed to the original Mobone.ir, 7% (8 requests) were made to Up.mobone.ir and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Mobone.ir.
Page size can be reduced by 906.7 kB (59%)
1.5 MB
628.6 kB
In fact, the total size of Mobone.ir main page is 1.5 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. 55% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 142.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. 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 142.6 kB or 84% of the original size.
Potential reduce by 20.8 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. Mobone images are well optimized though.
Potential reduce by 722.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 722.7 kB or 71% of the original size.
Potential reduce by 20.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. Mobone.ir needs all CSS files to be minified and compressed as it can save up to 20.6 kB or 76% of the original size.
Number of requests can be reduced by 21 (21%)
102
81
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
mobone.ir
1153 ms
popupcode
1766 ms
style.css
228 ms
responsive.css
223 ms
styles.css
226 ms
styles-rtl.css
226 ms
notifications.css
237 ms
addtoany.min.css
238 ms
ldc-lite.css
330 ms
wp-about-author.css
337 ms
jquery.js
452 ms
jquery-migrate.min.js
339 ms
notifications.js
356 ms
jquery-1.9.1.min.js
447 ms
json2.min.js
342 ms
livicons-1.3.min.js
819 ms
raphael-min.js
489 ms
main.js
455 ms
tooltip.js
457 ms
jquery.form.min.js
493 ms
scripts.js
556 ms
wp-embed.min.js
567 ms
wp-emoji-release.min.js
416 ms
do.php
1539 ms
1409810684091.png
378 ms
logo.png
380 ms
HTC-One-M9.png
382 ms
HTC-One-E9.png
384 ms
HTC-Desire-Eye.png
382 ms
HTC-Desire-826.png
385 ms
HTC-One-M8-s.png
386 ms
HTC-One-M9-Plus.png
387 ms
HTC-One-M8.png
389 ms
HTC-Desire-816.png
389 ms
HTC-One-Max.png
390 ms
HTC-One-mini%202.png
608 ms
Xperia-Z3%20Plus.png
609 ms
Xperia-Z3.png
610 ms
Xperia-M4-Aqua.png
611 ms
Xperia-E4.png
612 ms
Xperia-Z3-Compact.png
611 ms
Xperia-Z2.png
616 ms
Xperia-T3.png
615 ms
Xperia-E3.png
616 ms
Xperia-M2.png
618 ms
Xperia-T2-Ultra.png
669 ms
Galaxy-S6.png
619 ms
Galaxy-S6-Edge.png
643 ms
Galaxy-Note-Edge.png
653 ms
Galaxy-A5.png
656 ms
Galaxy-E5.png
664 ms
Galaxy-S5.png
670 ms
Galaxy-S4.png
750 ms
Galaxy-Note-3.png
767 ms
Galaxy-Mega.png
764 ms
Galaxy-S3.png
775 ms
Huawei-P8.png
780 ms
Honor-6.png
781 ms
Ascend-P6.png
856 ms
do.php
609 ms
do.php
1485 ms
do.php
1590 ms
do.php
607 ms
do.php
1383 ms
do.php
1689 ms
do.php
616 ms
ga.js
234 ms
iYekan.woff
612 ms
page.js
738 ms
Ascend-G6.png
514 ms
Honor-3X%20G750.png
519 ms
Ascend-G730.png
519 ms
Ascend-Mate7.png
590 ms
Ascend-G7.png
621 ms
Ascend-P7.png
731 ms
Huawei-Honor-3C.png
730 ms
LG-G4.png
731 ms
LG-G-Stylo.png
730 ms
LG-L90.png
772 ms
__utm.gif
187 ms
LG-Spirit.png
562 ms
LG-Magna.png
561 ms
LG%20G%20Flex%202.png
560 ms
LG-G3.png
630 ms
LG-G2.png
630 ms
LG%20G2-Mini.png
629 ms
LG-L70.png
628 ms
galaxy_a9-250x155.jpg
626 ms
galaxy_note_5-250x155.jpg
625 ms
Honor-4C-Full-B510-Marshmallow-250x155.jpeg
674 ms
Color-OS-3.0-250x155.png
804 ms
apple-id-250x151.png
953 ms
Xperia-X-Wallpapers-250x155.jpg
694 ms
honor-5x-stock-wallpapers-250x155.jpg
692 ms
Honor-4C-250x155.jpg
686 ms
honor-6-250x155.jpg
732 ms
galaxy-s6-marshmallow-6.0.1-250x155.jpg
791 ms
HTC-Desire-825-250x155.jpg
709 ms
Stock-Samsung-Galaxy-S7-S7-edge-250x155.png
930 ms
G5-250x155.jpg
740 ms
edge-250x155.jpg
764 ms
Samsung-Galaxy-Note-5-250x155.jpg
792 ms
1408421797221.png
791 ms
MTForumBlock_row_over.png
1135 ms
MTForumBlock_row.png
2493 ms
sm11.html
17 ms
hbpix
33 ms
mobone.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
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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
mobone.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
mobone.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 doesn't use 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 Mobone.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 Mobone.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.
mobone.ir
Open Graph data is detected on the main page of Mobone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: