3.9 sec in total
501 ms
3.2 sec
259 ms
Welcome to printrus.ru homepage info - get ready to check Printrus best content for Russia right away, or after learning these important things about printrus.ru
Типография в Санкт-Петербурге - цены на печать полиграфии. Онлайн заказ в типографии. Листовки, буклеты, каталоги, визитки, наклейки, календари - всё это вы можете с легкостью заказать в нашей офсетно...
Visit printrus.ruWe analyzed Printrus.ru page load time and found that the first response time was 501 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
printrus.ru performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value5.8 s
15/100
25%
Value6.2 s
43/100
10%
Value770 ms
38/100
30%
Value0.172
69/100
15%
Value8.8 s
36/100
10%
501 ms
751 ms
64 ms
107 ms
38 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 79% of them (48 requests) were addressed to the original Printrus.ru, 10% (6 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Printrus.ru.
Page size can be reduced by 142.9 kB (9%)
1.5 MB
1.4 MB
In fact, the total size of Printrus.ru main page is 1.5 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. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 79.7 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 12.5 kB, which is 13% 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 79.7 kB or 83% of the original size.
Potential reduce by 41.1 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. Printrus images are well optimized though.
Potential reduce by 8.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.
Potential reduce by 13.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. Printrus.ru needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 15% of the original size.
Number of requests can be reduced by 36 (73%)
49
13
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Printrus. 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.
printrus.ru
501 ms
printrus.ru
751 ms
gtm.js
64 ms
js
107 ms
css
38 ms
style.css
127 ms
content.css
252 ms
normalize.css
334 ms
font-awesome.css
336 ms
material-design.css
338 ms
bootstrap.css
464 ms
allvmscripts.css
349 ms
virtuemart.css
377 ms
animate.css
453 ms
template.css
565 ms
bannersblock.css
456 ms
superfish.css
475 ms
slicknav.css
510 ms
contactus_lightbox.css
570 ms
jquery.min.js
686 ms
jquery-noconflict.js
586 ms
jquery-migrate.min.js
596 ms
bootstrap.min.js
636 ms
core.js
684 ms
punycode.js
703 ms
validate.js
711 ms
superfish.js
719 ms
hoverIntent.js
762 ms
sftouchscreen.js
803 ms
jquery.slicknav.js
804 ms
contactus_common.js
802 ms
contactus_lightbox.js
833 ms
jquery.ui.core.min.js
885 ms
tm-stick-up.js
899 ms
scrollUp.min.js
970 ms
scriptsAll.js
1035 ms
wow.js
971 ms
scripts.js
1007 ms
all.css
27 ms
tag.js
980 ms
logo_141021_2.png
173 ms
Listovki_smaller2.jpg
404 ms
byklet_smaller2.jpg
515 ms
catalog-2-2.jpg
314 ms
vizitki_smaller2.jpg
510 ms
kalendari%20(1).jpg
535 ms
bloknoti.jpg
427 ms
Nakleyki_smaller.jpg
540 ms
blanki_smaller2.jpg
526 ms
converts_smaller2.jpg
649 ms
korobki_samller2.jpg
750 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
86 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
87 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
122 ms
KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf
123 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
136 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
135 ms
fa-solid-900.woff
29 ms
fa-regular-400.woff
84 ms
fontawesome-webfont.woff
688 ms
material-design.woff
507 ms
printrus.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Form elements do not have associated labels
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.
printrus.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
printrus.ru SEO score
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
![]()
RU
![]()
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Printrus.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 Printrus.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.
printrus.ru
Open Graph description is not detected on the main page of Printrus. 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: