Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

microbus.su

(831) 429-02-99 Купить запчасти на автобусы ПАЗ, ЛИАЗ, грузовые автомобили в Нижнем Новгороде - ООО СВИТА-НН

Page Load Speed

5.5 sec in total

First Response

416 ms

Resources Loaded

4.9 sec

Page Rendered

226 ms

microbus.su screenshot

About Website

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

Каталог с ценами на запчасти для автобусов ПАЗ, ЛИАЗ, а также производителей запчастей к ним КААЗ, РЗАА, СААЗ, ЗМЗ, ММЗ и т. д. Накладки на тормоза, колодки, амортизаторы и др.

Visit microbus.su

Key Findings

We analyzed Microbus.su page load time and found that the first response time was 416 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

microbus.su performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value2,010 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

microbus.su

416 ms

microbus.su

657 ms

highslide.min.css

144 ms

highslide.packed.js

413 ms

flowplayer-3.2.9.min.js

366 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 37% of them (33 requests) were addressed to the original Microbus.su, 16% (14 requests) were made to Tpc.googlesyndication.com and 12% (11 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (969 ms) belongs to the original domain Microbus.su.

Page Optimization Overview & Recommendations

Page size can be reduced by 347.9 kB (24%)

Content Size

1.4 MB

After Optimization

1.1 MB

In fact, the total size of Microbus.su main page is 1.4 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. 50% of websites need less resources to load. Javascripts take 788.1 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 24.6 kB

  • Original 33.2 kB
  • After minification 30.4 kB
  • After compression 8.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 24.6 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 25.7 kB

  • Original 612.8 kB
  • After minification 587.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. Microbus images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 297.6 kB

  • Original 788.1 kB
  • After minification 788.1 kB
  • After compression 490.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 297.6 kB or 38% of the original size.

Requests Breakdown

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

Requests Now

82

After Optimization

31

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

Accessibility Review

microbus.su accessibility score

96

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

Links do not have a discernible name

Best Practices

microbus.su best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

microbus.su SEO score

77

Search Engine Optimization Advices

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 Microbus.su 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 Microbus.su 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

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