Tools & Wizards About Us
msphone.ru screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

msphone.ru

MS.Phone – телефоны, планшеты, смарт-часы, игрушки по доступным ценам

Page Load Speed

7.5 sec in total

First Response

496 ms

Resources Loaded

6.7 sec

Page Rendered

306 ms

msphone.ru screenshot

About Website

Welcome to msphone.ru homepage info - get ready to check MS Phone best content for Russia right away, or after learning these important things about msphone.ru

MSphone магазин электронных товаров, телефонов и и аксессуаров

Visit msphone.ru

Key Findings

We analyzed Msphone.ru page load time and found that the first response time was 496 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

msphone.ru performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

msphone.ru

496 ms

msphone.ru

1302 ms

notice.min.css

266 ms

ui.design-tokens.min.css

392 ms

ui.font.opensans.min.css

393 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 53% of them (41 requests) were addressed to the original Msphone.ru, 12% (9 requests) were made to Leadback.ru and 8% (6 requests) were made to Static.cloudim.ru. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Msphone.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (36%)

Content Size

2.9 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Msphone.ru main page is 2.9 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. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 635.3 kB

  • Original 713.6 kB
  • After minification 560.8 kB
  • After compression 78.3 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 152.7 kB, which is 21% 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 635.3 kB or 89% of the original size.

Image Optimization

-17%

Potential reduce by 221.6 kB

  • Original 1.3 MB
  • After minification 1.1 MB

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, MS Phone needs image optimization as it can save up to 221.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-18%

Potential reduce by 101.1 kB

  • Original 571.0 kB
  • After minification 570.9 kB
  • After compression 469.9 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 101.1 kB or 18% of the original size.

CSS Optimization

-29%

Potential reduce by 91.4 kB

  • Original 318.6 kB
  • After minification 318.6 kB
  • After compression 227.2 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. Msphone.ru needs all CSS files to be minified and compressed as it can save up to 91.4 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (75%)

Requests Now

73

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

msphone.ru

msphone.ru

496 ms

msphone.ru

msphone.ru

1302 ms

notice.min.css

notice.min.css

266 ms

ui.design-tokens.min.css

ui.design-tokens.min.css

392 ms

ui.font.opensans.min.css

ui.font.opensans.min.css

393 ms

main.popup.bundle.min.css

main.popup.bundle.min.css

394 ms

carousel.css

carousel.css

32 ms

template_34b27c5c1de1103f3a8d6ca479d6afcf_v1.css

template_34b27c5c1de1103f3a8d6ca479d6afcf_v1.css

1195 ms

core.min.js

core.min.js

686 ms

protobuf.min.js

protobuf.min.js

401 ms

model.min.js

model.min.js

522 ms

core_promise.min.js

core_promise.min.js

522 ms

rest.client.min.js

rest.client.min.js

523 ms

pull.client.min.js

pull.client.min.js

535 ms

ajax.min.js

ajax.min.js

650 ms

notice.min.js

notice.min.js

651 ms

main.popup.bundle.min.js

main.popup.bundle.min.js

781 ms

carousel.umd.js

carousel.umd.js

46 ms

currency-core.bundle.min.js

currency-core.bundle.min.js

665 ms

core_currency.min.js

core_currency.min.js

777 ms

critical.min.css

critical.min.css

778 ms

observer.js

observer.js

797 ms

ls.unveilhooks.min.js

ls.unveilhooks.min.js

816 ms

lazysizes.min.js

lazysizes.min.js

906 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

1037 ms

speed.min.js

speed.min.js

909 ms

bottom_panel.min.js

bottom_panel.min.js

929 ms

template_c42bfd160c728034bb2f998f73151141_v1.js

template_c42bfd160c728034bb2f998f73151141_v1.js

1297 ms

default_33b99ad265b97fa7007a075a3d5bf8bc_v1.js

default_33b99ad265b97fa7007a075a3d5bf8bc_v1.js

1033 ms

setTheme.php

setTheme.php

1063 ms

code.js

code.js

752 ms

ba.js

ba.js

316 ms

gxqdw9h7gstgctrt6zupdpt0e7chhyw2.png

gxqdw9h7gstgctrt6zupdpt0e7chhyw2.png

147 ms

07nnxpt5aa7vj0dinabrk8h2ibq1ojo2.png

07nnxpt5aa7vj0dinabrk8h2ibq1ojo2.png

527 ms

double_ring.svg

double_ring.svg

142 ms

header_icons_srite.svg

header_icons_srite.svg

144 ms

trianglearrow_sprite.svg

trianglearrow_sprite.svg

135 ms

ex3u7pdkn43ep2ra5acohbe0i95gsv4o.png

ex3u7pdkn43ep2ra5acohbe0i95gsv4o.png

829 ms

header_icons.svg

header_icons.svg

154 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

4 ms

social.svg

social.svg

427 ms

payment.svg

payment.svg

408 ms

tag.js

tag.js

868 ms

leadback.js

leadback.js

756 ms

2t4h2u4aqi37rmkswl0tb3r24afxeg14.png

2t4h2u4aqi37rmkswl0tb3r24afxeg14.png

132 ms

i4hw1wnvxzyhsu8hr3d6rnoo82cubs7p.jpg

i4hw1wnvxzyhsu8hr3d6rnoo82cubs7p.jpg

921 ms

0aoivezn3ohqe0okyiyrziraq7qmshvv.jpg

0aoivezn3ohqe0okyiyrziraq7qmshvv.jpg

265 ms

bx_stat

bx_stat

184 ms

sync-loader.js

sync-loader.js

956 ms

counter

counter

156 ms

dyn-goal-config.js

dyn-goal-config.js

277 ms

analytics.js

analytics.js

17 ms

jquery.min.js

jquery.min.js

38 ms

collect

collect

23 ms

widget_uuid.php

widget_uuid.php

135 ms

widget_data.php

widget_data.php

235 ms

print.min.css

print.min.css

134 ms

advert.gif

advert.gif

846 ms

chat.js

chat.js

812 ms

_assets.min.js

_assets.min.js

97 ms

widget_event.php

widget_event.php

202 ms

widget_widget.php

widget_widget.php

215 ms

css

css

43 ms

chat.css

chat.css

106 ms

cobrowsing.css

cobrowsing.css

133 ms

sync_cookie_image_decide

sync_cookie_image_decide

202 ms

103 ms

widget2.css

widget2.css

931 ms

ua-parser.min.js

ua-parser.min.js

958 ms

_chat_socket.min.js

_chat_socket.min.js

1273 ms

watch.js

watch.js

0 ms

1

1

155 ms

arrow.png

arrow.png

96 ms

im_enter.png

im_enter.png

96 ms

cloudim-chat-label.png

cloudim-chat-label.png

95 ms

default.png

default.png

96 ms

online.php

online.php

184 ms

leadback-chat-api.js

leadback-chat-api.js

192 ms

Accessibility Review

msphone.ru accessibility score

69

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

msphone.ru best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

msphone.ru SEO score

89

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

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

Social Sharing Optimization

msphone.ru

Open Graph data is detected on the main page of MS Phone. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: