Tools & Wizards About Us
nami.ru screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 34

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nami.ru

Государственный Научный Центр Российской Федерации ФГУП НАМИ

Page Load Speed

5.7 sec in total

First Response

521 ms

Resources Loaded

4.7 sec

Page Rendered

423 ms

nami.ru screenshot

About Website

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

ФГУП НАМИ — это современная научно-исследовательская, опытно-производственная база, которая позволяет решить любую задачу в области исследований, проектирования, построения, разработки и испытаний авт...

Visit nami.ru

Key Findings

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

nami.ru performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

nami.ru

521 ms

nami.ru

744 ms

burger.min.css

139 ms

bootstrap5.min.css

421 ms

component.css

414 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 97% of them (84 requests) were addressed to the original Nami.ru, 2% (2 requests) were made to Mc.yandex.com and 1% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nami.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 219.1 kB (9%)

Content Size

2.5 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 61.1 kB

  • Original 71.1 kB
  • After minification 57.7 kB
  • After compression 10.0 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 13.4 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 61.1 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 125.9 kB

  • Original 2.1 MB
  • After minification 2.0 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. Nami images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 18.7 kB

  • Original 273.3 kB
  • After minification 273.2 kB
  • After compression 254.5 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

-19%

Potential reduce by 13.4 kB

  • Original 69.9 kB
  • After minification 69.2 kB
  • After compression 56.6 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. Nami.ru needs all CSS files to be minified and compressed as it can save up to 13.4 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (64%)

Requests Now

83

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nami.ru

nami.ru

521 ms

nami.ru

nami.ru

744 ms

burger.min.css

burger.min.css

139 ms

bootstrap5.min.css

bootstrap5.min.css

421 ms

component.css

component.css

414 ms

accordeon.css

accordeon.css

434 ms

bootstrap-select.css

bootstrap-select.css

433 ms

font-awesome.min.css

font-awesome.min.css

436 ms

magnific-popup.css

magnific-popup.css

434 ms

jquery.arcticmodal-0.3.css

jquery.arcticmodal-0.3.css

551 ms

table.css

table.css

557 ms

accordion.css

accordion.css

566 ms

blocks.css

blocks.css

567 ms

main.css

main.css

567 ms

datepicker.css

datepicker.css

568 ms

carousel.css

carousel.css

687 ms

owl.carousel.css

owl.carousel.css

693 ms

slick.css

slick.css

706 ms

slick-theme.css

slick-theme.css

706 ms

video-js.css

video-js.css

707 ms

flexslider.css

flexslider.css

707 ms

html5shiv.js

html5shiv.js

823 ms

respond.min.js

respond.min.js

828 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

992 ms

bootstrap.min.js

bootstrap.min.js

848 ms

dropdown.js

dropdown.js

847 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

847 ms

jquery.mask.js

jquery.mask.js

958 ms

alert.js

alert.js

963 ms

modal.js

modal.js

988 ms

tooltip.js

tooltip.js

988 ms

transition.js

transition.js

988 ms

bootstrap-select.js

bootstrap-select.js

1098 ms

modernizr.custom.js

modernizr.custom.js

1100 ms

jquery.animateNumber.min.js

jquery.animateNumber.min.js

1128 ms

accordeon.js

accordeon.js

1128 ms

jquery.accordion.js

jquery.accordion.js

1129 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1128 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1108 ms

jquery.mousewheel-3.0.4.pack.js

jquery.mousewheel-3.0.4.pack.js

836 ms

jquery.arcticmodal-0.3.min.js

jquery.arcticmodal-0.3.min.js

846 ms

accordion.js

accordion.js

846 ms

datepicker.js

datepicker.js

847 ms

burger.min.js

burger.min.js

844 ms

owl.carousel.min.js

owl.carousel.min.js

951 ms

slick.min.js

slick.min.js

838 ms

video.js

video.js

1010 ms

youtube.js

youtube.js

853 ms

jquery.flexslider.js

jquery.flexslider.js

852 ms

demo.js

demo.js

854 ms

welcome.js

welcome.js

954 ms

collapse.js

collapse.js

836 ms

end_js.js

end_js.js

865 ms

classie.js

classie.js

854 ms

uisearch.js

uisearch.js

856 ms

main.js

main.js

949 ms

Logo_white.svg

Logo_white.svg

380 ms

banner_aurus_new.jpg

banner_aurus_new.jpg

700 ms

280h180_666842ab79e32.jpg

280h180_666842ab79e32.jpg

420 ms

nazarov_smolensk_6662b79e9ea71.png

nazarov_smolensk_6662b79e9ea71.png

704 ms

nami_meteor_main_6661805a1c67b.png

nami_meteor_main_6661805a1c67b.png

567 ms

nvl_6660144d67ad5.png

nvl_6660144d67ad5.png

789 ms

import_62d6c09ebc873.png

import_62d6c09ebc873.png

1198 ms

fiat_639c3ead75f80.jpg

fiat_639c3ead75f80.jpg

700 ms

korr_61adcb395e49d.jpg

korr_61adcb395e49d.jpg

709 ms

prototype1_56fb80ab8a5e8.png

prototype1_56fb80ab8a5e8.png

1124 ms

2_56f50240b8c67.jpg

2_56f50240b8c67.jpg

841 ms

2_0009_standartizatsiyai_i_identifikatsiya_56f8f9142be9c.png

2_0009_standartizatsiyai_i_identifikatsiya_56f8f9142be9c.png

984 ms

4_1_2_56f90029610cc.jpg

4_1_2_56f90029610cc.jpg

850 ms

2_0007_dvigateli1_56f8f9c851c6d.png

2_0007_dvigateli1_56f8f9c851c6d.png

1061 ms

2_0006_lab_ispitaniya_2_56fa2ba133e60.png

2_0006_lab_ispitaniya_2_56fa2ba133e60.png

1343 ms

207h207_5956060c798c1.jpg

207h207_5956060c798c1.jpg

991 ms

2_0004_informatsionnie_i_intellektualnie_sistemi_56f8f64a10881.png

2_0004_informatsionnie_i_intellektualnie_sistemi_56f8f64a10881.png

1128 ms

2_0007_dvigateli_56f8f66fcc71f.png

2_0007_dvigateli_56f8f66fcc71f.png

1344 ms

12_56f502e0976bc.jpg

12_56f502e0976bc.jpg

1198 ms

sertificat2_5649750dec1d4.png

sertificat2_5649750dec1d4.png

1343 ms

3d2_56497524ba9c6.png

3d2_56497524ba9c6.png

1344 ms

diagnostika2_5649752bd10af.png

diagnostika2_5649752bd10af.png

1345 ms

upar_nowm.png

upar_nowm.png

1344 ms

tg.png

tg.png

1383 ms

latolight.ttf

latolight.ttf

1307 ms

latobold.ttf

latobold.ttf

1313 ms

vk11.png

vk11.png

1282 ms

bg-job.jpg

bg-job.jpg

1339 ms

tag.js

tag.js

867 ms

advert.gif

advert.gif

682 ms

sync_cookie_image_decide

sync_cookie_image_decide

144 ms

Accessibility Review

nami.ru accessibility score

34

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.

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

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

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

nami.ru best practices score

67

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

nami.ru SEO score

85

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

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

nami.ru

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