Tools & Wizards About Us
prokazin.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

prokazin.com

Саженцы плодовых и ягодных культур| Проказин Леонид Ильич частный плодопитомник

Page Load Speed

3.3 sec in total

First Response

704 ms

Resources Loaded

2.4 sec

Page Rendered

227 ms

prokazin.com screenshot

About Website

Click here to check amazing Prokazin content for Ukraine. Otherwise, check out these important facts you probably never knew about prokazin.com

Саженцы плодовых деревьев и кустарников новые и проверенные временем сорта. Описание сортов, купить саженцы в частном питомнике Проказина Леонида Ильича

Visit prokazin.com

Key Findings

We analyzed Prokazin.com page load time and found that the first response time was 704 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

prokazin.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

prokazin.com

704 ms

prettyPhoto.css

119 ms

rokbox.css

241 ms

menu-e2aac4fac98543256f0dcee3b86d39cd.css

238 ms

grid-responsive.css

244 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 98% of them (60 requests) were addressed to the original Prokazin.com, 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (940 ms) belongs to the original domain Prokazin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.3 kB (13%)

Content Size

533.6 kB

After Optimization

465.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 40.8 kB

  • Original 52.2 kB
  • After minification 46.1 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 6.0 kB, which is 12% 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 40.8 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 6.4 kB

  • Original 203.6 kB
  • After minification 197.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. Prokazin images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 14.6 kB

  • Original 205.6 kB
  • After minification 205.1 kB
  • After compression 191.0 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

-9%

Potential reduce by 6.6 kB

  • Original 72.2 kB
  • After minification 71.3 kB
  • After compression 65.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. Prokazin.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (64%)

Requests Now

58

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prokazin.com

prokazin.com

704 ms

prettyPhoto.css

prettyPhoto.css

119 ms

rokbox.css

rokbox.css

241 ms

menu-e2aac4fac98543256f0dcee3b86d39cd.css

menu-e2aac4fac98543256f0dcee3b86d39cd.css

238 ms

grid-responsive.css

grid-responsive.css

244 ms

bootstrap.css

bootstrap.css

353 ms

master-702fcc67caa36df244bbdd9931335f1a.css

master-702fcc67caa36df244bbdd9931335f1a.css

364 ms

mediaqueries.css

mediaqueries.css

235 ms

rokajaxsearch.css

rokajaxsearch.css

362 ms

rokajaxsearch-theme.css

rokajaxsearch-theme.css

361 ms

style.css

style.css

363 ms

ebrlatestentries.css

ebrlatestentries.css

372 ms

mosaic.css

mosaic.css

470 ms

style.css

style.css

473 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

472 ms

style-scrollbar.css

style-scrollbar.css

472 ms

mootools-core.js

mootools-core.js

479 ms

core.js

core.js

498 ms

caption.js

caption.js

587 ms

mootools-more.js

mootools-more.js

754 ms

jquery.min.js

jquery.min.js

9 ms

jquerynoconflict.js

jquerynoconflict.js

588 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

589 ms

rokbox.js

rokbox.js

590 ms

gantry-totop.js

gantry-totop.js

591 ms

browser-engines.js

browser-engines.js

703 ms

rokmediaqueries.js

rokmediaqueries.js

704 ms

rokmediaqueries.js

rokmediaqueries.js

705 ms

responsive.js

responsive.js

708 ms

responsive-selectbox.js

responsive-selectbox.js

708 ms

rokajaxsearch.js

rokajaxsearch.js

821 ms

jquery.lightbox_me.js

jquery.lightbox_me.js

821 ms

mootools-mobile.js

mootools-mobile.js

823 ms

rokmediaqueries.js

rokmediaqueries.js

824 ms

roksprocket.js

roksprocket.js

825 ms

moofx.js

moofx.js

871 ms

roksprocket.request.js

roksprocket.request.js

939 ms

mosaic.js

mosaic.js

940 ms

mosaic.js

mosaic.js

825 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

708 ms

logo2.jpg

logo2.jpg

124 ms

menu-separator.png

menu-separator.png

124 ms

menu-shadow.png

menu-shadow.png

123 ms

icon-cart.png

icon-cart.png

125 ms

icon-down.png

icon-down.png

124 ms

89.gif

89.gif

124 ms

img1.jpg

img1.jpg

351 ms

img2.jpg

img2.jpg

237 ms

img3.jpg

img3.jpg

352 ms

printButton.png

printButton.png

237 ms

emailButton.png

emailButton.png

236 ms

ballaton_cat_pre.jpg

ballaton_cat_pre.jpg

237 ms

zhadana_cat_pre.jpg

zhadana_cat_pre.jpg

354 ms

kseniya_cat_pre.jpg

kseniya_cat_pre.jpg

357 ms

hinomaki_red_cat_prev.jpg

hinomaki_red_cat_prev.jpg

357 ms

spiral.jpg

spiral.jpg

420 ms

module-shadow.png

module-shadow.png

419 ms

horiz-lines.png

horiz-lines.png

419 ms

search-icon.png

search-icon.png

420 ms

exo-regular-webfont.woff

exo-regular-webfont.woff

419 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

581 ms

Accessibility Review

prokazin.com accessibility score

90

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

prokazin.com 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

SEO Factors

prokazin.com 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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prokazin.com 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 Prokazin.com 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

prokazin.com

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