Tools & Wizards About Us
lengalia.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    88% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lengalia.com

Spanisch Lernen Online: 24 Kurse zum Selbstlernen – Lengalia

Page Load Speed

3.2 sec in total

First Response

328 ms

Resources Loaded

2.6 sec

Page Rendered

243 ms

lengalia.com screenshot

About Website

Welcome to lengalia.com homepage info - get ready to check Lengalia best content for Chile right away, or after learning these important things about lengalia.com

Spanisch Lernen Online: 24 Spanischkurse zum Selbstlernen, plus Podcasts, Videos und Tutor. Abschlusszertifikat nach dem Europäische Referenzrahmen GER.

Visit lengalia.com

Key Findings

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

Performance Metrics

lengalia.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

privatkunden.html

328 ms

stylesheet_6c6dd11024.css

184 ms

CssBasic.css

188 ms

lengalia2.css

553 ms

jplayer.css

191 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 85% of them (51 requests) were addressed to the original Lengalia.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (644 ms) belongs to the original domain Lengalia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 498.5 kB (58%)

Content Size

858.3 kB

After Optimization

359.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lengalia.com main page is 858.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. 30% of websites need less resources to load. Javascripts take 448.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.1 kB

  • Original 34.3 kB
  • After minification 32.8 kB
  • After compression 8.3 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 26.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 180 B

  • Original 190.3 kB
  • After minification 190.1 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. Lengalia images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 314.2 kB

  • Original 448.4 kB
  • After minification 405.2 kB
  • After compression 134.3 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 314.2 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 158.1 kB

  • Original 185.2 kB
  • After minification 153.5 kB
  • After compression 27.2 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. Lengalia.com needs all CSS files to be minified and compressed as it can save up to 158.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (49%)

Requests Now

57

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

privatkunden.html

privatkunden.html

328 ms

stylesheet_6c6dd11024.css

stylesheet_6c6dd11024.css

184 ms

CssBasic.css

CssBasic.css

188 ms

lengalia2.css

lengalia2.css

553 ms

jplayer.css

jplayer.css

191 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

476 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

384 ms

conversion.js

conversion.js

15 ms

lengalia.js

lengalia.js

278 ms

dropdown.js

dropdown.js

189 ms

button.js

button.js

189 ms

carousel.js

carousel.js

292 ms

jquery.datetimepicker.js

jquery.datetimepicker.js

473 ms

parsley.min.js

parsley.min.js

472 ms

tabs.js

tabs.js

383 ms

form.js

form.js

386 ms

powermail_frontend.js

powermail_frontend.js

476 ms

css

css

24 ms

NavbarBg.png

NavbarBg.png

94 ms

de.gif

de.gif

99 ms

es.gif

es.gif

100 ms

gb.gif

gb.gif

94 ms

fr.gif

fr.gif

95 ms

it.gif

it.gif

99 ms

br.gif

br.gif

178 ms

logo_lengalia.png

logo_lengalia.png

186 ms

Home.jpg

Home.jpg

187 ms

RTEmagicC_b4896374f0.gif.gif

RTEmagicC_b4896374f0.gif.gif

188 ms

RTEmagicC_485ee6a8be.gif.gif

RTEmagicC_485ee6a8be.gif.gif

190 ms

RTEmagicC_60b48e69b9.gif.gif

RTEmagicC_60b48e69b9.gif.gif

190 ms

RTEmagicC_lerntools.gif.gif

RTEmagicC_lerntools.gif.gif

271 ms

RTEmagicC_d8f9d8ad7e.gif.gif

RTEmagicC_d8f9d8ad7e.gif.gif

279 ms

werbung-Home-de.png

werbung-Home-de.png

462 ms

RTEmagicC_sterne-webertung-home.gif.gif

RTEmagicC_sterne-webertung-home.gif.gif

279 ms

RTEmagicC_beratung-home.jpg.jpg

RTEmagicC_beratung-home.jpg.jpg

283 ms

telefon-beratung-home.gif

telefon-beratung-home.gif

284 ms

Stempel_lengalia_vektor_de_01.png

Stempel_lengalia_vektor_de_01.png

362 ms

karte61.png

karte61.png

371 ms

RTEmagicC_all-in-flat-karusell_03.gif.gif

RTEmagicC_all-in-flat-karusell_03.gif.gif

373 ms

RTEmagicC_left.gif.gif

RTEmagicC_left.gif.gif

378 ms

RTEmagicC_right.gif.gif

RTEmagicC_right.gif.gif

378 ms

RTEmagicC_9a485afd84.gif.gif

RTEmagicC_9a485afd84.gif.gif

453 ms

RTEmagicC_b5d6a3e932.gif.gif

RTEmagicC_b5d6a3e932.gif.gif

462 ms

RTEmagicC_0a8c0db74c.gif.gif

RTEmagicC_0a8c0db74c.gif.gif

462 ms

RTEmagicC_e32bf6ddf7.gif.gif

RTEmagicC_e32bf6ddf7.gif.gif

468 ms

RTEmagicC_9d30075527.gif.gif

RTEmagicC_9d30075527.gif.gif

468 ms

RTEmagicC_42ef5f7ea3.gif.gif

RTEmagicC_42ef5f7ea3.gif.gif

558 ms

RTEmagicC_92365d6277.gif.gif

RTEmagicC_92365d6277.gif.gif

557 ms

RTEmagicC_41ab408a32.gif.gif

RTEmagicC_41ab408a32.gif.gif

558 ms

RTEmagicC_1dcbc48642.gif.gif

RTEmagicC_1dcbc48642.gif.gif

557 ms

RTEmagicC_a996dc5453.gif.gif

RTEmagicC_a996dc5453.gif.gif

561 ms

RTEmagicC_d29e850d99.gif.gif

RTEmagicC_d29e850d99.gif.gif

562 ms

RTEmagicC_74706d9532.gif.gif

RTEmagicC_74706d9532.gif.gif

644 ms

piwik.js

piwik.js

464 ms

c2KTkZ_oLp2UOMwi4GGs9A.woff

c2KTkZ_oLp2UOMwi4GGs9A.woff

34 ms

47 ms

analytics.js

analytics.js

31 ms

392 ms

collect

collect

18 ms

44 ms

Accessibility Review

lengalia.com accessibility score

77

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lengalia.com SEO score

86

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

lengalia.com

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