Tools & Wizards About Us

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

gigant-m.ru

Page Load Speed

4.3 sec in total

First Response

863 ms

Resources Loaded

3.1 sec

Page Rendered

290 ms

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 863 ms and then it took 3.4 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

18

Measured Metrics

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%

Network Requests Diagram

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 309.8 kB (35%)

Content Size

894.8 kB

After Optimization

585.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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 Breakdown

Number of requests can be reduced by 40 (89%)

Requests Now

45

After Optimization

5

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

gigant-m.ru accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

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

Page has valid source maps

SEO Factors

gigant-m.ru SEO score

91

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

    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

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: