Tools & Wizards About Us

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

lintex.ru

ЛИНТЕКС - разработчик и производитель хирургических материалов (шовные материалы, эндопротезы-сетки для герниопластики и реконструкции тазового дна и ...

Page Load Speed

5.3 sec in total

First Response

1.7 sec

Resources Loaded

3.2 sec

Page Rendered

321 ms

About Website

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

Предприятие ЛИНТЕКС, основанное в 1991 году, является одним из ведущих российских разработчиков и производителей хирургических шовных материалов.

Visit lintex.ru

Key Findings

We analyzed Lintex.ru page load time and found that the first response time was 1.7 sec and then it took 3.6 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

lintex.ru performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value23.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value27.0 s

0/100

25%

SI (Speed Index)

Value27.0 s

0/100

10%

TBT (Total Blocking Time)

Value550 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value35.4 s

0/100

10%

Network Requests Diagram

www.lintex.ru

1700 ms

jquery.js

384 ms

jquery.lightbox-0.5.css

262 ms

jquery.form.js

266 ms

jquery.lightbox-0.5.pack.js

266 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 88% of them (58 requests) were addressed to the original Lintex.ru, 5% (3 requests) were made to S.ytimg.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Lintex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (50%)

Content Size

2.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lintex.ru main page is 2.7 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-27%

Potential reduce by 245.5 kB

  • Original 917.3 kB
  • After minification 912.1 kB
  • After compression 671.8 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 245.5 kB or 27% of the original size.

Image Optimization

-56%

Potential reduce by 627.7 kB

  • Original 1.1 MB
  • After minification 487.7 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, Lintex needs image optimization as it can save up to 627.7 kB or 56% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 254.1 kB

  • Original 377.1 kB
  • After minification 350.8 kB
  • After compression 123.0 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 254.1 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 217.3 kB

  • Original 261.5 kB
  • After minification 255.0 kB
  • After compression 44.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. Lintex.ru needs all CSS files to be minified and compressed as it can save up to 217.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (21%)

Requests Now

63

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lintex. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

lintex.ru accessibility score

93

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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.

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

Links do not have a discernible name

Best Practices

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

Displays images with incorrect aspect ratio

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

lintex.ru SEO score

90

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

    RU

  • Encoding

    UTF-8

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