Tools & Wizards About Us
gresso.ru screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

gresso.ru

GRESSO | Очки нового поколения

Page Load Speed

3.4 sec in total

First Response

531 ms

Resources Loaded

2.6 sec

Page Rendered

277 ms

gresso.ru screenshot

About Website

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

Титановые | Ультралегкие | 10 лет гарантии | Немецкие линзы ZEISS

Visit gresso.ru

Key Findings

We analyzed Gresso.ru page load time and found that the first response time was 531 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

gresso.ru performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value1,760 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

gresso.ru

531 ms

jquery.bxslider.css

128 ms

bootstrap.css

252 ms

form.css

258 ms

template_styles.css

258 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 64% of them (37 requests) were addressed to the original Gresso.ru, 12% (7 requests) were made to Api-maps.yandex.ru and 7% (4 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (976 ms) belongs to the original domain Gresso.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 510.5 kB (41%)

Content Size

1.3 MB

After Optimization

743.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gresso.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. 40% of websites need less resources to load. Images take 541.3 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 138.8 kB

  • Original 216.8 kB
  • After minification 213.3 kB
  • After compression 78.0 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 138.8 kB or 64% of the original size.

Image Optimization

-1%

Potential reduce by 6.9 kB

  • Original 541.3 kB
  • After minification 534.4 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. GRESSO images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 255.3 kB

  • Original 365.4 kB
  • After minification 307.3 kB
  • After compression 110.1 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 255.3 kB or 70% of the original size.

CSS Optimization

-84%

Potential reduce by 109.5 kB

  • Original 130.7 kB
  • After minification 106.8 kB
  • After compression 21.2 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. Gresso.ru needs all CSS files to be minified and compressed as it can save up to 109.5 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

49

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gresso.ru

gresso.ru

531 ms

jquery.bxslider.css

jquery.bxslider.css

128 ms

bootstrap.css

bootstrap.css

252 ms

form.css

form.css

258 ms

template_styles.css

template_styles.css

258 ms

jquery.min.js

jquery.min.js

30 ms

228 ms

bootstrap.min.js

bootstrap.min.js

255 ms

vscrollarea.js

vscrollarea.js

277 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

276 ms

jquery.ui.selectmenu.js

jquery.ui.selectmenu.js

372 ms

jquery.uniform.min.js

jquery.uniform.min.js

377 ms

useful.lib.js

useful.lib.js

381 ms

validate.lib.js

validate.lib.js

386 ms

hash.js

hash.js

386 ms

button.js

button.js

387 ms

analyticstracking_init.js

analyticstracking_init.js

493 ms

script.js

script.js

501 ms

main.js

main.js

507 ms

jquery.bxslider.js

jquery.bxslider.js

517 ms

634 ms

combine.xml

combine.xml

569 ms

bg-body.jpg

bg-body.jpg

664 ms

logo.png

logo.png

128 ms

01.jpg

01.jpg

257 ms

04.jpg

04.jpg

259 ms

02.jpg

02.jpg

251 ms

05.jpg

05.jpg

247 ms

img2.png

img2.png

255 ms

kommersant.png

kommersant.png

371 ms

bgr.png

bgr.png

380 ms

slashgear.png

slashgear.png

382 ms

_.png

_.png

386 ms

analytics.js

analytics.js

40 ms

bg-b.gif

bg-b.gif

384 ms

Home_Gresso-Russia.jpg

Home_Gresso-Russia.jpg

976 ms

bx_loader.gif

bx_loader.gif

462 ms

controls.png

controls.png

467 ms

icon_inst.png

icon_inst.png

473 ms

sep.gif

sep.gif

473 ms

gothic.woff

gothic.woff

834 ms

myriad_pro-webfont.woff

myriad_pro-webfont.woff

720 ms

watch.js

watch.js

616 ms

watch.js

watch.js

177 ms

rtrg

rtrg

278 ms

ec.js

ec.js

15 ms

code.js

code.js

316 ms

sync

sync

32 ms

watch.js

watch.js

459 ms

counter

counter

157 ms

ef50ac9e93aaebe3299791c79f277f8e.cur

ef50ac9e93aaebe3299791c79f277f8e.cur

113 ms

3ce22e999d54bb9ca8150a59207f9d3e.cur

3ce22e999d54bb9ca8150a59207f9d3e.cur

169 ms

4965b66fe115b2f2ed500ece66514d86.cur

4965b66fe115b2f2ed500ece66514d86.cur

280 ms

77492cf358d8b12629399322926c93f2.cur

77492cf358d8b12629399322926c93f2.cur

391 ms

click.php

click.php

401 ms

advert.gif

advert.gif

91 ms

1

1

91 ms

tracker

tracker

154 ms

Accessibility Review

gresso.ru accessibility score

80

Accessibility Issues

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

gresso.ru best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

gresso.ru SEO score

85

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

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

gresso.ru

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