Tools & Wizards About Us
metancor.md screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

metancor.md

Oțel inoxidabil (Inox ) in Chisinau

Page Load Speed

6.5 sec in total

First Response

545 ms

Resources Loaded

4.7 sec

Page Rendered

1.3 sec

metancor.md screenshot

About Website

Welcome to metancor.md homepage info - get ready to check Metancor best content for Moldova right away, or after learning these important things about metancor.md

Oțel inoxidabil (Inox ) in Chisinau

Visit metancor.md

Key Findings

We analyzed Metancor.md page load time and found that the first response time was 545 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

metancor.md performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value1,990 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.247

50/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

metancor.md

545 ms

metancor.md

1376 ms

site.theme.min.css

710 ms

js

59 ms

font.css

262 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 73% of them (24 requests) were addressed to the original Metancor.md, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Metancor.md.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (66%)

Content Size

1.5 MB

After Optimization

521.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Metancor.md main page is 1.5 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. 50% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 943.2 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 131.5 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 943.2 kB or 88% of the original size.

Image Optimization

-10%

Potential reduce by 4.2 kB

  • Original 43.4 kB
  • After minification 39.3 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. Metancor images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 37.8 kB

  • Original 309.6 kB
  • After minification 309.6 kB
  • After compression 271.7 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 37.8 kB or 12% of the original size.

CSS Optimization

-25%

Potential reduce by 26.4 kB

  • Original 105.1 kB
  • After minification 105.1 kB
  • After compression 78.7 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. Metancor.md needs all CSS files to be minified and compressed as it can save up to 26.4 kB or 25% of the original size.

Requests Breakdown

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

Requests Now

20

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

metancor.md

metancor.md

545 ms

metancor.md

metancor.md

1376 ms

site.theme.min.css

site.theme.min.css

710 ms

js

js

59 ms

font.css

font.css

262 ms

frontend.bundle.js

frontend.bundle.js

499 ms

vendors.min.js

vendors.min.js

674 ms

site.theme.min.js

site.theme.min.js

499 ms

shop.theme.min.js

shop.theme.min.js

570 ms

gtm.js

gtm.js

157 ms

fbevents.js

fbevents.js

172 ms

tag.js

tag.js

1015 ms

embed

embed

247 ms

logo.png

logo.png

198 ms

11-14.svg

11-14.svg

195 ms

Rubik-400-3.ttf

Rubik-400-3.ttf

147 ms

Rubik-500-4.ttf

Rubik-500-4.ttf

308 ms

Rubik-300-2.ttf

Rubik-300-2.ttf

346 ms

Rubik-600-5.ttf

Rubik-600-5.ttf

402 ms

Rubik-700-6.ttf

Rubik-700-6.ttf

274 ms

Rubik-800-7.ttf

Rubik-800-7.ttf

307 ms

Rubik-900-8.ttf

Rubik-900-8.ttf

308 ms

Rubik-400-1.ttf

Rubik-400-1.ttf

485 ms

frontend.bundle.css

frontend.bundle.css

428 ms

js

js

50 ms

config.json

config.json

138 ms

smart-button-phone.svg

smart-button-phone.svg

162 ms

roboto-v15-latin_cyrillic-500.woff

roboto-v15-latin_cyrillic-500.woff

328 ms

roboto-v15-latin_cyrillic-300.woff

roboto-v15-latin_cyrillic-300.woff

281 ms

roboto-v15-latin_cyrillic-100.woff

roboto-v15-latin_cyrillic-100.woff

144 ms

advert.gif

advert.gif

685 ms

sync_cookie_image_decide

sync_cookie_image_decide

130 ms

sync_cookie_image_decide

sync_cookie_image_decide

151 ms

Accessibility Review

metancor.md accessibility score

81

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

metancor.md best practices score

83

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

Page has valid source maps

SEO Factors

metancor.md SEO score

89

Search Engine Optimization Advices

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

    RO

  • Language Claimed

    RO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metancor.md can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Metancor.md 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

metancor.md

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