Tools & Wizards About Us
mfpoisk.ru screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

mfpoisk.ru

Воздушные шары оптом в Москве | Интернет-магазин «МФ Поиск»

Page Load Speed

13.2 sec in total

First Response

635 ms

Resources Loaded

11.4 sec

Page Rendered

1.2 sec

mfpoisk.ru screenshot

About Website

Visit mfpoisk.ru now to see the best up-to-date Mfpoisk content for Russia and also check out these interesting facts you probably never knew about mfpoisk.ru

Продажа воздушных шаров крупным и мелким оптом - от поставщика с доставкой по всей России ◈ Тематические надувные шарики из латекса и фольги для любого повода ◈ Более 4000 наименований товаров для пра...

Visit mfpoisk.ru

Key Findings

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

Performance Metrics

mfpoisk.ru performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

mfpoisk.ru

635 ms

www.mfpoisk.ru

6712 ms

kernel_main0.css

543 ms

template_12241c24f160ba35dae5b9dea1699eba0.css

748 ms

kernel_main.js

1408 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 73% of them (56 requests) were addressed to the original Mfpoisk.ru, 14% (11 requests) were made to Web.redhelper.ru and 4% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Mfpoisk.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 401.0 kB (52%)

Content Size

766.5 kB

After Optimization

365.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mfpoisk.ru main page is 766.5 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. 40% of websites need less resources to load. Javascripts take 421.8 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 33.4 kB

  • Original 46.2 kB
  • After minification 43.6 kB
  • After compression 12.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. 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 33.4 kB or 72% of the original size.

Image Optimization

-22%

Potential reduce by 58.6 kB

  • Original 261.6 kB
  • After minification 203.1 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, Mfpoisk needs image optimization as it can save up to 58.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 280.5 kB

  • Original 421.8 kB
  • After minification 421.1 kB
  • After compression 141.3 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 280.5 kB or 66% of the original size.

CSS Optimization

-78%

Potential reduce by 28.6 kB

  • Original 36.8 kB
  • After minification 32.7 kB
  • After compression 8.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. Mfpoisk.ru needs all CSS files to be minified and compressed as it can save up to 28.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (47%)

Requests Now

73

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mfpoisk.ru

mfpoisk.ru

635 ms

www.mfpoisk.ru

www.mfpoisk.ru

6712 ms

kernel_main0.css

kernel_main0.css

543 ms

template_12241c24f160ba35dae5b9dea1699eba0.css

template_12241c24f160ba35dae5b9dea1699eba0.css

748 ms

kernel_main.js

kernel_main.js

1408 ms

template_56c1c4876459b79ad912c2815572e0be.js

template_56c1c4876459b79ad912c2815572e0be.js

1205 ms

all_styles.css

all_styles.css

1214 ms

all_js.js

all_js.js

1483 ms

urchin.js

urchin.js

183 ms

main.js

main.js

983 ms

ba.js

ba.js

396 ms

reset.css

reset.css

118 ms

product.css

product.css

120 ms

logo

logo

366 ms

loader.gif

loader.gif

248 ms

chtop.png

chtop.png

156 ms

chl.png

chl.png

159 ms

heander_left.png

heander_left.png

157 ms

logo1.png

logo1.png

154 ms

home.png

home.png

166 ms

map.png

map.png

239 ms

mail.png

mail.png

242 ms

vkontakte6.png

vkontakte6.png

240 ms

youtube.png

youtube.png

243 ms

facebook.png

facebook.png

257 ms

b1.png

b1.png

355 ms

b2.png

b2.png

358 ms

b3.png

b3.png

357 ms

b4.png

b4.png

358 ms

b5.png

b5.png

361 ms

b6.png

b6.png

358 ms

chr.png

chr.png

446 ms

ch1.png

ch1.png

465 ms

basket_box.png

basket_box.png

631 ms

on.png

on.png

465 ms

but_newf.png

but_newf.png

462 ms

but_newl.png

but_newl.png

464 ms

but_new.png

but_new.png

545 ms

but_s.png

but_s.png

608 ms

but_s_l.png

but_s_l.png

606 ms

ch5.png

ch5.png

607 ms

top_catalog.png

top_catalog.png

615 ms

bul.png

bul.png

710 ms

pdf.jpg

pdf.jpg

789 ms

ch6.png

ch6.png

790 ms

h1f.png

h1f.png

787 ms

_upload_iblock_000_000746d76b77f8442d7de60887644b1c_thumb_200x150.jpg

_upload_iblock_000_000746d76b77f8442d7de60887644b1c_thumb_200x150.jpg

790 ms

_upload_iblock_35f_35f01eb56b4911b223bf5e7d496f2771_thumb_200x150.jpg

_upload_iblock_35f_35f01eb56b4911b223bf5e7d496f2771_thumb_200x150.jpg

790 ms

_upload_iblock_4b3_4b3d177b772b6b1239dca27f8d74cfc3_thumb_200x150.jpg

_upload_iblock_4b3_4b3d177b772b6b1239dca27f8d74cfc3_thumb_200x150.jpg

815 ms

_upload_iblock_b5f_b5f957d0bf926dc27389bdea4a0249c6_thumb_200x150.jpg

_upload_iblock_b5f_b5f957d0bf926dc27389bdea4a0249c6_thumb_200x150.jpg

782 ms

_upload_iblock_317_317ed6d222a154fb4bde5398fb5cbd7a_thumb_200x150.jpg

_upload_iblock_317_317ed6d222a154fb4bde5398fb5cbd7a_thumb_200x150.jpg

751 ms

_upload_iblock_3c3_3c34eee830d40da6e1feaead2bed06f6_thumb_200x150.jpg

_upload_iblock_3c3_3c34eee830d40da6e1feaead2bed06f6_thumb_200x150.jpg

750 ms

_upload_iblock_395_3957ef1aa138468b5211c81633ace318_thumb_200x150.jpg

_upload_iblock_395_3957ef1aa138468b5211c81633ace318_thumb_200x150.jpg

750 ms

avante_2-webfont.ttf

avante_2-webfont.ttf

857 ms

hit

hit

302 ms

73be794a76600ea7d9f548f51230c395.png

73be794a76600ea7d9f548f51230c395.png

1098 ms

watch.js

watch.js

1 ms

dc.js

dc.js

86 ms

bx_stat

bx_stat

291 ms

main.js

main.js

467 ms

start

start

514 ms

h1f.png

h1f.png

762 ms

footer_box.png

footer_box.png

764 ms

ch8.png

ch8.png

762 ms

ch7.png

ch7.png

762 ms

footer_ch.png

footer_ch.png

1004 ms

__utm.gif

__utm.gif

49 ms

jquery-new.min.js

jquery-new.min.js

309 ms

mfpoisk

mfpoisk

165 ms

Ava_default.png

Ava_default.png

158 ms

96ee8050-94e2-4ec6-9e50-98de29c2adfb.png

96ee8050-94e2-4ec6-9e50-98de29c2adfb.png

537 ms

__utm.gif

__utm.gif

50 ms

mac.css

mac.css

163 ms

259 ms

main.js

main.js

399 ms

mail.png

mail.png

143 ms

mac.css

mac.css

153 ms

Accessibility Review

mfpoisk.ru accessibility score

89

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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

Links do not have a discernible name

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

mfpoisk.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

mfpoisk.ru SEO score

91

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

    N/A

  • Encoding

    WINDOWS-1251

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

Social Sharing Optimization

mfpoisk.ru

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