Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

fruitarian.ru

Всё о фруктах

Page Load Speed

5.6 sec in total

First Response

709 ms

Resources Loaded

3.9 sec

Page Rendered

904 ms

fruitarian.ru screenshot

About Website

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

Блог о фруктах и сыроедении

Visit fruitarian.ru

Key Findings

We analyzed Fruitarian.ru page load time and found that the first response time was 709 ms and then it took 4.8 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

fruitarian.ru performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

fruitarian.ru

709 ms

template_css.css

315 ms

funcs.js

323 ms

nextgen_gallery_related_images.css

363 ms

styles.css

370 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 43% of them (51 requests) were addressed to the original Fruitarian.ru, 17% (20 requests) were made to Vk.com and 3% (4 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Fruitarian.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 596.1 kB (28%)

Content Size

2.1 MB

After Optimization

1.5 MB

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

HTML Optimization

-72%

Potential reduce by 38.3 kB

  • Original 52.9 kB
  • After minification 49.6 kB
  • After compression 14.6 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 38.3 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 36.5 kB

  • Original 1.2 MB
  • After minification 1.2 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. Fruitarian images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 444.0 kB

  • Original 703.8 kB
  • After minification 591.7 kB
  • After compression 259.9 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 444.0 kB or 63% of the original size.

CSS Optimization

-78%

Potential reduce by 77.3 kB

  • Original 99.0 kB
  • After minification 80.6 kB
  • After compression 21.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. Fruitarian.ru needs all CSS files to be minified and compressed as it can save up to 77.3 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (49%)

Requests Now

115

After Optimization

59

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

Accessibility Review

fruitarian.ru accessibility score

96

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

fruitarian.ru best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fruitarian.ru SEO score

82

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

    N/A

  • Encoding

    UTF-8

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