Tools & Wizards About Us

Report Summary

  • 83

    Performance

    Renders faster than
    87% of other websites

  • 29

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

gardener.ru

GARDENER.ru - ландшафтный дизайн и архитектура сада | Информационный портал о ландшафтном дизайне

Page Load Speed

4.4 sec in total

First Response

498 ms

Resources Loaded

3.7 sec

Page Rendered

203 ms

About Website

Click here to check amazing GARDENER content for Russia. Otherwise, check out these important facts you probably never knew about gardener.ru

Информационный портал о ландшафтном дизайне

Visit gardener.ru

Key Findings

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

Performance Metrics

gardener.ru performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value3.7 s

91/100

10%

Network Requests Diagram

gardener.ru

498 ms

gardener.ru

632 ms

all.css

158 ms

ie-hover-ns-pack.js

293 ms

jquery-1.6.1.min.js

527 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 97% of them (60 requests) were addressed to the original Gardener.ru, 2% (1 request) were made to Mc.yandex.ru and 2% (1 request) were made to Yandex.ru. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Gardener.ru.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gardener.ru main page is 1.2 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. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 28.5 kB

  • Original 34.9 kB
  • After minification 33.1 kB
  • After compression 6.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 28.5 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 117.2 kB

  • Original 1.1 MB
  • After minification 954.7 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, GARDENER needs image optimization as it can save up to 117.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-10%

Potential reduce by 4.1 kB

  • Original 40.6 kB
  • After minification 40.6 kB
  • After compression 36.5 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

-11%

Potential reduce by 736 B

  • Original 6.7 kB
  • After minification 6.7 kB
  • After compression 6.0 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. Gardener.ru needs all CSS files to be minified and compressed as it can save up to 736 B or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (5%)

Requests Now

57

After Optimization

54

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

gardener.ru accessibility score

29

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

gardener.ru best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

gardener.ru SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

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