Tools & Wizards About Us
ampika.ru screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

ampika.ru

Ампика - продажа и производство насосов, насосного оборудования

Page Load Speed

6.4 sec in total

First Response

953 ms

Resources Loaded

5.2 sec

Page Rendered

229 ms

ampika.ru screenshot

About Website

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

Компания «Ампика» является представителем более чем тридцати насосных заводов России, стран СНГ и дальнего зарубежья. Мы работаем на рынке насосов и насосного оборудования уже более 15 лет.

Visit ampika.ru

Key Findings

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

Performance Metrics

ampika.ru performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

ampika.ru

953 ms

www.ampika.ru

728 ms

jquery-1.12.4.min.js

265 ms

swiper.css

387 ms

swiper.min.js

528 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 66% of them (25 requests) were addressed to the original Ampika.ru, 11% (4 requests) were made to Top-fwz1.mail.ru and 5% (2 requests) were made to Code.jivo.ru. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.2 kB (15%)

Content Size

275.3 kB

After Optimization

234.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 33.3 kB

  • Original 44.8 kB
  • After minification 40.7 kB
  • After compression 11.5 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.3 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 855 B

  • Original 21.1 kB
  • After minification 20.2 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. Ampika images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.7 kB

  • Original 191.7 kB
  • After minification 191.7 kB
  • After compression 187.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-13%

Potential reduce by 2.4 kB

  • Original 17.7 kB
  • After minification 17.7 kB
  • After compression 15.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. Ampika.ru needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (74%)

Requests Now

35

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ampika.ru

ampika.ru

953 ms

www.ampika.ru

www.ampika.ru

728 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

265 ms

swiper.css

swiper.css

387 ms

swiper.min.js

swiper.min.js

528 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

398 ms

scroll.js

scroll.js

393 ms

header.css

header.css

418 ms

userstyle.css

userstyle.css

417 ms

breadcrumbs.css

breadcrumbs.css

516 ms

collapse.js

collapse.js

521 ms

ab6Xzc8dPW

ab6Xzc8dPW

415 ms

main.js

main.js

540 ms

fonts.css

fonts.css

548 ms

price_list.css

price_list.css

548 ms

magnific-popup.css

magnific-popup.css

642 ms

mobile.css

mobile.css

647 ms

card.css

card.css

135 ms

gtm.js

gtm.js

98 ms

logo.svg

logo.svg

132 ms

ampika-hms-small.jpg

ampika-hms-small.jpg

163 ms

lypa.png

lypa.png

134 ms

empty.gif

empty.gif

165 ms

youtube.png

youtube.png

163 ms

header-bg.jpg

header-bg.jpg

156 ms

sprite.svg

sprite.svg

320 ms

car.png

car.png

322 ms

ab6Xzc8dPW

ab6Xzc8dPW

176 ms

hit

hit

545 ms

code.js

code.js

782 ms

js

js

56 ms

tag.js

tag.js

2601 ms

ab6Xzc8dPW

ab6Xzc8dPW

554 ms

hit

hit

140 ms

counter2

counter2

139 ms

sync-loader.js

sync-loader.js

875 ms

counter

counter

140 ms

dyn-goal-config.js

dyn-goal-config.js

141 ms

Accessibility Review

ampika.ru accessibility score

62

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

Image elements do not have [alt] attributes

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.

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

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

ampika.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

Missing source maps for large first-party JavaScript

SEO Factors

ampika.ru SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    UTF-8

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

ampika.ru

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