Tools & Wizards About Us
infuture.ru screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

infuture.ru

InFuture.ru - новости науки и техники

Page Load Speed

5.6 sec in total

First Response

1.3 sec

Resources Loaded

2.9 sec

Page Rendered

1.5 sec

infuture.ru screenshot

About Website

Welcome to infuture.ru homepage info - get ready to check In Future best content for Russia right away, or after learning these important things about infuture.ru

InFuture.ru - Почувствуй будущее!

Visit infuture.ru

Key Findings

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

Performance Metrics

infuture.ru performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

infuture.ru

1258 ms

infuture.css

276 ms

swiper.min.css

283 ms

bootstrap-grid.min.css

280 ms

quill.snow.css

281 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 67% of them (28 requests) were addressed to the original Infuture.ru, 7% (3 requests) were made to Googleads.g.doubleclick.net and 5% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Infuture.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 172.4 kB (12%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Infuture.ru main page is 1.4 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 775.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 138.9 kB

  • Original 169.4 kB
  • After minification 149.1 kB
  • After compression 30.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. This page needs HTML code to be minified as it can gain 20.2 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 138.9 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 6.5 kB

  • Original 775.5 kB
  • After minification 769.0 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. In Future images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.6 kB

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

CSS Optimization

-53%

Potential reduce by 25.4 kB

  • Original 48.1 kB
  • After minification 45.5 kB
  • After compression 22.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. Infuture.ru needs all CSS files to be minified and compressed as it can save up to 25.4 kB or 53% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

infuture.ru

infuture.ru

1258 ms

infuture.css

infuture.css

276 ms

swiper.min.css

swiper.min.css

283 ms

bootstrap-grid.min.css

bootstrap-grid.min.css

280 ms

quill.snow.css

quill.snow.css

281 ms

style.css

style.css

424 ms

adsbygoogle.js

adsbygoogle.js

92 ms

infuture.css

infuture.css

288 ms

swiper.min.css

swiper.min.css

410 ms

bootstrap-grid.min.css

bootstrap-grid.min.css

416 ms

quill.snow.css

quill.snow.css

416 ms

style.css

style.css

421 ms

logo.png

logo.png

672 ms

a28b7c1e9415f7d64d28150d754a17a6_1.js

a28b7c1e9415f7d64d28150d754a17a6_1.js

140 ms

js

js

49 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

597 ms

socket.io.js

socket.io.js

608 ms

swiper.min.js

swiper.min.js

607 ms

selection-sharer.js

selection-sharer.js

535 ms

quill.min.js

quill.min.js

621 ms

app.js

app.js

714 ms

cd-icon-close.svg

cd-icon-close.svg

488 ms

real_logo.svg

real_logo.svg

420 ms

show_ads_impl.js

show_ads_impl.js

613 ms

fzeiwi0uxuo0qszprfdo7tc0.jpg

fzeiwi0uxuo0qszprfdo7tc0.jpg

764 ms

iupyfcrm4ko01uw1nbmif8hs0.jpg

iupyfcrm4ko01uw1nbmif8hs0.jpg

365 ms

mi8bn431f4g01ic7mokubx1c0.jpg

mi8bn431f4g01ic7mokubx1c0.jpg

776 ms

o6zz0vitltc0azmio1zul4s0.jpg

o6zz0vitltc0azmio1zul4s0.jpg

938 ms

1qyijf3eupvk01o2c8k91ei8w0.jpg

1qyijf3eupvk01o2c8k91ei8w0.jpg

747 ms

whitelogo.png

whitelogo.png

465 ms

infuture.woff

infuture.woff

499 ms

hit

hit

244 ms

watch.js

watch.js

0 ms

js

js

77 ms

analytics.js

analytics.js

34 ms

collect

collect

47 ms

smil.user.js

smil.user.js

314 ms

hit

hit

489 ms

zrt_lookup.html

zrt_lookup.html

35 ms

ads

ads

365 ms

ads

ads

500 ms

real_logo.svg

real_logo.svg

143 ms

Accessibility Review

infuture.ru accessibility score

86

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

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

infuture.ru SEO score

85

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

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

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

infuture.ru

Open Graph data is detected on the main page of In Future. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: