Tools & Wizards About Us
nppiris.ru screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

nppiris.ru

Проектирование и изготовление металлоконструкций в Воронеже и других регионах России – завод ИРИСМАШ

Page Load Speed

4.5 sec in total

First Response

473 ms

Resources Loaded

3.6 sec

Page Rendered

409 ms

nppiris.ru screenshot

About Website

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

Компания «ИРИСМАШ» осуществляет проектирование и изготовление металлоконструкций. Доставка по всей России. Тел. +7 (473) 237-35-09.

Visit nppiris.ru

Key Findings

We analyzed Nppiris.ru page load time and found that the first response time was 473 ms and then it took 4 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

nppiris.ru performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value260 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

nppiris.ru

473 ms

xn--36-6kc5aay0aj9d.xn--p1ai

952 ms

ui.design-tokens.css

120 ms

ui.font.opensans.css

238 ms

main.popup.bundle.css

354 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Nppiris.ru, 4% (2 requests) were made to Bitrix.info and 2% (1 request) were made to Nppiris.ru. The less responsive or slowest element that took the longest time to load (952 ms) relates to the external source .

Page Optimization Overview & Recommendations

Page size can be reduced by 145.5 kB (7%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nppiris.ru main page is 2.0 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. 35% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 29.2 kB

  • Original 38.9 kB
  • After minification 35.0 kB
  • After compression 9.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. 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 29.2 kB or 75% of the original size.

Image Optimization

-7%

Potential reduce by 104.2 kB

  • Original 1.6 MB
  • After minification 1.5 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. Nppiris images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 9.2 kB

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

CSS Optimization

-6%

Potential reduce by 2.9 kB

  • Original 46.2 kB
  • After minification 46.2 kB
  • After compression 43.4 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. Nppiris.ru has all CSS files already compressed.

Requests Breakdown

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

Requests Now

43

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nppiris.ru

nppiris.ru

473 ms

xn--36-6kc5aay0aj9d.xn--p1ai

xn--36-6kc5aay0aj9d.xn--p1ai

952 ms

ui.design-tokens.css

ui.design-tokens.css

120 ms

ui.font.opensans.css

ui.font.opensans.css

238 ms

main.popup.bundle.css

main.popup.bundle.css

354 ms

style.css

style.css

355 ms

bootstrap.min.css

bootstrap.min.css

473 ms

slicknav.css

slicknav.css

356 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

356 ms

owl.carousel.min.css

owl.carousel.min.css

357 ms

owl.theme.default.min.css

owl.theme.default.min.css

468 ms

style.css

style.css

469 ms

style.css

style.css

471 ms

style.css

style.css

483 ms

form_style.css

form_style.css

483 ms

template_styles.css

template_styles.css

585 ms

core.js

core.js

941 ms

main.popup.bundle.js

main.popup.bundle.js

719 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

709 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

602 ms

jquery.min.js

jquery.min.js

722 ms

owl.carousel.min.js

owl.carousel.min.js

704 ms

jquery.slicknav.js

jquery.slicknav.js

722 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

827 ms

script.js

script.js

825 ms

form_script.js

form_script.js

837 ms

user_consent.js

user_consent.js

839 ms

user_consent.css

user_consent.css

839 ms

ba.js

ba.js

328 ms

bg_section_menu.png

bg_section_menu.png

123 ms

sprites.png

sprites.png

117 ms

a367e8762db7b72bb978a18e2bb13e21.png

a367e8762db7b72bb978a18e2bb13e21.png

586 ms

img1.jpg

img1.jpg

349 ms

img2.jpg

img2.jpg

237 ms

img3.jpg

img3.jpg

470 ms

5866aabc874e8934ee4c6f288ff610fc.png

5866aabc874e8934ee4c6f288ff610fc.png

233 ms

5479839bce54bb048f54b087c12ca824.png

5479839bce54bb048f54b087c12ca824.png

235 ms

690662859027e82638ba77780f90ea69.png

690662859027e82638ba77780f90ea69.png

349 ms

5fd8ab5725aa4edbea4aedde0880c794.png

5fd8ab5725aa4edbea4aedde0880c794.png

353 ms

company-img1.jpg

company-img1.jpg

353 ms

company-img2.jpg

company-img2.jpg

582 ms

company-img3.jpg

company-img3.jpg

813 ms

company-img4.jpg

company-img4.jpg

704 ms

captcha.php

captcha.php

489 ms

HelveticaNeue-CondensedRegular.ttf

HelveticaNeue-CondensedRegular.ttf

531 ms

framdcn.ttf

framdcn.ttf

521 ms

tag.js

tag.js

946 ms

bx_stat

bx_stat

187 ms

Accessibility Review

nppiris.ru accessibility score

76

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.

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

nppiris.ru best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

nppiris.ru SEO score

82

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

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

nppiris.ru

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