Tools & Wizards About Us
gigant-m.ru screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    72% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 90% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

gigant-m.ru

АО «ГИГАНТ» | Промышленные станки и оборудование для металлообработки и деревообработки

Page Load Speed

4.3 sec in total

First Response

546 ms

Resources Loaded

3.5 sec

Page Rendered

264 ms

gigant-m.ru screenshot

About Website

Click here to check amazing Gigant M content for Russia. Otherwise, check out these important facts you probably never knew about gigant-m.ru

Широкий ассортимент металлообрабатывающих, деревообрабатывающих станков, техоснастка. Доставка по всем городам России, Беларуси и Казахстана. Оборудование в лизинг

Visit gigant-m.ru

Key Findings

We analyzed Gigant-m.ru page load time and found that the first response time was 546 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

gigant-m.ru performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value5.6 s

54/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

gigant-m.ru

546 ms

www.gigant-m.ru

1305 ms

style.css

728 ms

cufon-yui.js

741 ms

Myriad_Pro_italic_400.font.js

901 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 67% of them (24 requests) were addressed to the original Gigant-m.ru, 14% (5 requests) were made to Mc.yandex.ru and 6% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Gigant-m.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.6 kB (51%)

Content Size

498.7 kB

After Optimization

244.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 91.0 kB

  • Original 109.0 kB
  • After minification 97.6 kB
  • After compression 18.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 91.0 kB or 84% of the original size.

Image Optimization

-16%

Potential reduce by 21.7 kB

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

JavaScript Optimization

-52%

Potential reduce by 119.4 kB

  • Original 229.8 kB
  • After minification 226.7 kB
  • After compression 110.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 119.4 kB or 52% of the original size.

CSS Optimization

-81%

Potential reduce by 22.5 kB

  • Original 27.8 kB
  • After minification 22.8 kB
  • After compression 5.3 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 22.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (31%)

Requests Now

32

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 32 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 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

gigant-m.ru

gigant-m.ru

546 ms

www.gigant-m.ru

www.gigant-m.ru

1305 ms

style.css

style.css

728 ms

cufon-yui.js

cufon-yui.js

741 ms

Myriad_Pro_italic_400.font.js

Myriad_Pro_italic_400.font.js

901 ms

jquery.min.js

jquery.min.js

7 ms

scripts.js

scripts.js

638 ms

jquery.fancybox.css

jquery.fancybox.css

642 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

874 ms

watch.js

watch.js

169 ms

base_bg.jpg

base_bg.jpg

362 ms

1000.jpg

1000.jpg

514 ms

title_bg.gif

title_bg.gif

396 ms

mws.gif

mws.gif

794 ms

logo.png

logo.png

337 ms

cat-list.png

cat-list.png

155 ms

Qr223BLFWY

Qr223BLFWY

171 ms

sprite.gif

sprite.gif

472 ms

header_bg.jpg

header_bg.jpg

654 ms

slash.png

slash.png

676 ms

at.png

at.png

521 ms

menu_bg.gif

menu_bg.gif

804 ms

prozent.png

prozent.png

832 ms

footer_bg.jpg

footer_bg.jpg

900 ms

hit

hit

255 ms

dev.gif

dev.gif

973 ms

ga.js

ga.js

25 ms

header.html

header.html

808 ms

__utm.gif

__utm.gif

11 ms

watch.js

watch.js

443 ms

widget_ru_RU.js

widget_ru_RU.js

189 ms

hit

hit

132 ms

advert.gif

advert.gif

87 ms

1

1

116 ms

ajax-loader.gif

ajax-loader.gif

337 ms

1147033

1147033

86 ms

Accessibility Review

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

Best Practices

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

gigant-m.ru SEO score

86

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