3.1 sec in total
393 ms
2.3 sec
315 ms
Visit srv-mobile.ru now to see the best up-to-date Srv Mobile content for Russia and also check out these interesting facts you probably never knew about srv-mobile.ru
Продажа запчастей к мобильным телефонам, устройствам различных марок оптом и в розницу Москва. Широкий выбор аксессуаров для сотовых и мобильных устройств.
Visit srv-mobile.ruWe analyzed Srv-mobile.ru page load time and found that the first response time was 393 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
srv-mobile.ru performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.3 s
21/100
25%
Value7.1 s
31/100
10%
Value8,860 ms
0/100
30%
Value0.006
100/100
15%
Value15.4 s
7/100
10%
393 ms
26 ms
40 ms
123 ms
223 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 76% of them (71 requests) were addressed to the original Srv-mobile.ru, 10% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Srv-mobile.ru.
Page size can be reduced by 889.7 kB (56%)
1.6 MB
692.0 kB
In fact, the total size of Srv-mobile.ru main page is 1.6 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. 50% of websites need less resources to load. Javascripts take 821.9 kB which makes up the majority of the site volume.
Potential reduce by 87.8 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 30.5 kB, which is 29% 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 87.8 kB or 85% of the original size.
Potential reduce by 16.7 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. Srv Mobile images are well optimized though.
Potential reduce by 567.8 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 567.8 kB or 69% of the original size.
Potential reduce by 217.3 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. Srv-mobile.ru needs all CSS files to be minified and compressed as it can save up to 217.3 kB or 89% of the original size.
Number of requests can be reduced by 61 (74%)
82
21
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Srv 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 38 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
srv-mobile.ru
393 ms
css
26 ms
css
40 ms
kernel_main.css
123 ms
kernel_socialservices.css
223 ms
template_43c6085d7868860c329db39673556e70.css
336 ms
core.min.js
334 ms
core_db.min.js
226 ms
core_ajax.min.js
236 ms
json2.min.js
236 ms
core_ls.min.js
332 ms
core_fx.min.js
364 ms
core_frame_cache.min.js
365 ms
ajax.min.js
368 ms
ss.js
441 ms
modernizr-2.0.6.min.js
442 ms
jquery-1.8.3.min.js
555 ms
jquery-ui-1.10.2.custom.min.js
778 ms
jquery.mousewheel.min.js
468 ms
jquery.touchSwipe.min.js
470 ms
jquery.ui.touch-punch.min.js
550 ms
jquery.carouFredSel-6.2.1-packed.js
552 ms
jquery.fancybox.pack.js
584 ms
jquery.validate.min.js
587 ms
additional-methods.min.js
659 ms
jquery.maskedinput-1.3.1.min.js
662 ms
jquery.numberMask.js
662 ms
jquery.scrollbar.min.js
698 ms
debounce.js
702 ms
strx-magic-floating-sidebar-maker.js
769 ms
elementStatus.js
772 ms
selectStyler.js
772 ms
imagepreloader.js
820 ms
app.js
821 ms
functions.js
879 ms
cookie.js
880 ms
script.js
881 ms
srv-mobile.ru
1227 ms
ba.js
178 ms
analytics.js
149 ms
sdk.js
175 ms
line_marker-2.png
122 ms
logo.png
121 ms
line_marker-1.png
144 ms
blank.gif
144 ms
964_20x20_f66759d510707dfc12ec33f9d087e291.png
147 ms
965_20x20_de56c80e5a43be502667b1668bf0cb6f.png
234 ms
963_20x20_6fe0aa12f5873264eec2b30059b89562.png
236 ms
970_20x20_60c1a9db8b942f43b4308731cc4640ee.png
243 ms
966_20x20_868f85670febbfbd46d65430768790a1.png
244 ms
967_20x20_eed4ab71d4f5d088ab3953af67b1b993.png
266 ms
968_20x20_9732d6d1e20f9f8cf3d33cf00cf9617b.png
338 ms
969_20x20_36831dcc3c50a034e56f103b49613f1d.png
378 ms
971_20x20_520a6601e428fbce51100139cc5c5724.png
379 ms
972_20x20_6b24bb93df4dcb741ae07b311529723e.png
377 ms
973_20x20_932b65ceb3ffd87ba6dd20537abd3630.png
381 ms
974_20x20_e093ce101701b1e21aa60e2e59fc8e57.png
447 ms
975_20x20_4b632cbcfba672de5603119cb7ce5740.png
449 ms
976_20x20_13abbc6ca4635d940d9999f20c45c073.png
485 ms
icons.png
477 ms
slider_arrow-1.png
477 ms
47273_1290x_b047d4c2cfacd6ffd73bf9bf866b261b.jpg
844 ms
47274_1290x_e181bc35738c1a7d6f70960cc72a1efe.jpg
998 ms
47275_1290x_30252c9bfa62454baf4338dd17723c72.jpg
893 ms
li_marker.png
585 ms
280518_180x_f8a723600442ff5d38280c1a2b96a897.jpg
586 ms
268336_180x_b8138c9b36bf8de1f8f6f742a2bb6ce4.jpg
597 ms
260425_180x_a22c93c206e2241ea3b944bfcafad7b4.jpg
721 ms
245295_180x_69577bd6ee5b55fb546000850137a166.jpg
720 ms
233226_180x_cf479436a0d4f4710f0a29b521a24703.jpg
722 ms
payment_icon-1.png
809 ms
payment_icon-2.png
810 ms
payment_icon-3.png
828 ms
watch.js
177 ms
sprite-1x.png
810 ms
slider_dot.png
812 ms
RjgO7rYTmqiVp7vzi-Q5USZ2oysoEQEeKwjgmXLRnTc.ttf
57 ms
DXI1ORHCpsQm3Vp6mXoaTXdckgy16U_L-eNUgMz0EAk.ttf
56 ms
MTP_ySUJH_bn48VBG8sNSndckgy16U_L-eNUgMz0EAk.ttf
95 ms
k3k702ZOKiLJc3WVjuplzHdckgy16U_L-eNUgMz0EAk.ttf
95 ms
xjAJXh38I15wypJXxuGMBnEh7F1Z_3lydansdLiaPMg.ttf
94 ms
PRmiXeptR36kaC0GEAetxk3zLKZ99nDzxe08CEIyEW0.ttf
94 ms
PRmiXeptR36kaC0GEAetxtkwt9VrET3KSzeYk_1rUOU.ttf
94 ms
PRmiXeptR36kaC0GEAetxndM4L-fhhyuUnFhqCaTF8Y.ttf
74 ms
gk5FxslNkTTHtojXrkp-xMtVlSEZW0ZJMie8AtMQgO3r7w4p9aSvGirXi6XmeXNA.ttf
93 ms
collect
36 ms
bx_stat
210 ms
85 ms
xd_arbiter.php
183 ms
xd_arbiter.php
289 ms
watch.js
464 ms
rubl.woff
585 ms
advert.gif
91 ms
1
91 ms
srv-mobile.ru 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.
srv-mobile.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
srv-mobile.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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Srv-mobile.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Srv-mobile.ru 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.
srv-mobile.ru
Open Graph description is not detected on the main page of Srv 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: