Tools & Wizards About Us
spb.zapchasti-poisk.ru screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 95

    SEO

    Google-friendlier than
    91% of websites

spb.zapchasti-poisk.ru

Запчасти-Поиск: Новые и бу запчасти, магазины автозапчастей и разборки

Page Load Speed

5 sec in total

First Response

1.3 sec

Resources Loaded

3.4 sec

Page Rendered

280 ms

spb.zapchasti-poisk.ru screenshot

About Website

Welcome to spb.zapchasti-poisk.ru homepage info - get ready to check Spb Zapchasti Poisk best content for Russia right away, or after learning these important things about spb.zapchasti-poisk.ru

Запчасти-Поиск: Новый способ дешево купить новые и бу запчасти. Разборки и магазины автозапчастей. Санкт-Петербург

Visit spb.zapchasti-poisk.ru

Key Findings

We analyzed Spb.zapchasti-poisk.ru page load time and found that the first response time was 1.3 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

spb.zapchasti-poisk.ru performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

84/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

spb.zapchasti-poisk.ru

1254 ms

style.min.css

583 ms

jquery.min.js

42 ms

jquery-ui.min.js

996 ms

polyfiller.js

379 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 25% of them (8 requests) were addressed to the original Spb.zapchasti-poisk.ru, 41% (13 requests) were made to Zapchasti-poisk.ru and 9% (3 requests) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Spb.zapchasti-poisk.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 89.7 kB (45%)

Content Size

199.7 kB

After Optimization

109.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spb.zapchasti-poisk.ru main page is 199.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 61.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 49.2 kB

  • Original 61.6 kB
  • After minification 60.0 kB
  • After compression 12.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 49.2 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 302 B

  • Original 42.7 kB
  • After minification 42.4 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. Spb Zapchasti Poisk images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 1.6 kB

  • Original 43.9 kB
  • After minification 43.9 kB
  • After compression 42.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

-75%

Potential reduce by 38.6 kB

  • Original 51.5 kB
  • After minification 51.5 kB
  • After compression 12.9 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. Spb.zapchasti-poisk.ru needs all CSS files to be minified and compressed as it can save up to 38.6 kB or 75% of the original size.

Requests Breakdown

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

Requests Now

30

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

spb.zapchasti-poisk.ru

spb.zapchasti-poisk.ru

1254 ms

style.min.css

style.min.css

583 ms

jquery.min.js

jquery.min.js

42 ms

jquery-ui.min.js

jquery-ui.min.js

996 ms

polyfiller.js

polyfiller.js

379 ms

libtools.min.js

libtools.min.js

995 ms

share.js

share.js

59 ms

fp.min.js

fp.min.js

863 ms

watch.js

watch.js

1 ms

shim-ext.css

shim-ext.css

163 ms

3.js

3.js

519 ms

form-shim-extend.js

form-shim-extend.js

325 ms

17.js

17.js

670 ms

logo.png

logo.png

168 ms

bg.png

bg.png

173 ms

home2q.png

home2q.png

173 ms

sequence.png

sequence.png

379 ms

send-request.png

send-request.png

380 ms

popup.png

popup.png

381 ms

tabs_nav.png

tabs_nav.png

381 ms

list-logos.png

list-logos.png

380 ms

findparts

findparts

201 ms

ya-share-cnt.html

ya-share-cnt.html

91 ms

tabs_nav_active.png

tabs_nav_active.png

313 ms

b-share-icon.png

b-share-icon.png

108 ms

b-share_counter_large.png

b-share_counter_large.png

186 ms

share_count

share_count

808 ms

816 ms

fql.query

fql.query

414 ms

dk

dk

777 ms

share.php

share.php

643 ms

formcfg-ru.js

formcfg-ru.js

162 ms

Accessibility Review

spb.zapchasti-poisk.ru accessibility score

98

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

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

Best Practices

spb.zapchasti-poisk.ru best practices score

75

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

Page has valid source maps

SEO Factors

spb.zapchasti-poisk.ru SEO score

95

Search Engine Optimization Advices

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

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spb.zapchasti-poisk.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 Spb.zapchasti-poisk.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

spb.zapchasti-poisk.ru

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