Tools & Wizards About Us
preply.org screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

preply.org

Find online language tutors at Preply. Book your first lesson now!

Page Load Speed

1.8 sec in total

First Response

159 ms

Resources Loaded

1.5 sec

Page Rendered

146 ms

preply.org screenshot

About Website

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

Looking for a tutor? Preply is the best platform for private online lessons with a flexible payment system and affordable prices. Book your first lesson.

Visit preply.org

Key Findings

We analyzed Preply.org page load time and found that the first response time was 159 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

preply.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value5,750 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

preply.org

159 ms

preply.com

431 ms

polyfills-c67a75d1b6f99dc8.js

127 ms

webpack-e236841087b7a06a.js

154 ms

framework-24b689b0ef8cdbd3.js

157 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Preply.org, 91% (40 requests) were made to Static.preply.com and 7% (3 requests) were made to Preply.com. The less responsive or slowest element that took the longest time to load (742 ms) relates to the external source Static.preply.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 667.4 kB (37%)

Content Size

1.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Preply.org main page is 1.8 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. 65% of websites need less resources to load. Images take 822.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 667.1 kB

  • Original 821.8 kB
  • After minification 821.7 kB
  • After compression 154.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 667.1 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 822.9 kB
  • After minification 822.9 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. Preply images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 173 B

  • Original 142.9 kB
  • After minification 142.9 kB
  • After compression 142.7 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

-0%

Potential reduce by 51 B

  • Original 37.1 kB
  • After minification 37.1 kB
  • After compression 37.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. Preply.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (79%)

Requests Now

42

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

preply.org

preply.org

159 ms

preply.com

preply.com

431 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

127 ms

webpack-e236841087b7a06a.js

webpack-e236841087b7a06a.js

154 ms

framework-24b689b0ef8cdbd3.js

framework-24b689b0ef8cdbd3.js

157 ms

main-4137e24349c18114.js

main-4137e24349c18114.js

155 ms

_app-0e8959e1bd78d95a.js

_app-0e8959e1bd78d95a.js

202 ms

styles-f3c22f9d3392120d.js

styles-f3c22f9d3392120d.js

121 ms

774-7ec61ac81fa88e19.js

774-7ec61ac81fa88e19.js

315 ms

2332-ef54b4b3cf61eccc.js

2332-ef54b4b3cf61eccc.js

314 ms

7967-08762c3afacf03b3.js

7967-08762c3afacf03b3.js

375 ms

2273-51620a60081e5fae.js

2273-51620a60081e5fae.js

377 ms

3131-77cdf7f8ac91dad2.js

3131-77cdf7f8ac91dad2.js

320 ms

2871-fd2b6acba0cd8ec0.js

2871-fd2b6acba0cd8ec0.js

378 ms

4792-f35e85d1da441bc3.js

4792-f35e85d1da441bc3.js

380 ms

4688-76d958a4628b8d61.js

4688-76d958a4628b8d61.js

382 ms

5652-892d6ca6d5105e56.js

5652-892d6ca6d5105e56.js

383 ms

7018-f265d13ee0a0eb36.js

7018-f265d13ee0a0eb36.js

389 ms

9235-f404d599e5ab294b.js

9235-f404d599e5ab294b.js

389 ms

2068-00db52fc09169ad3.js

2068-00db52fc09169ad3.js

403 ms

6398-bd1402d504064ef8.js

6398-bd1402d504064ef8.js

392 ms

5552-4c87e09b4280590d.js

5552-4c87e09b4280590d.js

395 ms

3735-df243de778ffa67e.js

3735-df243de778ffa67e.js

391 ms

3314-02af21a90a9f4862.js

3314-02af21a90a9f4862.js

392 ms

8999-450e0b7fdcd741e1.js

8999-450e0b7fdcd741e1.js

393 ms

925-8bc51a282f61c175.js

925-8bc51a282f61c175.js

396 ms

9831-f6225403511e5f5b.js

9831-f6225403511e5f5b.js

399 ms

7105-9108ee39151441c5.js

7105-9108ee39151441c5.js

396 ms

1253-f74ff6cbc3c4dccb.js

1253-f74ff6cbc3c4dccb.js

395 ms

9534-1e588990cc0ed344.js

9534-1e588990cc0ed344.js

397 ms

2550-02894afc022b7de2.js

2550-02894afc022b7de2.js

409 ms

home-c9c2f2fcd4a2b0dd.js

home-c9c2f2fcd4a2b0dd.js

411 ms

_buildManifest.js

_buildManifest.js

731 ms

_ssgManifest.js

_ssgManifest.js

742 ms

hero-image-1600-1b48d990d7bbc637b042d8cc927bd71b.jpg

hero-image-1600-1b48d990d7bbc637b042d8cc927bd71b.jpg

684 ms

b2b-banner-mobile-736-f7a0fea027670d85b929d4297f46cb51.png

b2b-banner-mobile-736-f7a0fea027670d85b929d4297f46cb51.png

687 ms

b2b-banner-740-4844d0180cad1326e6a0be5783b282b5.png

b2b-banner-740-4844d0180cad1326e6a0be5783b282b5.png

686 ms

app_store_badge_desktop_en-79b8b5a578eb1f4d7bf116fad64f53e6.svg

app_store_badge_desktop_en-79b8b5a578eb1f4d7bf116fad64f53e6.svg

690 ms

qwe.gif

qwe.gif

336 ms

qweqwe.gif

qweqwe.gif

340 ms

google_play_badge_desktop_en-897e4cf70065f669b8bbc97bb9ccb5cb.svg

google_play_badge_desktop_en-897e4cf70065f669b8bbc97bb9ccb5cb.svg

638 ms

8535-0326d41acac87831.js

8535-0326d41acac87831.js

34 ms

_error-68db29eb80814b63.js

_error-68db29eb80814b63.js

183 ms

f300d951c442f2c8.css

f300d951c442f2c8.css

36 ms

Accessibility Review

preply.org accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

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

Best Practices

preply.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

preply.org SEO score

95

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

preply.org

Open Graph data is detected on the main page of Preply. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: