Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

inline.ru

INLINE.RU - ЭКОНОМИКА ФИНАНСЫ КУРСЫ ВАЛЮТ, ДОЛЛАР и ЕВРО, НОВОСТИ, FOREX, USD и EUR

Page Load Speed

3.4 sec in total

First Response

867 ms

Resources Loaded

2.2 sec

Page Rendered

405 ms

inline.ru screenshot

About Website

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

новости экономики, новости финансов, деловые новости, фондовый рынок, FOREX, политика, финансы

Visit inline.ru

Key Findings

We analyzed Inline.ru page load time and found that the first response time was 867 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

inline.ru performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value1,340 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.31

38/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

inline.ru

867 ms

main.css

264 ms

logo_new2.png

396 ms

white_line2.gif

269 ms

context.js

638 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 18% of them (9 requests) were addressed to the original Inline.ru, 64% (32 requests) were made to Icdn.lenta.ru and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Icdn.lenta.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.6 kB (18%)

Content Size

529.5 kB

After Optimization

432.0 kB

In fact, the total size of Inline.ru main page is 529.5 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. 30% of websites need less resources to load. Images take 400.0 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 92.6 kB

  • Original 108.1 kB
  • After minification 102.3 kB
  • After compression 15.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 92.6 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 4.6 kB

  • Original 400.0 kB
  • After minification 395.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. INLINE images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-70%

Potential reduce by 306 B

  • Original 437 B
  • After minification 315 B
  • After compression 131 B

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. Inline.ru needs all CSS files to be minified and compressed as it can save up to 306 B or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (6%)

Requests Now

47

After Optimization

44

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

Accessibility Review

inline.ru accessibility score

47

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.

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

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best Practices

inline.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inline.ru SEO score

69

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inline.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 Inline.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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