Tools & Wizards About Us
lingobus.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

lingobus.com

Online Chinese Learning, Learn Mandarin Online, E-Learning for Kids| Lingo Bus

Page Load Speed

6.6 sec in total

First Response

646 ms

Resources Loaded

4.5 sec

Page Rendered

1.5 sec

lingobus.com screenshot

About Website

Visit lingobus.com now to see the best up-to-date Lingo Bus content for Canada and also check out these interesting facts you probably never knew about lingobus.com

Chinese learning courses for kids from 4 to 15 years old. Lingo Bus is an online Mandarin learning platform consisting of professional Chinese teachers.

Visit lingobus.com

Key Findings

We analyzed Lingobus.com page load time and found that the first response time was 646 ms and then it took 6 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

lingobus.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value12.1 s

4/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.95

3/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

lingobus.com

646 ms

www.lingobus.com

852 ms

gtm.js

49 ms

index.css

477 ms

chunk-vendors.a1f4d8a7.css

283 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 7% of them (7 requests) were addressed to the original Lingobus.com, 82% (77 requests) were made to S.vipkidstatic.com and 5% (5 requests) were made to Sensorsdata.vipkid.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source S.vipkidstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 538.1 kB (14%)

Content Size

3.8 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lingobus.com main page is 3.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. 60% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 205.8 kB

  • Original 253.7 kB
  • After minification 247.2 kB
  • After compression 48.0 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 205.8 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 14.8 kB

  • Original 2.8 MB
  • After minification 2.8 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. Lingo Bus images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 304.8 kB

  • Original 642.1 kB
  • After minification 638.8 kB
  • After compression 337.4 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 304.8 kB or 47% of the original size.

CSS Optimization

-20%

Potential reduce by 12.7 kB

  • Original 62.3 kB
  • After minification 62.3 kB
  • After compression 49.6 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. Lingobus.com needs all CSS files to be minified and compressed as it can save up to 12.7 kB or 20% of the original size.

Requests Breakdown

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

Requests Now

87

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lingobus.com

lingobus.com

646 ms

www.lingobus.com

www.lingobus.com

852 ms

gtm.js

gtm.js

49 ms

index.css

index.css

477 ms

chunk-vendors.a1f4d8a7.css

chunk-vendors.a1f4d8a7.css

283 ms

app.c1ea1306.css

app.c1ea1306.css

281 ms

preview-header-img.png

preview-header-img.png

285 ms

12.png

12.png

300 ms

13.png

13.png

277 ms

14.png

14.png

293 ms

15.png

15.png

281 ms

16.png

16.png

282 ms

17.png

17.png

308 ms

18.png

18.png

281 ms

19.png

19.png

284 ms

20.png

20.png

287 ms

21.png

21.png

284 ms

overview-mascot.36ff4f35.png

overview-mascot.36ff4f35.png

531 ms

home-customer_1.jpg

home-customer_1.jpg

278 ms

home-customer_2.jpg

home-customer_2.jpg

343 ms

home-customer_3.jpg

home-customer_3.jpg

285 ms

cooperation_2.3e6bf79f.png

cooperation_2.3e6bf79f.png

524 ms

cooperation_4.99ef39d2.png

cooperation_4.99ef39d2.png

523 ms

chunk-vendors.d0604712.js

chunk-vendors.d0604712.js

282 ms

app.cb3160e1.js

app.cb3160e1.js

285 ms

gt.js

gt.js

71 ms

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~5a1b4d44.4746b1e6.js

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~5a1b4d44.4746b1e6.js

14 ms

appdownload-~appdownload--vue~faq-article--~faq-article---vue~faq-category--~faq-category---vue~faq-~c9762b68.6fa5faa7.css

appdownload-~appdownload--vue~faq-article--~faq-article---vue~faq-category--~faq-category---vue~faq-~c9762b68.6fa5faa7.css

103 ms

appdownload-~appdownload--vue~faq-article--~faq-article---vue~faq-category--~faq-category---vue~faq-~c9762b68.4d46f20f.js

appdownload-~appdownload--vue~faq-article--~faq-article---vue~faq-category--~faq-category---vue~faq-~c9762b68.4d46f20f.js

35 ms

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~3a9bc72e.6df7e364.css

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~3a9bc72e.6df7e364.css

24 ms

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~3a9bc72e.abac3ac6.js

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~3a9bc72e.abac3ac6.js

27 ms

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~6be98466.8507e8e0.css

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~6be98466.8507e8e0.css

13 ms

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~6be98466.740884c2.js

home-~home--vue~home-complete-register--~home-complete-register-dlg---~home-complete-register-fullpa~6be98466.740884c2.js

14 ms

home--vue.53bd24f9.css

home--vue.53bd24f9.css

60 ms

home--vue.214a39ad.js

home--vue.214a39ad.js

52 ms

lingobus_medium_darktm.png

lingobus_medium_darktm.png

281 ms

whatsApp.414da3bd.png

whatsApp.414da3bd.png

71 ms

wechat-qr.e4843316.png

wechat-qr.e4843316.png

150 ms

wechat.0cc7929e.png

wechat.0cc7929e.png

24 ms

fast-register-dlg-head.96fbf68e.png

fast-register-dlg-head.96fbf68e.png

71 ms

logoV2.png

logoV2.png

51 ms

default-banner.jpg

default-banner.jpg

49 ms

icon-arrow-down.30d4f3bb.svg

icon-arrow-down.30d4f3bb.svg

25 ms

home-statistics-bg.jpg

home-statistics-bg.jpg

1281 ms

home-overview-bg.jpg

home-overview-bg.jpg

72 ms

example-pinyin-bg.77428254.png

example-pinyin-bg.77428254.png

71 ms

promise-bg.f27ce289.jpg

promise-bg.f27ce289.jpg

115 ms

1.png

1.png

72 ms

2.png

2.png

116 ms

3.png

3.png

178 ms

4.png

4.png

1611 ms

5.png

5.png

259 ms

6.png

6.png

200 ms

7.png

7.png

1368 ms

8.png

8.png

291 ms

9.png

9.png

215 ms

10.png

10.png

252 ms

11.png

11.png

291 ms

overview-mascot.36ff4f35.png

overview-mascot.36ff4f35.png

326 ms

design-icon_1.1896225c.png

design-icon_1.1896225c.png

314 ms

gift-step_1.dac14cc4.png

gift-step_1.dac14cc4.png

319 ms

gift-step_2.ae88c829.png

gift-step_2.ae88c829.png

342 ms

gift-step_3.2c1af1be.png

gift-step_3.2c1af1be.png

332 ms

gift-step_4.d88a6044.png

gift-step_4.d88a6044.png

330 ms

gift-step_5.00a58ca0.png

gift-step_5.00a58ca0.png

333 ms

cooperation_2.3e6bf79f.png

cooperation_2.3e6bf79f.png

335 ms

cooperation_4.99ef39d2.png

cooperation_4.99ef39d2.png

339 ms

investment.25e3924e.png

investment.25e3924e.png

351 ms

icon.2408be2d.svg

icon.2408be2d.svg

345 ms

icon-active.c4199198.svg

icon-active.c4199198.svg

448 ms

home-learning-cycle_bg.jpg

home-learning-cycle_bg.jpg

357 ms

js

js

47 ms

user-signin-.c4281c89.css

user-signin-.c4281c89.css

351 ms

saveUserAccess

saveUserAccess

450 ms

user-signin--vue.ba93434f.css

user-signin--vue.ba93434f.css

335 ms

user-signup--vue.87266499.css

user-signup--vue.87266499.css

334 ms

user-signin-.3fa85e98.js

user-signin-.3fa85e98.js

350 ms

user-signin--vue.8536f29c.js

user-signin--vue.8536f29c.js

326 ms

user-signup--vue.1d548a0b.js

user-signup--vue.1d548a0b.js

307 ms

PingFang.woff

PingFang.woff

1036 ms

gift-header.baefb021.png

gift-header.baefb021.png

357 ms

bus-logo.aebb9bae.png

bus-logo.aebb9bae.png

407 ms

30 ms

findus-fb@2x.deae8ac2.png

findus-fb@2x.deae8ac2.png

367 ms

linkedin.86207baa.svg

linkedin.86207baa.svg

1626 ms

youtube.0e666d4e.svg

youtube.0e666d4e.svg

429 ms

24 ms

instagram.c7b2b4b7.svg

instagram.c7b2b4b7.svg

409 ms

sensorsdata.1.16.1.min.js

sensorsdata.1.16.1.min.js

60 ms

sa.gif

sa.gif

901 ms

sa.gif

sa.gif

811 ms

sa.gif

sa.gif

600 ms

sa.gif

sa.gif

312 ms

sa.gif

sa.gif

212 ms

Accessibility Review

lingobus.com accessibility score

45

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.

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lingobus.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

lingobus.com SEO score

85

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

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lingobus.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lingobus.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

lingobus.com

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