Tools & Wizards About Us
mamsky.ru screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

mamsky.ru

Интернет магазин недорогой одежды для беременных и одежды для кормящих мам в Москве

Page Load Speed

4.5 sec in total

First Response

351 ms

Resources Loaded

3.8 sec

Page Rendered

353 ms

mamsky.ru screenshot

About Website

Click here to check amazing Mamsky content for Russia. Otherwise, check out these important facts you probably never knew about mamsky.ru

Интернет магазин: одежда для беременных, одежда для кормящих мам, нижнее белье для кормления грудью, бандажи послеродовые, нижнее белье для беременных, верхняя и зимняя одежда для беременных, платья д...

Visit mamsky.ru

Key Findings

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

Performance Metrics

mamsky.ru performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

96/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value2,770 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value27.4 s

0/100

10%

Network Requests Diagram

mamsky.ru

351 ms

template_css.css

190 ms

openapi.js

324 ms

email-decode.min.js

27 ms

JSCookMenu.js

264 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 33% of them (22 requests) were addressed to the original Mamsky.ru, 28% (19 requests) were made to St6-21.vk.com and 12% (8 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source St6-21.vk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.9 kB (13%)

Content Size

654.8 kB

After Optimization

572.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mamsky.ru main page is 654.8 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. 60% of websites need less resources to load. CSS take 466.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 65.7 kB

  • Original 80.5 kB
  • After minification 65.5 kB
  • After compression 14.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 15.0 kB, which is 19% 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 65.7 kB or 82% of the original size.

Image Optimization

-13%

Potential reduce by 9.7 kB

  • Original 76.5 kB
  • After minification 66.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. Obviously, Mamsky needs image optimization as it can save up to 9.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 6.5 kB

  • Original 31.6 kB
  • After minification 29.6 kB
  • After compression 25.1 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 6.5 kB or 20% of the original size.

CSS Optimization

-0%

Potential reduce by 979 B

  • Original 466.3 kB
  • After minification 466.3 kB
  • After compression 465.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. Mamsky.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (69%)

Requests Now

62

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mamsky. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

mamsky.ru

mamsky.ru

351 ms

template_css.css

template_css.css

190 ms

openapi.js

openapi.js

324 ms

email-decode.min.js

email-decode.min.js

27 ms

JSCookMenu.js

JSCookMenu.js

264 ms

theme.css

theme.css

184 ms

theme.js

theme.js

194 ms

mambojavascript.js

mambojavascript.js

240 ms

logotxt.gif

logotxt.gif

244 ms

Dostavka_banner.png

Dostavka_banner.png

164 ms

sskinnude4_x250.jpg

sskinnude4_x250.jpg

254 ms

all.js

all.js

47 ms

topmenubg_l.gif

topmenubg_l.gif

240 ms

topmenubg.gif

topmenubg.gif

240 ms

topmenubg_r.gif

topmenubg_r.gif

238 ms

upleft.gif

upleft.gif

416 ms

upmid.gif

upmid.gif

393 ms

upright.gif

upright.gif

394 ms

lm_side1.gif

lm_side1.gif

395 ms

lm_side.gif

lm_side.gif

385 ms

all.js

all.js

47 ms

bottomleft.gif

bottomleft.gif

189 ms

bottommid.gif

bottommid.gif

204 ms

bottomright.gif

bottomright.gif

201 ms

upload.gif

upload.gif

255 ms

widget_community.php

widget_community.php

270 ms

watch.js

watch.js

10 ms

analytics.js

analytics.js

63 ms

xdiWD5S7T3

xdiWD5S7T3

538 ms

collect

collect

28 ms

65 ms

upload.gif

upload.gif

520 ms

widget_community.php

widget_community.php

571 ms

xdiWD5S7T3

xdiWD5S7T3

562 ms

loader_nav21526008798_3.js

loader_nav21526008798_3.js

412 ms

fonts_cnt.5df9a2d31f91db9fc063.css

fonts_cnt.5df9a2d31f91db9fc063.css

997 ms

lite.6af08af59db160f1d821.css

lite.6af08af59db160f1d821.css

536 ms

lite.js

lite.js

280 ms

lang3_0.js

lang3_0.js

427 ms

xdm.js

xdm.js

452 ms

ui_common.f84b667095c1513ae4a5.css

ui_common.f84b667095c1513ae4a5.css

469 ms

vendors.1505d7877b40f6cb4dac.js

vendors.1505d7877b40f6cb4dac.js

638 ms

palette.c11f1080c2b166a63023.js

palette.c11f1080c2b166a63023.js

554 ms

audioplayer.1fff3154e7b8519a9805.js

audioplayer.1fff3154e7b8519a9805.js

659 ms

common.8d42e5f565f4fc010343.js

common.8d42e5f565f4fc010343.js

930 ms

ui_common.851b2b33538608cb0914.css

ui_common.851b2b33538608cb0914.css

626 ms

ui_common.4471ba55c7a94980f60a.js

ui_common.4471ba55c7a94980f60a.js

669 ms

audioplayer.851b2b33538608cb0914.css

audioplayer.851b2b33538608cb0914.css

717 ms

audioplayer.a973faf2d3af5fffdd34.js

audioplayer.a973faf2d3af5fffdd34.js

721 ms

widget_community.ad42a33851e9f0531ecc.css

widget_community.ad42a33851e9f0531ecc.css

745 ms

likes.851b2b33538608cb0914.css

likes.851b2b33538608cb0914.css

762 ms

likes.dc023372a4b0549e2e40.js

likes.dc023372a4b0549e2e40.js

808 ms

community.js

community.js

1189 ms

base.9e3d08c055bdd0c7ee80.css

base.9e3d08c055bdd0c7ee80.css

852 ms

AVG-tU5d9J3TvEzEx-PsQ1CI15CgGxWLJk_wGiPcbBZGe8bEgas9PAtk8J279vLLelzW0NB52zSkzAHPbN3icHTE.jpg

AVG-tU5d9J3TvEzEx-PsQ1CI15CgGxWLJk_wGiPcbBZGe8bEgas9PAtk8J279vLLelzW0NB52zSkzAHPbN3icHTE.jpg

460 ms

camera_50.png

camera_50.png

178 ms

XvpWlwb6ZE1vpQgX3oPqNVYrLb6Td3E89XtWu2ifs-BAB63N_7mvvxGED5_Z-7hVpeucrY36IiUQyu4Spl6m2kIv.jpg

XvpWlwb6ZE1vpQgX3oPqNVYrLb6Td3E89XtWu2ifs-BAB63N_7mvvxGED5_Z-7hVpeucrY36IiUQyu4Spl6m2kIv.jpg

426 ms

TuOz3uh4oO0GYavOCpUa8oUb-LpWKPvJAl5UZ6hJ28QFdNAyCULRiq8SXMhgPkfcjNj-moIRakt9_hCRwkFIGCLU.jpg

TuOz3uh4oO0GYavOCpUa8oUb-LpWKPvJAl5UZ6hJ28QFdNAyCULRiq8SXMhgPkfcjNj-moIRakt9_hCRwkFIGCLU.jpg

433 ms

HtPlviH1SCAZ8LsaC4u6BLu2Ia5UarZ0pNWwlEvnc0MQrxgPmFx8p13cRncJOqN6SBZVG2xc.jpg

HtPlviH1SCAZ8LsaC4u6BLu2Ia5UarZ0pNWwlEvnc0MQrxgPmFx8p13cRncJOqN6SBZVG2xc.jpg

517 ms

XUKscdXo637ifSBkNgfjVDU-Dq9eDxTulGxbF1va2kEyCSP6VSIg-6Pkm8fUOVHwKvXuH1AVwEdwtUYOysv_zPOf.jpg

XUKscdXo637ifSBkNgfjVDU-Dq9eDxTulGxbF1va2kEyCSP6VSIg-6Pkm8fUOVHwKvXuH1AVwEdwtUYOysv_zPOf.jpg

448 ms

r5NLPBA0Gv6hvyCgZ-GkWcZDIJGJPaHE1Vf6gOWZMpYmeggs1o3e3JlZgjEoUUqxtWAVlT5-.jpg

r5NLPBA0Gv6hvyCgZ-GkWcZDIJGJPaHE1Vf6gOWZMpYmeggs1o3e3JlZgjEoUUqxtWAVlT5-.jpg

487 ms

jltCvVQ22saWUSPB37S_w0WY63dSLWbJAwmBleWwJlRJIJNx4MJU0rgMtvW2fTptO5Rlxbdho7HjQ0akxrXi5tF4.jpg

jltCvVQ22saWUSPB37S_w0WY63dSLWbJAwmBleWwJlRJIJNx4MJU0rgMtvW2fTptO5Rlxbdho7HjQ0akxrXi5tF4.jpg

488 ms

cH7RXcrzDGtLjwjOs4g61E3oM_HS3JZ97hSuX7NHFx0WSFyxNZPh708up7KzkraEzw3k_qa14EFTbRcqahIRU8rG.jpg

cH7RXcrzDGtLjwjOs4g61E3oM_HS3JZ97hSuX7NHFx0WSFyxNZPh708up7KzkraEzw3k_qa14EFTbRcqahIRU8rG.jpg

610 ms

yCLiMkcQCOu3FKiTAhUwiecCIxZOHXX4RRYBYQZqVoUgF0MawBL9c3qXIUs7I0RxuAbrfpzYfthLWnOK4CrO4dYu.jpg

yCLiMkcQCOu3FKiTAhUwiecCIxZOHXX4RRYBYQZqVoUgF0MawBL9c3qXIUs7I0RxuAbrfpzYfthLWnOK4CrO4dYu.jpg

402 ms

by0lIH1_0uADOl4z9reP54k4arEWYc5J_m89so2YkKiD02uf9OMNuY-SxOpMU3gUB2WLPA.jpg

by0lIH1_0uADOl4z9reP54k4arEWYc5J_m89so2YkKiD02uf9OMNuY-SxOpMU3gUB2WLPA.jpg

511 ms

post_widget.png

post_widget.png

166 ms

upload.gif

upload.gif

167 ms

Accessibility Review

mamsky.ru accessibility score

81

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

mamsky.ru best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

mamsky.ru SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

mamsky.ru

Open Graph description is not detected on the main page of Mamsky. 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: