4 sec in total
496 ms
3.3 sec
223 ms
Visit poshk.ru now to see the best up-to-date Poshk content for Russia and also check out these interesting facts you probably never knew about poshk.ru
ПОШК РУ интернет-магазин, у нас можно купить недорого шины и диски в Москве на легковой автомобиль, внедорожник, грузовик или спецтехнику
Visit poshk.ruWe analyzed Poshk.ru page load time and found that the first response time was 496 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
poshk.ru performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value6.1 s
12/100
25%
Value10.2 s
9/100
10%
Value2,320 ms
5/100
30%
Value0.002
100/100
15%
Value15.5 s
7/100
10%
496 ms
797 ms
44 ms
88 ms
1036 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 76% of them (47 requests) were addressed to the original Poshk.ru, 6% (4 requests) were made to Clients.streamwood.ru and 5% (3 requests) were made to Maps.api.2gis.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cdn.callibri.ru.
Page size can be reduced by 380.6 kB (24%)
1.6 MB
1.2 MB
In fact, the total size of Poshk.ru main page is 1.6 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. 45% of websites need less resources to load. Images take 870.6 kB which makes up the majority of the site volume.
Potential reduce by 181.8 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 48.3 kB, which is 23% 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 181.8 kB or 85% of the original size.
Potential reduce by 193.6 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. Obviously, Poshk needs image optimization as it can save up to 193.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 3.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.4 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. Poshk.ru has all CSS files already compressed.
Number of requests can be reduced by 14 (24%)
58
44
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poshk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
poshk.ru
496 ms
poshk.ru
797 ms
gtm.js
44 ms
js
88 ms
code
1036 ms
tag.js
890 ms
loader.js
677 ms
96851edcebba2efa362082f6af77256411118722714.css
247 ms
owl.carousel.css
356 ms
owl.theme.css
358 ms
e8fbbc51dfc2074b3286ab80ca271aeb12555435784.js
488 ms
callibri.js
1372 ms
openapi.c340c125c61ec5745ebb2a98626e46ab.js
399 ms
734 ms
close.png
164 ms
loading.gif
121 ms
prev.png
254 ms
next.png
255 ms
footer-background.svg
265 ms
phys.png
265 ms
phys-orders.png
264 ms
logo.png
265 ms
phys-cart.png
387 ms
0502c823f81e527284fa1d4820c2b99d74d8d915_1000x300.jpg
891 ms
filter_tires_active.svg
385 ms
filter-disks-active.svg
381 ms
filter-cameras-active.svg
384 ms
legk.png
505 ms
offroad.png
499 ms
legkogruz.png
500 ms
gruz.png
501 ms
selskohoz.png
505 ms
specshina.png
619 ms
legk-disk.png
617 ms
gruz-disk.png
618 ms
selskohoz-disk.png
626 ms
bg-slider.png
1247 ms
altai_F-35_75x100.jpg
733 ms
NORTEC_IM-14_75x100.jpg
734 ms
Nortec_TA-02_75x100.jpg
734 ms
altai_altaishina_M-145_75x100.jpg
746 ms
altai_altaishina_K-84_75x100.jpg
850 ms
altai_V-105A_75x100.jpg
851 ms
Forward-Prof_156_75x100.jpg
852 ms
Forward_Professional_301_75x100.jpg
867 ms
safari_540_75x100.jpg
969 ms
Forward_Safari_510_75x100.jpg
970 ms
1.gif
970 ms
2.jpg
988 ms
3.gif
1022 ms
rtrg
148 ms
Rubik-Regular.ttf
1092 ms
fontawesome-webfont.woff
971 ms
4.jpg
860 ms
5.jpg
860 ms
vk-icon.png
878 ms
sw.js
460 ms
sw.css
381 ms
advert.gif
330 ms
149 ms
sync_cookie_image_decide
158 ms
115 ms
poshk.ru accessibility score
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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
poshk.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
poshk.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
RU
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poshk.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 Poshk.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.
poshk.ru
Open Graph description is not detected on the main page of Poshk. 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: