Access gigant-m.ru.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.509

15/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

gigant-m.ru

863 ms

jquery.min.js

376 ms

jquery-ui.min.js

492 ms

slick.css

223 ms

styles_articles_tpl.css

224 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 71% of them (40 requests) were addressed to the original Gigant-m.ru, 18% (10 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Counter.megagroup.ru. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Client.onicon.ru.

Content Size

894.8 kB

After Optimization

585.1 kB

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

HTML Optimization

-85%

Potential reduce by 173.9 kB

Original 204.3 kB
After minification 184.0 kB
After compression 30.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 173.9 kB or 85% of the original size.

Image Optimization

-31%

Potential reduce by 4.3 kB

Original 13.9 kB
After minification 9.6 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, Gigant M needs image optimization as it can save up to 4.3 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 86.5 kB

Original 526.7 kB
After minification 526.7 kB
After compression 440.3 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 86.5 kB or 16% of the original size.

CSS Optimization

-30%

Potential reduce by 45.1 kB

Original 149.9 kB
After minification 149.9 kB
After compression 104.8 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. Gigant-m.ru needs all CSS files to be minified and compressed as it can save up to 45.1 kB or 30% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

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 Gigant-m.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 Gigant-m.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

gigant-m.ru

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

gigant-m.ru

jquery.min.js

jquery-ui.min.js

slick.css

styles_articles_tpl.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

gigant-m.ru

jquery.min.js

jquery-ui.min.js

slick.css

styles_articles_tpl.css

lightgallery.min.css

lightgallery.proxy.to.hs.min.css

lightgallery.proxy.to.hs.stub.min.js

lightgallery.proxy.to.hs.js

ru.js

common.min.js

calendar.css

user.css

user.blue.css

user.js

theme.less.css

printme.js

tpl.js

baron.min.js

shop2.2.js

theme.scss.css

global_styles.css

addons_site.scss.css

jquery.matchHeight-min.js

s3.form.js

jquery.formstyler.min.js

jquery.ui.touch_punch.min.js

slick.min.js

jquery.responsiveTabs.min.js

flexmenu.min.js

modernizr.custom.js

lightgallery.min.js

lazyload.min.js

main.js

flexFix.js

site.min.js

663f64a3b887ee96238b4574.js

defender.min.js

spacer.gif

css

pattern.png

patern2.png

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf