Tools & Wizards About Us
printsburg.ru screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

printsburg.ru

Printsburg.ru

Page Load Speed

8.4 sec in total

First Response

1.1 sec

Resources Loaded

6.4 sec

Page Rendered

920 ms

printsburg.ru screenshot

About Website

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

Сеть полиграфический центров Printsburg.ru

Visit printsburg.ru

Key Findings

We analyzed Printsburg.ru page load time and found that the first response time was 1.1 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

printsburg.ru performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

printsburg.ru

1066 ms

css

88 ms

kernel_main.css

284 ms

page_0fe5b3b19492d682fb4aaba89380067c.css

439 ms

template_7a2b0e629fcd44ae3cf0b4500080ca83.css

684 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 55% of them (56 requests) were addressed to the original Printsburg.ru, 26% (27 requests) were made to Old.printsburg.ru and 5% (5 requests) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Printsburg.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (43%)

Content Size

3.8 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 168.2 kB

  • Original 204.6 kB
  • After minification 188.5 kB
  • After compression 36.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 168.2 kB or 82% of the original size.

Image Optimization

-19%

Potential reduce by 431.8 kB

  • Original 2.3 MB
  • After minification 1.9 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. Obviously, Printsburg needs image optimization as it can save up to 431.8 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 500.9 kB

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

CSS Optimization

-85%

Potential reduce by 538.9 kB

  • Original 634.6 kB
  • After minification 574.7 kB
  • After compression 95.7 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. Printsburg.ru needs all CSS files to be minified and compressed as it can save up to 538.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (39%)

Requests Now

92

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

printsburg.ru

printsburg.ru

1066 ms

css

css

88 ms

kernel_main.css

kernel_main.css

284 ms

page_0fe5b3b19492d682fb4aaba89380067c.css

page_0fe5b3b19492d682fb4aaba89380067c.css

439 ms

template_7a2b0e629fcd44ae3cf0b4500080ca83.css

template_7a2b0e629fcd44ae3cf0b4500080ca83.css

684 ms

slot

slot

1128 ms

logo.png

logo.png

204 ms

cc1c0acd00b139cdb6872cda35f8443f.jpg

cc1c0acd00b139cdb6872cda35f8443f.jpg

1103 ms

bdd1f4dbe2f6021fdea007b7abd4c16f.png

bdd1f4dbe2f6021fdea007b7abd4c16f.png

1124 ms

skachannye-fai_ly.png

skachannye-fai_ly.png

329 ms

gruzovik.png

gruzovik.png

1133 ms

9df7cccafa69487d5f3f08f3cde2c26d.jpg

9df7cccafa69487d5f3f08f3cde2c26d.jpg

1124 ms

8cc74a24c74578d1b522f5718af81880.png

8cc74a24c74578d1b522f5718af81880.png

1128 ms

1c5ed60bedba93ee1da267bb426d0a33.png

1c5ed60bedba93ee1da267bb426d0a33.png

1111 ms

62b61d5d891ac56583dd43edfe27f9aa.png

62b61d5d891ac56583dd43edfe27f9aa.png

1733 ms

82eba6412fa9e93e61e0c7e6dde2ca0f.jpg

82eba6412fa9e93e61e0c7e6dde2ca0f.jpg

2788 ms

624bab3244f67315adb5499501076a3d.png

624bab3244f67315adb5499501076a3d.png

1389 ms

cfcc141e01087ff837f1140aaa2d7ccb.png

cfcc141e01087ff837f1140aaa2d7ccb.png

1129 ms

981ccbb38186e702708c06d6916ae9d6.png

981ccbb38186e702708c06d6916ae9d6.png

2073 ms

00e5cfc4aa65bb24fd446196cb58c106.png

00e5cfc4aa65bb24fd446196cb58c106.png

1238 ms

4c02fc5538f456e25b7f630f89d37526.png

4c02fc5538f456e25b7f630f89d37526.png

1245 ms

e609c8cff9133b839277e2d018e592c2.png

e609c8cff9133b839277e2d018e592c2.png

1462 ms

efe1d4b448f4d9664ffded60cbe33090.png

efe1d4b448f4d9664ffded60cbe33090.png

1462 ms

68fb4413f6e70d36a5f25a69465322ee.png

68fb4413f6e70d36a5f25a69465322ee.png

1564 ms

ee27e087d257b4cd1be82d309511b992.png

ee27e087d257b4cd1be82d309511b992.png

1614 ms

818f2da41626a0aa32a4911251c9b247.png

818f2da41626a0aa32a4911251c9b247.png

1625 ms

850de69749d8912c48fe659cf521f5cf.png

850de69749d8912c48fe659cf521f5cf.png

1728 ms

db3fde1721cf182ae0ee0205afd31c2d.png

db3fde1721cf182ae0ee0205afd31c2d.png

1766 ms

563653499c3d99a7a668832d009e27b5.png

563653499c3d99a7a668832d009e27b5.png

1780 ms

23f3c0e142f0c7d0db14cc044f047ed7.png

23f3c0e142f0c7d0db14cc044f047ed7.png

1861 ms

20c2788893282e88d3147d1eac777d72.png

20c2788893282e88d3147d1eac777d72.png

3266 ms

8576ce87e5957d1155414c76173257c4.png

8576ce87e5957d1155414c76173257c4.png

1934 ms

a9395d321d31c162ff331e07cef70894.png

a9395d321d31c162ff331e07cef70894.png

1945 ms

f91850f630fb3a29b96dc7228dbbceb9.png

f91850f630fb3a29b96dc7228dbbceb9.png

2023 ms

2937a67496b6a004c2d776cdc3bba1dc.png

2937a67496b6a004c2d776cdc3bba1dc.png

2111 ms

e3a850806d6e88418481df962bee7ea2.png

e3a850806d6e88418481df962bee7ea2.png

2122 ms

750fff6903cf47a56c8b8f3b44654a0f.png

750fff6903cf47a56c8b8f3b44654a0f.png

2177 ms

kernel_main.js

kernel_main.js

2362 ms

share.js

share.js

82 ms

ajax.min.js

ajax.min.js

2231 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

2125 ms

template_b8cd76bd58f8846e7d2e638da1b506de.js

template_b8cd76bd58f8846e7d2e638da1b506de.js

2717 ms

page_2ecbd40d711133b396d3ad3372e500e7.js

page_2ecbd40d711133b396d3ad3372e500e7.js

2187 ms

html5shiv.js

html5shiv.js

2156 ms

respond.min.js

respond.min.js

2431 ms

jquery.formstyler.min.js

jquery.formstyler.min.js

1508 ms

spring-top.png

spring-top.png

2295 ms

slot.css

slot.css

216 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

522 ms

jquery.corner.js

jquery.corner.js

417 ms

jquery.validate.min.js

jquery.validate.min.js

417 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

416 ms

slot.js

slot.js

416 ms

cart.png

cart.png

1652 ms

footer_bg.png

footer_bg.png

2143 ms

metro-icon.png

metro-icon.png

2142 ms

socialsprites.png

socialsprites.png

2148 ms

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf

144 ms

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf

200 ms

MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf

MTP_ySUJH_bn48VBG8sNSvOEPOIfcPv-fZ-WyMUtx48.ttf

268 ms

k3k702ZOKiLJc3WVjuplzPOEPOIfcPv-fZ-WyMUtx48.ttf

k3k702ZOKiLJc3WVjuplzPOEPOIfcPv-fZ-WyMUtx48.ttf

329 ms

EInbV5DfGHOiMmvb1Xr-hvOEPOIfcPv-fZ-WyMUtx48.ttf

EInbV5DfGHOiMmvb1Xr-hvOEPOIfcPv-fZ-WyMUtx48.ttf

328 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2155 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2798 ms

screen.png

screen.png

187 ms

icon1.png

icon1.png

649 ms

icon1-move.png

icon1-move.png

418 ms

icon2.png

icon2.png

192 ms

icon2-move.png

icon2-move.png

192 ms

icon3.png

icon3.png

647 ms

icon3-move.png

icon3-move.png

379 ms

icon4.png

icon4.png

409 ms

icon4-move.png

icon4-move.png

377 ms

icon5.png

icon5.png

545 ms

icon5-move.png

icon5-move.png

544 ms

icon6.png

icon6.png

563 ms

icon6-move.png

icon6-move.png

569 ms

icon7.png

icon7.png

787 ms

icon7-move.png

icon7-move.png

788 ms

icon8.png

icon8.png

788 ms

icon8-move.png

icon8-move.png

789 ms

icon9.png

icon9.png

835 ms

icon9-move.png

icon9-move.png

833 ms

lever.png

lever.png

903 ms

api.min.js

api.min.js

1529 ms

ba.js

ba.js

277 ms

watch.js

watch.js

499 ms

bx_stat

bx_stat

540 ms

b-share-form-button.png

b-share-form-button.png

119 ms

watch.js

watch.js

113 ms

favorable_spring.jpg

favorable_spring.jpg

1425 ms

loader.gif

loader.gif

354 ms

bullet.png

bullet.png

352 ms

large_left.png

large_left.png

359 ms

large_right.png

large_right.png

346 ms

bx_loader.gif

bx_loader.gif

347 ms

b-share-form-button_share__icon.png

b-share-form-button_share__icon.png

93 ms

b-share-icon.png

b-share-icon.png

79 ms

b-share-popup_down__tail.png

b-share-popup_down__tail.png

82 ms

jsconnect

jsconnect

710 ms

1441725145766-lodtt2q0.png

1441725145766-lodtt2q0.png

488 ms

events

events

418 ms

Accessibility Review

printsburg.ru accessibility score

93

Accessibility Issues

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.

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

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

printsburg.ru SEO score

89

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Printsburg.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Printsburg.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

printsburg.ru

Open Graph data is detected on the main page of Printsburg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: