3.8 sec in total
813 ms
2.8 sec
214 ms
Welcome to sotofone.ru homepage info - get ready to check Sotofone best content for Russia right away, or after learning these important things about sotofone.ru
В интернет-магазине Sotofone.ru вы можете купить iPhone и другие мобильные устройства на выгодных условиях. Детали по контактным телефонам в Петербурге: +7 (812) 953-26-66, +7 (911) 123-55-55.
Visit sotofone.ruWe analyzed Sotofone.ru page load time and found that the first response time was 813 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
sotofone.ru performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value9.0 s
1/100
25%
Value4.8 s
66/100
10%
Value100 ms
98/100
30%
Value0.022
100/100
15%
Value5.6 s
69/100
10%
813 ms
211 ms
212 ms
216 ms
218 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 97% of them (73 requests) were addressed to the original Sotofone.ru, 3% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Sotofone.ru.
Page size can be reduced by 187.1 kB (15%)
1.2 MB
1.0 MB
In fact, the total size of Sotofone.ru main page is 1.2 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. Images take 824.4 kB which makes up the majority of the site volume.
Potential reduce by 62.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 12.9 kB, which is 16% 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 62.6 kB or 78% of the original size.
Potential reduce by 53.3 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. Sotofone images are well optimized though.
Potential reduce by 42.2 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 42.2 kB or 18% of the original size.
Potential reduce by 29.0 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. Sotofone.ru needs all CSS files to be minified and compressed as it can save up to 29.0 kB or 35% of the original size.
Number of requests can be reduced by 21 (30%)
70
49
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sotofone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
sotofone.ru
813 ms
core.min.css
211 ms
kernel_main_v1.css
212 ms
ui.font.opensans.min.css
216 ms
main.popup.bundle.min.css
218 ms
page_f2e9296204b1ee2caf5b9b35d27d7501_v1.css
223 ms
template_98b7b824aac3248e97c37a6e1b4e068d_v1.css
450 ms
popup.min.css
316 ms
core.min.js
539 ms
kernel_main_v1.js
431 ms
main.popup.bundle.min.js
433 ms
template_6cae5439c906a1e0a370850b6892c2ea_v1.js
668 ms
page_d6c0084bf6a16988333ec00ef75bc088_v1.js
421 ms
ba.js
139 ms
cfe82ac1f4b416d619faee4c1e1d2cc8.png
108 ms
c8aeb8fd47a10bfd868b8b90cdce9c75.png
109 ms
logo_new.png
112 ms
catalogButton.png
113 ms
b5a503a33c4401a295e945cbbee3c090.png
110 ms
3f956f6e9e65d3c8484893a86d8eb47d.png
108 ms
f486e592dbb99d385174dc278dc12993.png
213 ms
5e72f4c4953bc105b03764c4c4c77b7e.png
214 ms
68b803c74add8409ea4a750fa14c4a38.png
217 ms
5b9c8014824d57db9f4b8d5714ec09fd.png
218 ms
1.png
223 ms
2.png
224 ms
3.png
421 ms
4.png
318 ms
27c2d1bf381077c0debd4f88114f86f7.png
325 ms
49a9a87c3ff48c22122f9fe07dbcae94.png
325 ms
dad0a4637782c719f268f0df773fb0e7.png
334 ms
57b140cffd1218481f8aadde4647dc82.png
335 ms
2bfdbaa53960a620eb411b20ba7975c0.png
422 ms
a9ece94d51d2a0ac3b8494225f32446a.png
432 ms
98067622066ee989920d22e03eb27ec8.png
434 ms
427caf842a5e6950e48c25e37d76efd2.png
446 ms
d46496e1af6828ad928d811794adfcfa.png
445 ms
756553bbe480eff97a4332ac14d53441.png
525 ms
85f10ff33f70ec41c9524b2f04529579.png
530 ms
9f75d6a2229c6b4eb3d19385bd3f87be.png
540 ms
8637f558a6c59065621818f9fefb53e0.png
540 ms
61d771de003774380ca9386fd3cb0ef6.png
557 ms
af69de7cb957b9abb7ccf7eb45ceb513.png
556 ms
da5f7c273e81bdb989cdf1be6d8163b4.jpg
734 ms
638f9342aed796c813ed4b93761381be.jpg
634 ms
b4c6813273a3e330b42eba021c5c8d49.jpg
757 ms
1c824927fdd5dd582246bc1e0f72f9f0.jpg
868 ms
93b4354a3a6d47225a28cff6670e2d4e.jpg
779 ms
125c072c57c680075a94d057a0660284.png
777 ms
ad5b95e021ee766ad16f4050ef560909.png
933 ms
roboto-light.woff
737 ms
roboto-medium.woff
763 ms
roboto-bold.woff
787 ms
ajax_counter.php
1106 ms
picLoad.gif
838 ms
incart.png
868 ms
bx_stat
69 ms
request.png
768 ms
searchH2.png
793 ms
searchIcoH2.png
837 ms
compareH4.png
848 ms
wishlistH4.png
865 ms
cartH4.png
864 ms
slideArrow.png
801 ms
91fd11e68fa1f9e8eff357fc190439e5.jpg
836 ms
e3b1484b6c6a1cb7423ac9c74a1c3bec.jpg
847 ms
12a47f552f6472d746de196346e3ab87.jpg
861 ms
ccf5d1e67aacf58e7754d8d61b1786cc.jpg
861 ms
f19c76dd12554445b5b97db16a552a64.jpg
810 ms
aa39fd7f8fd39150cd1314794fd11672.jpg
948 ms
callbackFooterMin.png
846 ms
compareFooterMin.png
870 ms
wishlistFooterMin.png
858 ms
cartFooterMin.png
879 ms
up.png
815 ms
sotofone.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
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.
sotofone.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
sotofone.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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sotofone.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 Sotofone.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.
sotofone.ru
Open Graph description is not detected on the main page of Sotofone. 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: