Tools & Wizards About Us
plantus.ru screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 0

    Best Practices

  • 84

    SEO

    Google-friendlier than
    53% of websites

plantus.ru

Page Load Speed

5.2 sec in total

First Response

675 ms

Resources Loaded

3.3 sec

Page Rendered

1.2 sec

plantus.ru screenshot

About Website

Welcome to plantus.ru homepage info - get ready to check Plantus best content for Russia right away, or after learning these important things about plantus.ru

Visit plantus.ru

Key Findings

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

Performance Metrics

plantus.ru performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

plantus.ru

675 ms

node.css

97 ms

defaults.css

198 ms

system.css

194 ms

system-menus.css

199 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 74% of them (42 requests) were addressed to the original Plantus.ru, 7% (4 requests) were made to Pagead2.googlesyndication.com and 5% (3 requests) were made to An.yandex.ru. The less responsive or slowest element that took the longest time to load (790 ms) belongs to the original domain Plantus.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 263.4 kB (20%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Plantus.ru main page is 1.3 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 975.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 172.4 kB

  • Original 200.9 kB
  • After minification 199.5 kB
  • After compression 28.5 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 172.4 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 38.4 kB

  • Original 975.7 kB
  • After minification 937.3 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. Plantus images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 27.5 kB

  • Original 109.2 kB
  • After minification 101.9 kB
  • After compression 81.7 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 27.5 kB or 25% of the original size.

CSS Optimization

-77%

Potential reduce by 25.1 kB

  • Original 32.5 kB
  • After minification 23.3 kB
  • After compression 7.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. Plantus.ru needs all CSS files to be minified and compressed as it can save up to 25.1 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

53

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

plantus.ru

plantus.ru

675 ms

node.css

node.css

97 ms

defaults.css

defaults.css

198 ms

system.css

system.css

194 ms

system-menus.css

system-menus.css

199 ms

user.css

user.css

200 ms

content-module.css

content-module.css

196 ms

date.css

date.css

197 ms

filefield.css

filefield.css

283 ms

views.css

views.css

287 ms

style.css

style.css

286 ms

jquery.js

jquery.js

376 ms

drupal.js

drupal.js

288 ms

ru_3f35f81e6340ec1f5fab3b41a72b4382.js

ru_3f35f81e6340ec1f5fab3b41a72b4382.js

288 ms

poormanscron.js

poormanscron.js

375 ms

adsbygoogle.js

adsbygoogle.js

8 ms

bluemarine_logo.jpg

bluemarine_logo.jpg

214 ms

img_2956_2.jpg

img_2956_2.jpg

217 ms

851548366aed919a19c307379d267043.jpg

851548366aed919a19c307379d267043.jpg

215 ms

koren.jpg

koren.jpg

303 ms

hc5qjnxbaps.jpg

hc5qjnxbaps.jpg

215 ms

img_20140801_174126.jpg

img_20140801_174126.jpg

214 ms

image_19.jpg

image_19.jpg

393 ms

wp_001139_0.jpg

wp_001139_0.jpg

306 ms

84370926_large_5d327d6e58c847e09b798a3b8df5bd17.jpeg

84370926_large_5d327d6e58c847e09b798a3b8df5bd17.jpeg

393 ms

p1010022.png

p1010022.png

579 ms

cvetok_6.jpg

cvetok_6.jpg

484 ms

p020614_1013.jpg

p020614_1013.jpg

480 ms

dscn9680.jpg

dscn9680.jpg

482 ms

555.jpg

555.jpg

570 ms

win_20140504_113122.jpg

win_20140504_113122.jpg

570 ms

kira-pc_-_win_20140430_130718.jpg

kira-pc_-_win_20140430_130718.jpg

569 ms

dsc_0285-1.jpg

dsc_0285-1.jpg

661 ms

img_2275.jpg

img_2275.jpg

573 ms

img_20140416_130231_0.jpg

img_20140416_130231_0.jpg

751 ms

img_20140416_130237.jpg

img_20140416_130237.jpg

781 ms

img_20130815_19.jpg

img_20130815_19.jpg

751 ms

teshchin_yazyk.jpeg

teshchin_yazyk.jpeg

662 ms

mak_3.jpeg

mak_3.jpeg

668 ms

24.gif

24.gif

787 ms

kleshch1.jpg

kleshch1.jpg

788 ms

limon5_1.jpg

limon5_1.jpg

790 ms

context.js

context.js

244 ms

context_static_r1084.js

context_static_r1084.js

735 ms

71469

71469

648 ms

watch.js

watch.js

30 ms

y150

y150

218 ms

y150

y150

247 ms

y150

y150

329 ms

ca-pub-3268730266042409.js

ca-pub-3268730266042409.js

154 ms

zrt_lookup.html

zrt_lookup.html

121 ms

show_ads_impl.js

show_ads_impl.js

50 ms

bgbgbg.jpg

bgbgbg.jpg

219 ms

hit

hit

280 ms

watch.js

watch.js

2 ms

ads

ads

277 ms

osd.js

osd.js

39 ms

Accessibility Review

plantus.ru accessibility score

86

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

SEO Factors

plantus.ru SEO score

84

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

    N/A

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plantus.ru can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Russian. Our system also found out that Plantus.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

plantus.ru

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