Tools & Wizards About Us
rimeks.ru screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 44

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

rimeks.ru

Шины и диски в Екатеринбурге — Римэкс

Page Load Speed

5.2 sec in total

First Response

1 sec

Resources Loaded

4 sec

Page Rendered

227 ms

rimeks.ru screenshot

About Website

Click here to check amazing Rimeks content for Russia. Otherwise, check out these important facts you probably never knew about rimeks.ru

Сеть сервисмаркетов Римэкс в Екатеринбурге. Лучший выбор шин и дисков для автомобилей от ведущих производителей. Низкие цены. Большой выбор.

Visit rimeks.ru

Key Findings

We analyzed Rimeks.ru page load time and found that the first response time was 1 sec and then it took 4.2 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

rimeks.ru performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.353

31/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

www.rimeks.ru

1008 ms

core.min.css

188 ms

style.css

190 ms

agile_carousel.css

193 ms

style.css

194 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 69% of them (74 requests) were addressed to the original Rimeks.ru, 12% (13 requests) were made to Vk.com and 4% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Rimeks.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (38%)

Content Size

3.7 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rimeks.ru main page is 3.7 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 91.1 kB

  • Original 113.5 kB
  • After minification 107.7 kB
  • After compression 22.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 91.1 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 137.5 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. Rimeks images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 950.3 kB

  • Original 1.2 MB
  • After minification 969.1 kB
  • After compression 281.8 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 950.3 kB or 77% of the original size.

CSS Optimization

-83%

Potential reduce by 230.5 kB

  • Original 276.0 kB
  • After minification 224.1 kB
  • After compression 45.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. Rimeks.ru needs all CSS files to be minified and compressed as it can save up to 230.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (40%)

Requests Now

106

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rimeks. 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 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.rimeks.ru

www.rimeks.ru

1008 ms

core.min.css

core.min.css

188 ms

style.css

style.css

190 ms

agile_carousel.css

agile_carousel.css

193 ms

style.css

style.css

194 ms

style.css

style.css

195 ms

template_styles.css

template_styles.css

197 ms

kernel_main.js

kernel_main.js

471 ms

openapi.js

openapi.js

387 ms

style.css

style.css

467 ms

jquery-ui-1.9.2.custom.css

jquery-ui-1.9.2.custom.css

284 ms

prettyPhoto.css

prettyPhoto.css

286 ms

googlecss.css

googlecss.css

286 ms

newteststyles.css

newteststyles.css

291 ms

template_55bace72084c44ee3ff27a9cf130252c.js

template_55bace72084c44ee3ff27a9cf130252c.js

856 ms

page_a4b7de5b71a6b441763e6c999f4eadeb.js

page_a4b7de5b71a6b441763e6c999f4eadeb.js

382 ms

main.css

main.css

384 ms

ajax_counter.php

ajax_counter.php

348 ms

ba.js

ba.js

156 ms

analytics.js

analytics.js

31 ms

watch.js

watch.js

168 ms

fbic.png

fbic.png

127 ms

vkswitch.png

vkswitch.png

124 ms

headerimg-11.png

headerimg-11.png

127 ms

headerimg-12.png

headerimg-12.png

125 ms

headerimg-10.png

headerimg-10.png

124 ms

headerimg-13.png

headerimg-13.png

125 ms

headerimg-14.png

headerimg-14.png

186 ms

05ba2fc72730de62423014bae44833f9.png

05ba2fc72730de62423014bae44833f9.png

553 ms

daf3debeb81ce099e1c290c285ae9f9f.png

daf3debeb81ce099e1c290c285ae9f9f.png

279 ms

817b110500748d3cac3788ef32cd7d05.png

817b110500748d3cac3788ef32cd7d05.png

474 ms

01c7a0aeb1b68d3ce6709ca6bc631958.gif

01c7a0aeb1b68d3ce6709ca6bc631958.gif

281 ms

cb73edcfce74c35b95ec4ff6a6ae2c67.jpg

cb73edcfce74c35b95ec4ff6a6ae2c67.jpg

1169 ms

0b428e514d5bdb4e923e0d3b20fa5205.png

0b428e514d5bdb4e923e0d3b20fa5205.png

467 ms

tiremainpage2.png

tiremainpage2.png

363 ms

checkgalka.png

checkgalka.png

365 ms

wheelmainpage.png

wheelmainpage.png

460 ms

korzina25.png

korzina25.png

739 ms

loadingmainform.gif

loadingmainform.gif

462 ms

europlan1.png

europlan1.png

550 ms

sova1.png

sova1.png

556 ms

beeline1.png

beeline1.png

557 ms

urao1.png

urao1.png

561 ms

siemens.png

siemens.png

631 ms

arval1.png

arval1.png

645 ms

rmc1.png

rmc1.png

649 ms

close.png

close.png

651 ms

surgutbank.png

surgutbank.png

652 ms

vk.png

vk.png

724 ms

fb.png

fb.png

739 ms

youtube.png

youtube.png

745 ms

collect

collect

73 ms

spamarrowl2.png

spamarrowl2.png

726 ms

spamarrowr2.png

spamarrowr2.png

728 ms

locationfooter.png

locationfooter.png

725 ms

contactsfooter.png

contactsfooter.png

744 ms

letterfooter.png

letterfooter.png

749 ms

kluchfooter.png

kluchfooter.png

752 ms

gcardfooter2.png

gcardfooter2.png

753 ms

sngbandother2.png

sngbandother2.png

819 ms

mobileversionfooter.png

mobileversionfooter.png

837 ms

starfooter.png

starfooter.png

842 ms

echo.png

echo.png

845 ms

control.png

control.png

845 ms

listarrow.png

listarrow.png

903 ms

bx_stat

bx_stat

200 ms

watch.js

watch.js

467 ms

1bc5eaeccdff9b4bdd3dd0a9ec930c76.png

1bc5eaeccdff9b4bdd3dd0a9ec930c76.png

1058 ms

rubznak.png

rubznak.png

782 ms

948ebd331845c59a0833dde2b459e341.png

948ebd331845c59a0833dde2b459e341.png

1063 ms

e6fa64b3ead1e661e3c99fe87415979e.png

e6fa64b3ead1e661e3c99fe87415979e.png

872 ms

0b66b890465a31457b2a04893ee7e3aa.png

0b66b890465a31457b2a04893ee7e3aa.png

835 ms

36266d31c53031655b13988286d2043a.png

36266d31c53031655b13988286d2043a.png

681 ms

06c3f3def5ce5c626cdcfba720c52b85.png

06c3f3def5ce5c626cdcfba720c52b85.png

867 ms

70ebdc7a13a8cea5e354a8d1b1217cfd.png

70ebdc7a13a8cea5e354a8d1b1217cfd.png

793 ms

d9f971b78e22f47078b335b717b4987b.png

d9f971b78e22f47078b335b717b4987b.png

924 ms

upload.gif

upload.gif

129 ms

widget_community.php

widget_community.php

295 ms

842eff04f47c498dd723d0a63e222737.png

842eff04f47c498dd723d0a63e222737.png

967 ms

7859e04910add2ba89adf00faccb5895.png

7859e04910add2ba89adf00faccb5895.png

872 ms

redpodloshka.png

redpodloshka.png

794 ms

rubznakwhite.png

rubznakwhite.png

863 ms

control_current.png

control_current.png

864 ms

advert.gif

advert.gif

91 ms

getCityList.php

getCityList.php

904 ms

loader_nav19127_3.js

loader_nav19127_3.js

132 ms

lite.css

lite.css

134 ms

lite.js

lite.js

512 ms

lang3_0.js

lang3_0.js

258 ms

widget_community.css

widget_community.css

264 ms

xdm.js

xdm.js

262 ms

al_community.js

al_community.js

263 ms

1

1

92 ms

aiJBjUZ3guE.jpg

aiJBjUZ3guE.jpg

388 ms

Jrm8Wjjogds.jpg

Jrm8Wjjogds.jpg

383 ms

-Rgo0lSB3z4.jpg

-Rgo0lSB3z4.jpg

404 ms

QXO_0yIGl6I.jpg

QXO_0yIGl6I.jpg

386 ms

KQIuZw2ZbqI.jpg

KQIuZw2ZbqI.jpg

261 ms

xmWhHEBQp-U.jpg

xmWhHEBQp-U.jpg

387 ms

l9ZAxHbb4_E.jpg

l9ZAxHbb4_E.jpg

269 ms

rnGa2hWtrYM.jpg

rnGa2hWtrYM.jpg

404 ms

TEpW2TvxgZc.jpg

TEpW2TvxgZc.jpg

415 ms

e_13086663.jpg

e_13086663.jpg

402 ms

_eG_rwszYeA.jpg

_eG_rwszYeA.jpg

398 ms

sSQzZVIeCLw.jpg

sSQzZVIeCLw.jpg

397 ms

camera_50.png

camera_50.png

130 ms

deactivated_50.png

deactivated_50.png

131 ms

w_logo.png

w_logo.png

134 ms

Accessibility Review

rimeks.ru accessibility score

44

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Form elements do not have associated labels

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

rimeks.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 Rimeks.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 Rimeks.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

rimeks.ru

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