Tools & Wizards About Us
i38.ru screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

i38.ru

Все новости Иркутска и Иркутской области - Информационное агентство «Телеинформ», г. Иркутск

Page Load Speed

4.5 sec in total

First Response

702 ms

Resources Loaded

3.5 sec

Page Rendered

328 ms

i38.ru screenshot

About Website

Click here to check amazing I 38 content for Russia. Otherwise, check out these important facts you probably never knew about i38.ru

ИА Телеинформ: новости Иркутской области и Иркутска сегодня, события и новости онлайн, Иркутск официальный, политика, экономика, общество, культура и многое другое о жизни Восточной Сибири

Visit i38.ru

Key Findings

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

Performance Metrics

i38.ru performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value18.4 s

0/100

25%

SI (Speed Index)

Value23.3 s

0/100

10%

TBT (Total Blocking Time)

Value7,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.527

14/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

i38.ru

702 ms

i38.ru

637 ms

btcontentslider.css

95 ms

default.css

84 ms

jquery.min.js

124 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 71% of them (56 requests) were addressed to the original I38.ru, 6% (5 requests) were made to Top-fwz1.mail.ru and 4% (3 requests) were made to News.mediametrics.ru. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Code.giraff.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 173.8 kB (9%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I38.ru main page is 2.0 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. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 128.9 kB

  • Original 164.6 kB
  • After minification 158.3 kB
  • After compression 35.7 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 128.9 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 16.1 kB

  • Original 1.6 MB
  • After minification 1.6 MB

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. I 38 images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 24.4 kB

  • Original 239.6 kB
  • After minification 239.6 kB
  • After compression 215.2 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

-35%

Potential reduce by 4.3 kB

  • Original 12.4 kB
  • After minification 12.4 kB
  • After compression 8.1 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. I38.ru needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (38%)

Requests Now

74

After Optimization

46

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

i38.ru

i38.ru

702 ms

i38.ru

i38.ru

637 ms

btcontentslider.css

btcontentslider.css

95 ms

default.css

default.css

84 ms

jquery.min.js

jquery.min.js

124 ms

slides.js

slides.js

85 ms

default.js

default.js

98 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

110 ms

blog_calendar.js

blog_calendar.js

114 ms

blog_list.js

blog_list.js

121 ms

template.css

template.css

141 ms

cookies.css

cookies.css

145 ms

jquery.js

jquery.js

332 ms

arrow.js

arrow.js

151 ms

cprgt.js

cprgt.js

151 ms

adsbygoogle.js

adsbygoogle.js

118 ms

widget-i38ru.js

widget-i38ru.js

1122 ms

context.js

context.js

918 ms

css

css

32 ms

b.fcgi

b.fcgi

807 ms

inpage_adnitro.js

inpage_adnitro.js

782 ms

cycounter

cycounter

691 ms

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

3_1_FFFFFFFF_EFEFEFFF_0_pageviews

675 ms

logo.png

logo.png

203 ms

flag.png

flag.png

99 ms

mlogo.png

mlogo.png

98 ms

logo2.png

logo2.png

99 ms

iris.jpg

iris.jpg

98 ms

tw.png

tw.png

97 ms

ok.png

ok.png

130 ms

vk.png

vk.png

130 ms

tg.png

tg.png

131 ms

kreml-002.jpg

kreml-002.jpg

150 ms

venger.jpeg

venger.jpeg

177 ms

operation-023.jpg

operation-023.jpg

204 ms

cult-039.jpg

cult-039.jpg

201 ms

airport-irk-1.jpg

airport-irk-1.jpg

268 ms

110424-10.jpg

110424-10.jpg

284 ms

organnii_zal.jpg

organnii_zal.jpg

241 ms

hands.jpg

hands.jpg

222 ms

korova.jpg

korova.jpg

226 ms

hirurgi.jpg

hirurgi.jpg

239 ms

sud.jpg

sud.jpg

249 ms

baikal-kosmos.jpg

baikal-kosmos.jpg

256 ms

str1.jpg

str1.jpg

266 ms

obezd.jpg

obezd.jpg

268 ms

rublll.jpg

rublll.jpg

297 ms

diplom.jpg

diplom.jpg

283 ms

venger.jpg

venger.jpg

297 ms

solar_eruption.jpg

solar_eruption.jpg

296 ms

luk.jpg

luk.jpg

303 ms

veter.jpg

veter.jpg

308 ms

radio.jpg

radio.jpg

313 ms

techno_biznes.jpg

techno_biznes.jpg

326 ms

birthdays-and-dates.jpg

birthdays-and-dates.jpg

323 ms

kinozal.jpg

kinozal.jpg

327 ms

rabota.jpg

rabota.jpg

336 ms

pressa.jpg

pressa.jpg

997 ms

tag.js

tag.js

753 ms

code.js

code.js

854 ms

b11.gif

b11.gif

370 ms

informer_png.php

informer_png.php

919 ms

font

font

45 ms

BEBASNEUE%20BOLD.woff

BEBASNEUE%20BOLD.woff

249 ms

h.css

h.css

131 ms

counter2

counter2

206 ms

hit

hit

658 ms

1715887375blob.jpg

1715887375blob.jpg

183 ms

top100.js

top100.js

763 ms

kreml-002.jpg

kreml-002.jpg

652 ms

loading.gif

loading.gif

32 ms

arrow46.png

arrow46.png

30 ms

sync-loader.js

sync-loader.js

768 ms

counter

counter

145 ms

dyn-goal-config.js

dyn-goal-config.js

142 ms

advert.gif

advert.gif

663 ms

hit

hit

131 ms

sync_cookie_image_decide

sync_cookie_image_decide

162 ms

tracker

tracker

145 ms

Accessibility Review

i38.ru accessibility score

75

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

i38.ru SEO score

92

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

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

i38.ru

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