Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

24speak.com

Speak24 - эффективная онлайн методика изучения английского языка

Page Load Speed

12.1 sec in total

First Response

46 ms

Resources Loaded

9.8 sec

Page Rendered

2.3 sec

24speak.com screenshot

About Website

Click here to check amazing 24 Speak content for Russia. Otherwise, check out these important facts you probably never knew about 24speak.com

По данной методике западные спец-службы учат любой иностранный язык в течение 3х месяцев. Регистрируйтесь прямо сейчас и получите всю информацию о программе, а также подарок - систему (входящую в част...

Visit 24speak.com

Key Findings

We analyzed 24speak.com page load time and found that the first response time was 46 ms and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

24speak.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value21.3 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value3,730 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value29.8 s

0/100

10%

Network Requests Diagram

24speak.com

46 ms

24speak.com

565 ms

bootstrap.css

389 ms

bootstrap-dialog.min.css

387 ms

bootstrap-fixed.css

403 ms

Our browser made a total of 188 requests to load all elements on the main page. We found that 73% of them (137 requests) were addressed to the original 24speak.com, 17% (32 requests) were made to Player.vimeo.com and 3% (5 requests) were made to Fs1.terrasale.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain 24speak.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 947.1 kB (6%)

Content Size

16.7 MB

After Optimization

15.8 MB

In fact, the total size of 24speak.com main page is 16.7 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. Only a small number of websites need less resources to load. Images take 16.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 204.1 kB

  • Original 236.2 kB
  • After minification 169.7 kB
  • After compression 32.1 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 66.5 kB, which is 28% 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 204.1 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 717.0 kB

  • Original 16.2 MB
  • After minification 15.5 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. 24 Speak images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 19.6 kB

  • Original 201.8 kB
  • After minification 201.8 kB
  • After compression 182.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

-9%

Potential reduce by 6.4 kB

  • Original 75.4 kB
  • After minification 75.4 kB
  • After compression 69.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. 24speak.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (27%)

Requests Now

152

After Optimization

111

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

Accessibility Review

24speak.com accessibility score

68

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-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

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

Best Practices

24speak.com 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

SEO Factors

24speak.com SEO score

83

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 24speak.com 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 24speak.com 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

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