Tools & Wizards About Us
empyros.org screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

empyros.org

ЛЕТАЕМ В ЭМПИРЕЯХ

Page Load Speed

9.7 sec in total

First Response

2.6 sec

Resources Loaded

6.3 sec

Page Rendered

708 ms

empyros.org screenshot

About Website

Visit empyros.org now to see the best up-to-date Empyros content for Ukraine and also check out these interesting facts you probably never knew about empyros.org

Стихи, проза, музыка, живопись, графика, фото, изобретательство, приколы и прочее творчество - от И.Высоцкого и его друзей

Visit empyros.org

Key Findings

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

Performance Metrics

empyros.org performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value470 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value1.6 s

100/100

10%

Network Requests Diagram

empyros.org

2645 ms

hit

1373 ms

iemain.css

382 ms

e_01.gif

448 ms

e_02.gif

448 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 91% of them (41 requests) were addressed to the original Empyros.org, 2% (1 request) were made to Counter.yadro.ru and 2% (1 request) were made to Forum.vitliner.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Forum.vitliner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.1 kB (73%)

Content Size

26.3 kB

After Optimization

7.2 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Empyros.org main page is 26.3 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. HTML takes 22.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 16.5 kB

  • Original 22.2 kB
  • After minification 21.3 kB
  • After compression 5.6 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 16.5 kB or 75% of the original size.

Image Optimization

-7%

Potential reduce by 73 B

  • Original 1.1 kB
  • After minification 1.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. Empyros images are well optimized though.

CSS Optimization

-83%

Potential reduce by 2.5 kB

  • Original 3.0 kB
  • After minification 2.5 kB
  • After compression 519 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. Empyros.org needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (45%)

Requests Now

42

After Optimization

23

  • Images
  • CSS

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

Network Requests Diagram

empyros.org

empyros.org

2645 ms

hit

hit

1373 ms

iemain.css

iemain.css

382 ms

e_01.gif

e_01.gif

448 ms

e_02.gif

e_02.gif

448 ms

e_06.gif

e_06.gif

827 ms

e_04.gif

e_04.gif

905 ms

e_05.gif

e_05.gif

526 ms

e_20.gif

e_20.gif

539 ms

e_24.gif

e_24.gif

535 ms

e_23.gif

e_23.gif

672 ms

e_22.gif

e_22.gif

687 ms

e_21.gif

e_21.gif

688 ms

e_30.gif

e_30.gif

840 ms

e_35.gif

e_35.gif

851 ms

1x1.gif

1x1.gif

855 ms

e_32.gif

e_32.gif

970 ms

iz_vsk00406_v.jpg

iz_vsk00406_v.jpg

981 ms

is_0004.gif

is_0004.gif

978 ms

m_lop.gif

m_lop.gif

979 ms

m_lev.gif

m_lev.gif

1060 ms

m_isa.gif

m_isa.gif

1131 ms

m_grm.gif

m_grm.gif

1137 ms

m_ben.gif

m_ben.gif

1139 ms

m_jur.gif

m_jur.gif

1137 ms

m_zvi.gif

m_zvi.gif

1205 ms

m_vsk.gif

m_vsk.gif

1284 ms

m_mir.gif

m_mir.gif

1285 ms

m_lit.gif

m_lit.gif

1282 ms

m_vit.gif

m_vit.gif

1280 ms

vitliner_logo.gif

vitliner_logo.gif

3703 ms

3_0_4F6F6FFF_2F4F4FFF_1_pageviews

3_0_4F6F6FFF_2F4F4FFF_1_pageviews

1335 ms

e_33.gif

e_33.gif

1135 ms

e_40.gif

e_40.gif

1212 ms

e_41.gif

e_41.gif

1701 ms

bun01.gif

bun01.gif

1464 ms

m_home.gif

m_home.gif

1747 ms

watch.js

watch.js

61 ms

e_03_bg.gif

e_03_bg.gif

1453 ms

e_34_bg.gif

e_34_bg.gif

1492 ms

e_31_bg.gif

e_31_bg.gif

1161 ms

day_bg.gif

day_bg.gif

1253 ms

bg_tabline.gif

bg_tabline.gif

1346 ms

e_33_bg.gif

e_33_bg.gif

1400 ms

e_41_bg.gif

e_41_bg.gif

1397 ms

Accessibility Review

empyros.org accessibility score

48

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

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

empyros.org best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

empyros.org SEO score

67

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

    N/A

  • Language Claimed

    RU

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Empyros.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Russian. Our system also found out that Empyros.org 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

empyros.org

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