Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

gekko.ru

Гекко — фабрика высокой кухни — готовая еда от шеф-повара

Page Load Speed

3.6 sec in total

First Response

754 ms

Resources Loaded

2.3 sec

Page Rendered

540 ms

gekko.ru screenshot

About Website

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

Visit gekko.ru

Key Findings

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

Performance Metrics

gekko.ru performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value2,380 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

gekko.ru

754 ms

centermenu.css

249 ms

arrowlistmenu.css

257 ms

jquery.fancybox-1.3.4.css

257 ms

layout.css

261 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 71% of them (50 requests) were addressed to the original Gekko.ru, 13% (9 requests) were made to A.disquscdn.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (754 ms) belongs to the original domain Gekko.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 262.9 kB (59%)

Content Size

446.9 kB

After Optimization

184.1 kB

In fact, the total size of Gekko.ru main page is 446.9 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. 45% of websites need less resources to load. Javascripts take 274.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 43.2 kB

  • Original 57.4 kB
  • After minification 56.9 kB
  • After compression 14.2 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 43.2 kB or 75% of the original size.

Image Optimization

-26%

Potential reduce by 21.3 kB

  • Original 83.2 kB
  • After minification 61.9 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, Gekko needs image optimization as it can save up to 21.3 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 173.5 kB

  • Original 274.8 kB
  • After minification 240.1 kB
  • After compression 101.4 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 173.5 kB or 63% of the original size.

CSS Optimization

-79%

Potential reduce by 24.9 kB

  • Original 31.5 kB
  • After minification 25.9 kB
  • After compression 6.6 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. Gekko.ru needs all CSS files to be minified and compressed as it can save up to 24.9 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

65

After Optimization

28

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

Accessibility Review

gekko.ru accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

High

[role]s are not contained by their required parent element

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

gekko.ru 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

High

Missing source maps for large first-party JavaScript

SEO Factors

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

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

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 Gekko.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 Gekko.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 Gekko. 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: