Tools & Wizards About Us
rantos.ru screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

rantos.ru

Металлическая сетка, производство сетки — Компания ООО «РАНТОС»

Page Load Speed

8.9 sec in total

First Response

728 ms

Resources Loaded

7.5 sec

Page Rendered

664 ms

rantos.ru screenshot

About Website

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

Компания ООО «РАНТОС» - производство сетки сварной металлической и каркасов по размерам заказчика, нарубка проволоки, катанки и бухтовой арматуры. Звоните: +7 (495) 651-9160, +7 (926) 908-6121

Visit rantos.ru

Key Findings

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

Performance Metrics

rantos.ru performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,900 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.76

6/100

15%

TTI (Time to Interactive)

Value26.7 s

0/100

10%

Network Requests Diagram

rantos.ru

728 ms

www.rantos.ru

810 ms

bootstrap-reboot.css

141 ms

bootstrap-grid.css

283 ms

owl.carousel.css

393 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 58% of them (72 requests) were addressed to the original Rantos.ru, 23% (28 requests) were made to Web.redhelper.ru and 4% (5 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Rantos.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 758.3 kB (11%)

Content Size

7.2 MB

After Optimization

6.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 182.0 kB

  • Original 220.4 kB
  • After minification 214.4 kB
  • After compression 38.4 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 182.0 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 464.1 kB

  • Original 6.3 MB
  • After minification 5.8 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. Rantos images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 97.0 kB

  • Original 273.9 kB
  • After minification 273.9 kB
  • After compression 176.9 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 97.0 kB or 35% of the original size.

CSS Optimization

-4%

Potential reduce by 15.3 kB

  • Original 408.1 kB
  • After minification 408.1 kB
  • After compression 392.8 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. Rantos.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 55 (51%)

Requests Now

107

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rantos.ru

rantos.ru

728 ms

www.rantos.ru

www.rantos.ru

810 ms

bootstrap-reboot.css

bootstrap-reboot.css

141 ms

bootstrap-grid.css

bootstrap-grid.css

283 ms

owl.carousel.css

owl.carousel.css

393 ms

owl.theme.default.css

owl.theme.default.css

396 ms

slick.css

slick.css

40 ms

style.css

style.css

424 ms

media.css

media.css

532 ms

default.css

default.css

524 ms

top100.jcn

top100.jcn

1578 ms

js

js

72 ms

jquery.js

jquery.js

658 ms

786 ms

owl.carousel.js

owl.carousel.js

703 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

40 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

50 ms

slick.min.js

slick.min.js

40 ms

main.js

main.js

921 ms

script.js

script.js

651 ms

default.js

default.js

686 ms

stanok-proizvodstvo-setki.jpg

stanok-proizvodstvo-setki.jpg

922 ms

rezka-setki.jpg

rezka-setki.jpg

921 ms

stylesheet.css

stylesheet.css

437 ms

jquery.jgrowl.min.css

jquery.jgrowl.min.css

268 ms

banner-88x31-rambler-gray2.gif

banner-88x31-rambler-gray2.gif

526 ms

logo.png

logo.png

141 ms

percent.png

percent.png

132 ms

mail.png

mail.png

194 ms

phone.png

phone.png

232 ms

question.png

question.png

214 ms

search-bgdark.png

search-bgdark.png

177 ms

slide1-1.jpg

slide1-1.jpg

1041 ms

slide1-2.jpg

slide1-2.jpg

976 ms

%D0%AD%D0%BB%D0%B5%D0%BA%D1%82%D1%80%D0%BE%D0%B4%D1%8B%20(%D1%81%D1%82%D0%B5%D1%80%D0%B6%D0%BD%D0%B8)%20%D0%B8%D0%B7%20%D0%BF%D1%80%D0%BE%D0%B2%D0%BE%D0%BE%D0%BA%D1%82%20%D0%92%D1%80-1.png

%D0%AD%D0%BB%D0%B5%D0%BA%D1%82%D1%80%D0%BE%D0%B4%D1%8B%20(%D1%81%D1%82%D0%B5%D1%80%D0%B6%D0%BD%D0%B8)%20%D0%B8%D0%B7%20%D0%BF%D1%80%D0%BE%D0%B2%D0%BE%D0%BE%D0%BA%D1%82%20%D0%92%D1%80-1.png

955 ms

setka_svarnaya.png

setka_svarnaya.png

1250 ms

setka_tkanaya.png

setka_tkanaya.png

737 ms

setka_pletenaya.png

setka_pletenaya.png

1148 ms

setka_kruchenaya.png

setka_kruchenaya.png

905 ms

setka_prosechno-vitjazhnaya.png

setka_prosechno-vitjazhnaya.png

1101 ms

scb-gib_2.jpg

scb-gib_2.jpg

1088 ms

provoloka.png

provoloka.png

1120 ms

armatura.png

armatura.png

1173 ms

katanka.png

katanka.png

1219 ms

setka.webp

setka.webp

1302 ms

katanka-18.jpg

katanka-18.jpg

1398 ms

setka-svarnaya-100x100x6.jpg

setka-svarnaya-100x100x6.jpg

1610 ms

address.png

address.png

1305 ms

phone2.png

phone2.png

1350 ms

mail2.png

mail2.png

1478 ms

PFDinDisplayPro-Regular.woff

PFDinDisplayPro-Regular.woff

1459 ms

PFDinDisplayPro-Medium.woff

PFDinDisplayPro-Medium.woff

1386 ms

PFDinDisplayPro-Light.woff

PFDinDisplayPro-Light.woff

1431 ms

PFDinDisplayPro-Thin.woff

PFDinDisplayPro-Thin.woff

1487 ms

PFDinDisplayPro-Bold.woff

PFDinDisplayPro-Bold.woff

1545 ms

PFDinDisplayPro-Black.woff

PFDinDisplayPro-Black.woff

2062 ms

banner-88x31-rambler-gray2.gif

banner-88x31-rambler-gray2.gif

128 ms

watch.js

watch.js

0 ms

tag.js

tag.js

855 ms

hit

hit

517 ms

watch.js

watch.js

0 ms

full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js

full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js

1754 ms

jquery.form.min.js

jquery.form.min.js

846 ms

jquery.jgrowl.min.js

jquery.jgrowl.min.js

951 ms

counter2

counter2

569 ms

main.js

main.js

501 ms

start

start

407 ms

1.png

1.png

142 ms

2.png

2.png

133 ms

3.png

3.png

232 ms

4.png

4.png

233 ms

5.png

5.png

133 ms

6.png

6.png

267 ms

7.png

7.png

267 ms

8.png

8.png

281 ms

mechel.jpg

mechel.jpg

463 ms

MMK-metiz.jpg

MMK-metiz.jpg

472 ms

NLMK.jpg

NLMK.jpg

399 ms

MMK-TD.jpg

MMK-TD.jpg

397 ms

nlmk_metiz-rus.jpg

nlmk_metiz-rus.jpg

422 ms

Tula-stal%20TD.jpg

Tula-stal%20TD.jpg

768 ms

Tula%D0%A1herMet.jpg

Tula%D0%A1herMet.jpg

530 ms

avtoalians.jpg

avtoalians.jpg

531 ms

BVB-Alians.jpg

BVB-Alians.jpg

563 ms

mdm-group.png

mdm-group.png

693 ms

metallservis.jpg

metallservis.jpg

684 ms

mzjbi.jpg

mzjbi.jpg

662 ms

Stalenergo96.jpg

Stalenergo96.jpg

663 ms

Stroy-resurs-TD.jpg

Stroy-resurs-TD.jpg

709 ms

Vash-Dom.jpg

Vash-Dom.jpg

800 ms

advert.gif

advert.gif

510 ms

main.js

main.js

679 ms

1

1

150 ms

jquery-new.min.js

jquery-new.min.js

257 ms

rantosru

rantosru

509 ms

grab.cur

grab.cur

156 ms

grabbing.cur

grabbing.cur

182 ms

help.cur

help.cur

324 ms

zoom_in.cur

zoom_in.cur

396 ms

badge_mt1.svg

badge_mt1.svg

720 ms

material.css

material.css

378 ms

Ava_default.svg

Ava_default.svg

140 ms

136 ms

23849272

23849272

144 ms

jquery.min.js

jquery.min.js

372 ms

main.js

main.js

780 ms

common.css

common.css

253 ms

606365

606365

134 ms

connector.html

connector.html

126 ms

connector.html

connector.html

633 ms

connector-frame.css

connector-frame.css

396 ms

connector.js

connector.js

358 ms

icon-close.png

icon-close.png

169 ms

icon_time_picker_close.png

icon_time_picker_close.png

296 ms

warning-top.png

warning-top.png

294 ms

warning-mid.png

warning-mid.png

376 ms

warning-bottom.png

warning-bottom.png

382 ms

copyright-bottom-p1.png

copyright-bottom-p1.png

420 ms

copyright-bottom-p3.png

copyright-bottom-p3.png

442 ms

v42r9LwwxUv8H9mNOJwAAAAFVgBmSAAA=

v42r9LwwxUv8H9mNOJwAAAAFVgBmSAAA=

3 ms

mail.svg

mail.svg

403 ms

material.css

material.css

1285 ms

flags.png

flags.png

147 ms

connector-popup.css

connector-popup.css

1010 ms

Accessibility Review

rantos.ru accessibility score

81

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

rantos.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

rantos.ru SEO score

81

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

rantos.ru

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