Tools & Wizards About Us
englex.ru screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    37% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

englex.ru

Английский онлайн — курсы английского языка по Скайпу в онлайн-школе «Инглекс»

Page Load Speed

8.5 sec in total

First Response

1.5 sec

Resources Loaded

4.9 sec

Page Rendered

2.2 sec

englex.ru screenshot

About Website

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

Онлайн-школа английского по Скайпу «Инглекс»⠀➤ Сильные учителя⠀➤ Скидки до 40% ☑️Попробуйте бесплатно!

Visit englex.ru

Key Findings

We analyzed Englex.ru page load time and found that the first response time was 1.5 sec and then it took 7 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

englex.ru performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value8,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.094

91/100

15%

TTI (Time to Interactive)

Value42.4 s

0/100

10%

Network Requests Diagram

englex.ru

1503 ms

core-ui-select.css

185 ms

jquery.scrollpane.css

356 ms

style.css

516 ms

jquery.min.js

52 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 82% of them (51 requests) were addressed to the original Englex.ru, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Englex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 306.7 kB (52%)

Content Size

587.2 kB

After Optimization

280.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Englex.ru main page is 587.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. 35% of websites need less resources to load. Javascripts take 219.8 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 20.0 kB

  • Original 27.5 kB
  • After minification 26.0 kB
  • After compression 7.4 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 20.0 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 1.6 kB

  • Original 174.8 kB
  • After minification 173.2 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. Englex images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 147.3 kB

  • Original 219.8 kB
  • After minification 184.6 kB
  • After compression 72.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 147.3 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 137.8 kB

  • Original 165.1 kB
  • After minification 141.2 kB
  • After compression 27.3 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. Englex.ru needs all CSS files to be minified and compressed as it can save up to 137.8 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

englex.ru

englex.ru

1503 ms

core-ui-select.css

core-ui-select.css

185 ms

jquery.scrollpane.css

jquery.scrollpane.css

356 ms

style.css

style.css

516 ms

jquery.min.js

jquery.min.js

52 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

359 ms

jquery.columnizer.min.js

jquery.columnizer.min.js

365 ms

jquery.mousewheel.js

jquery.mousewheel.js

363 ms

jquery.scrollpane.js

jquery.scrollpane.js

363 ms

jquery.core-ui-select.js

jquery.core-ui-select.js

505 ms

jquery.quicksand.js

jquery.quicksand.js

629 ms

script.js

script.js

623 ms

core.min.js

core.min.js

620 ms

widget.min.js

widget.min.js

695 ms

mouse.min.js

mouse.min.js

805 ms

sortable.min.js

sortable.min.js

804 ms

jquery.validate.min.js

jquery.validate.min.js

805 ms

jquery.cycle.all.js

jquery.cycle.all.js

38 ms

jquery.cycle.all.js

jquery.cycle.all.js

134 ms

html_bg.jpg

html_bg.jpg

209 ms

topmenu.png

topmenu.png

257 ms

tempmenu_item.png

tempmenu_item.png

259 ms

contacts_social_ext.png

contacts_social_ext.png

259 ms

logo.jpg

logo.jpg

259 ms

mainmenu_bg.png

mainmenu_bg.png

259 ms

bigredarc.png

bigredarc.png

1659 ms

signup_btn.png

signup_btn.png

460 ms

button_horizont.png

button_horizont.png

1041 ms

three_simple_q.png

three_simple_q.png

1514 ms

yellowarc.png

yellowarc.png

522 ms

reasons_numbers.png

reasons_numbers.png

927 ms

three_steps.png

three_steps.png

631 ms

simple_steps_resume.png

simple_steps_resume.png

726 ms

call_backs_bg.png

call_backs_bg.png

907 ms

avatar_keeper.png

avatar_keeper.png

926 ms

dots.png

dots.png

1031 ms

barblockstupidheader.png

barblockstupidheader.png

1066 ms

sidebar-video.jpg

sidebar-video.jpg

1124 ms

barblock_footer_arr.png

barblock_footer_arr.png

1423 ms

barblock_footer.png

barblock_footer.png

1424 ms

elena_ko_165.jpg

elena_ko_165.jpg

1428 ms

prices_header.png

prices_header.png

1424 ms

popup_shadow.png

popup_shadow.png

1424 ms

payment_methods_footer.png

payment_methods_footer.png

1425 ms

Tl736kjuZv4

Tl736kjuZv4

830 ms

pfsquaresanspro-medium-webfont.woff

pfsquaresanspro-medium-webfont.woff

1299 ms

pfsquaresanspro-bold-webfont.woff

pfsquaresanspro-bold-webfont.woff

1700 ms

pfsquaresanspro-light-webfont.woff

pfsquaresanspro-light-webfont.woff

1849 ms

pfsquaresanspro-regular-webfont.woff

pfsquaresanspro-regular-webfont.woff

2499 ms

footer_wr.png

footer_wr.png

1511 ms

footer_logo.png

footer_logo.png

1698 ms

agente.png

agente.png

1704 ms

watch.js

watch.js

65 ms

analytics.js

analytics.js

671 ms

blank_review_1651.jpg

blank_review_1651.jpg

1631 ms

call_backs_overflow_x.png

call_backs_overflow_x.png

1632 ms

call_backs_overflow.png

call_backs_overflow.png

1725 ms

collect

collect

41 ms

www-embed-player-vfl5foy2V.css

www-embed-player-vfl5foy2V.css

170 ms

www-embed-player.js

www-embed-player.js

290 ms

veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js

veBs87dwiCXgZb9CwomBYiW1hyWXgp0ohA3Vj3gnbUg.js

240 ms

ad_status.js

ad_status.js

424 ms

Accessibility Review

englex.ru accessibility score

87

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-hidden="true"] elements contain focusable descendents

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

Best Practices

englex.ru best practices score

83

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

Page has valid source maps

SEO Factors

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Englex.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Englex.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

englex.ru

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