4.1 sec in total
431 ms
3.3 sec
395 ms
Welcome to mobime.ru homepage info - get ready to check Mobime best content for Russia right away, or after learning these important things about mobime.ru
Мобильные телефоны на Mobime.ru: обзоры смартфонов, новости сотовой связи, новые телефоны
Visit mobime.ruWe analyzed Mobime.ru page load time and found that the first response time was 431 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
mobime.ru performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value7.2 s
5/100
25%
Value7.1 s
30/100
10%
Value860 ms
33/100
30%
Value0.605
10/100
15%
Value15.4 s
7/100
10%
431 ms
675 ms
601 ms
404 ms
22 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Mobime.ru, 55% (44 requests) were made to Static.mobime.ru and 11% (9 requests) were made to Manprogress.com. The less responsive or slowest element that took the longest time to load (1000 ms) relates to the external source Ad.webnext.ru.
Page size can be reduced by 490.3 kB (50%)
985.0 kB
494.7 kB
In fact, the total size of Mobime.ru main page is 985.0 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. 45% of websites need less resources to load. Images take 350.2 kB which makes up the majority of the site volume.
Potential reduce by 69.0 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 69.0 kB or 80% of the original size.
Potential reduce by 18.0 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. Mobime images are well optimized though.
Potential reduce by 187.5 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 187.5 kB or 69% of the original size.
Potential reduce by 215.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. Mobime.ru needs all CSS files to be minified and compressed as it can save up to 215.8 kB or 78% of the original size.
Number of requests can be reduced by 31 (42%)
73
42
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
mobime.ru
431 ms
www.mobime.ru
675 ms
screen.css
601 ms
index.css
404 ms
jquery.min.js
22 ms
screen.js
627 ms
zp.js
649 ms
1000 ms
967 ms
load.js
9 ms
hit;Mobime
274 ms
watch.js
17 ms
logo.gif
91 ms
64.gif
99 ms
thumb20694.jpg
116 ms
thumb20693.jpg
191 ms
thumb20692.jpg
203 ms
thumb20691.jpg
200 ms
thumb20690.jpg
204 ms
thumb20689.jpg
212 ms
thumb20688.jpg
217 ms
thumb20686.jpg
284 ms
thumb20685.jpg
307 ms
thumb20684.jpg
295 ms
alcatel_evo_7_hd.jpg
333 ms
acer_iconia_tab_b1-a71.jpg
333 ms
lenovo_k900.jpg
356 ms
alcatel_one_touch_tpop.jpg
439 ms
alcatel_one_touch_scribe_hd.jpg
441 ms
alcatel_tab_8.jpg
442 ms
alcatel_one_touch_spop.jpg
443 ms
pantech_discover.jpg
460 ms
alcatel_tab_7.jpg
460 ms
alcatel_one_touch_mpop.jpg
475 ms
sony_xperia_z.jpg
485 ms
alcatel_tab_7_hd.jpg
517 ms
alcatel_one_touch_xpop.jpg
517 ms
huawei_ascend_w1.jpg
546 ms
sony_xperia_zl.jpg
547 ms
watch.js
0 ms
hit;Mobime
180 ms
3.jpg
516 ms
thumb240_20622.jpg
172 ms
thumb240_20173.jpg
182 ms
thumb240_18637.jpg
311 ms
thumb240_18486.jpg
209 ms
thumb240_17281.jpg
366 ms
fade-vert.png
293 ms
ug.png
319 ms
t1.gif
351 ms
extbanner.html
389 ms
plusone.js
54 ms
impression.html
306 ms
extra.js
313 ms
games.gif
302 ms
themes.gif
331 ms
images.gif
350 ms
animations.gif
355 ms
videos.gif
390 ms
screensavers.gif
392 ms
px.gif
10 ms
cnt
253 ms
pixel;r=638183070;a=p-WCeJmPS5E7cR4;fpan=1;fpa=P0-1342921948-1460119462582;ns=0;ce=1;je=0;sr=1024x768x32;enc=n;dst=0;et=1460119462582;tzo=-180;ref=;url=http%3A%2F%2Fwww.mobime.ru%2F;ogl=
15 ms
px.gif
4 ms
feed
402 ms
cb=gapi.loaded_0
9 ms
bootstrap.css
100 ms
animations.css
180 ms
main.css
181 ms
green.css
185 ms
jquery.min.js
273 ms
common.js
189 ms
reality-240-400.png
292 ms
jquery.cookie.js
120 ms
ga.js
18 ms
ga_social_tracking.js
63 ms
__utm.gif
5 ms
support.html
157 ms
plusone.js
31 ms
widgets.js
112 ms
mobime.ru 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.
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
Links do not have a discernible name
mobime.ru 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
Issues were logged in the Issues panel in Chrome Devtools
mobime.ru 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 uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobime.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Mobime.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
mobime.ru
Open Graph description is not detected on the main page of Mobime. 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: