Tools & Wizards About Us
treli.ru screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

treli.ru

empty page

Page Load Speed

5.4 sec in total

First Response

498 ms

Resources Loaded

4.6 sec

Page Rendered

268 ms

treli.ru screenshot

About Website

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

Избранное обо всем

Visit treli.ru

Key Findings

We analyzed Treli.ru page load time and found that the first response time was 498 ms and then it took 4.9 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

treli.ru performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value4,320 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.427

22/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

treli.ru

498 ms

www.treli.ru

1210 ms

common.css

657 ms

extLinks.js

256 ms

collapsedBn_class.js

453 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 66% of them (50 requests) were addressed to the original Treli.ru, 17% (13 requests) were made to Nnn.ru and 8% (6 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Treli.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.6 kB (32%)

Content Size

269.2 kB

After Optimization

182.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 40.1 kB

  • Original 54.5 kB
  • After minification 51.1 kB
  • After compression 14.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 40.1 kB or 73% of the original size.

Image Optimization

-9%

Potential reduce by 15.0 kB

  • Original 175.6 kB
  • After minification 160.6 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. Treli images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 5.8 kB

  • Original 7.4 kB
  • After minification 6.0 kB
  • After compression 1.6 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 5.8 kB or 79% of the original size.

CSS Optimization

-81%

Potential reduce by 25.7 kB

  • Original 31.7 kB
  • After minification 26.2 kB
  • After compression 6.0 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. Treli.ru needs all CSS files to be minified and compressed as it can save up to 25.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (44%)

Requests Now

70

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

treli.ru

treli.ru

498 ms

www.treli.ru

www.treli.ru

1210 ms

common.css

common.css

657 ms

extLinks.js

extLinks.js

256 ms

collapsedBn_class.js

collapsedBn_class.js

453 ms

show.cgi

show.cgi

407 ms

base.css

base.css

256 ms

content.css

content.css

403 ms

show.cgi

show.cgi

533 ms

top100.cnt

top100.cnt

266 ms

banner-88x31-rambler-gray2.gif

banner-88x31-rambler-gray2.gif

262 ms

cycounter

cycounter

260 ms

usa280709s.jpg

usa280709s.jpg

611 ms

300_baiden_280709_w120.jpg

300_baiden_280709_w120.jpg

381 ms

02_w120.jpg

02_w120.jpg

667 ms

03_w120.jpg

03_w120.jpg

685 ms

03_w120.jpg

03_w120.jpg

607 ms

02_w120.jpg

02_w120.jpg

571 ms

01_w120.jpg

01_w120.jpg

928 ms

voiko160908s_w70.jpg

voiko160908s_w70.jpg

830 ms

pavelsvat130709s_w70.jpg

pavelsvat130709s_w70.jpg

857 ms

120_bogomolov_290505_w70.jpg

120_bogomolov_290505_w70.jpg

889 ms

KnigaHudet.jpg

KnigaHudet.jpg

1279 ms

IMG_2007-10-15-lyzhi_w70.jpg

IMG_2007-10-15-lyzhi_w70.jpg

1051 ms

s_veteran_060508_w70.jpg

s_veteran_060508_w70.jpg

1215 ms

02_w70.jpg

02_w70.jpg

1222 ms

r082701_s_w70.jpg

r082701_s_w70.jpg

1164 ms

q_90708_w70.jpg

q_90708_w70.jpg

1325 ms

rice300408sm_w70.jpg

rice300408sm_w70.jpg

1324 ms

developer.gif

developer.gif

1421 ms

bnTabriz.gif

bnTabriz.gif

1586 ms

hit

hit

258 ms

topBgLBot.png

topBgLBot.png

1454 ms

topBgRBot.png

topBgRBot.png

1517 ms

logo.png

logo.png

1551 ms

slogan.png

slogan.png

1558 ms

mnuBgLTiled.png

mnuBgLTiled.png

1659 ms

mnuBgRTiled.png

mnuBgRTiled.png

1701 ms

mainBgTopTiled.gif

mainBgTopTiled.gif

1754 ms

mainBgRTiled.gif

mainBgRTiled.gif

1795 ms

app_2_BgRTop.png

app_2_BgRTop.png

1814 ms

mainBgBotTiled.gif

mainBgBotTiled.gif

1806 ms

mainBgRBot.png

mainBgRBot.png

1920 ms

mainBgLBot.png

mainBgLBot.png

1939 ms

contentBgLTop.png

contentBgLTop.png

1999 ms

h2_BgRBot.png

h2_BgRBot.png

2053 ms

bull.gif

bull.gif

2041 ms

app_1_BgTopTiled.gif

app_1_BgTopTiled.gif

2064 ms

app_1_BgLTop.png

app_1_BgLTop.png

2190 ms

info.min.js

info.min.js

402 ms

189273.js

189273.js

157 ms

pixel.gif

pixel.gif

193 ms

counter

counter

278 ms

hit;All_da_nnn_dn_realty

hit;All_da_nnn_dn_realty

178 ms

hit

hit

224 ms

app_1_BgRTop.png

app_1_BgRTop.png

1825 ms

3292486.jpg

3292486.jpg

135 ms

3298302.jpg

3298302.jpg

260 ms

3299579.jpg

3299579.jpg

264 ms

3267450.jpg

3267450.jpg

268 ms

3318572.jpg

3318572.jpg

269 ms

3318474.jpg

3318474.jpg

269 ms

3318467.jpg

3318467.jpg

270 ms

3299567.jpg

3299567.jpg

387 ms

3298579.jpg

3298579.jpg

391 ms

3325706.jpg

3325706.jpg

396 ms

hit;All_da_nnn_dn_realty

hit;All_da_nnn_dn_realty

130 ms

hit

hit

258 ms

appNewsDateBgBot.png

appNewsDateBgBot.png

1695 ms

appNewsDateBgLTiled.gif

appNewsDateBgLTiled.gif

1690 ms

appHeaderBgBot.gif

appHeaderBgBot.gif

1704 ms

botBgLTop.gif

botBgLTop.gif

1666 ms

hit

hit

127 ms

botBgRTop.gif

botBgRTop.gif

1763 ms

topBnFrame.gif

topBnFrame.gif

1626 ms

counter

counter

257 ms

Accessibility Review

treli.ru accessibility score

89

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

ARIA input fields 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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

treli.ru best practices score

58

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

treli.ru SEO score

91

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

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Treli.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 Treli.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

treli.ru

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