Tools & Wizards About Us
vokabel.org screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

vokabel.org

Online Vokabeltrainer | Vokabeln lernen kostenlos

Page Load Speed

2.1 sec in total

First Response

409 ms

Resources Loaded

1.6 sec

Page Rendered

100 ms

vokabel.org screenshot

About Website

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

Der perfekte Vokabeltrainer für Englisch, Spanisch und viele andere Sprachen. Optimiert für Smartphones und Tablets.

Visit vokabel.org

Key Findings

We analyzed Vokabel.org page load time and found that the first response time was 409 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

vokabel.org performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.371

29/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

www.vokabel.org

409 ms

wp-emoji-release.min.js

111 ms

style.css

214 ms

style.css

216 ms

jquery.js

368 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 59% of them (17 requests) were addressed to the original Vokabel.org, 17% (5 requests) were made to Pagead2.googlesyndication.com and 7% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (409 ms) belongs to the original domain Vokabel.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.1 kB (48%)

Content Size

288.2 kB

After Optimization

151.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vokabel.org main page is 288.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 225.8 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 11.1 kB

  • Original 15.6 kB
  • After minification 15.1 kB
  • After compression 4.5 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 11.1 kB or 71% of the original size.

Image Optimization

-2%

Potential reduce by 254 B

  • Original 13.2 kB
  • After minification 12.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. Vokabel images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 98.9 kB

  • Original 225.8 kB
  • After minification 224.4 kB
  • After compression 126.9 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 98.9 kB or 44% of the original size.

CSS Optimization

-80%

Potential reduce by 26.8 kB

  • Original 33.7 kB
  • After minification 22.8 kB
  • After compression 6.9 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. Vokabel.org needs all CSS files to be minified and compressed as it can save up to 26.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (39%)

Requests Now

28

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.vokabel.org

www.vokabel.org

409 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

111 ms

style.css

style.css

214 ms

style.css

style.css

216 ms

jquery.js

jquery.js

368 ms

jquery-migrate.min.js

jquery-migrate.min.js

218 ms

adsbygoogle.js

adsbygoogle.js

7 ms

cookieconsent.min.js

cookieconsent.min.js

11 ms

js-default.php

js-default.php

219 ms

navigation.js

navigation.js

218 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

320 ms

wp-embed.min.js

wp-embed.min.js

320 ms

ga.js

ga.js

98 ms

logo.png

logo.png

162 ms

start.png

start.png

163 ms

englisch.png

englisch.png

121 ms

logo.png

logo.png

161 ms

listenpool.png

listenpool.png

120 ms

zitate.png

zitate.png

120 ms

listen.png

listen.png

230 ms

ca-pub-7638201754831951.js

ca-pub-7638201754831951.js

100 ms

zrt_lookup.html

zrt_lookup.html

145 ms

show_ads_impl.js

show_ads_impl.js

101 ms

2709.png

2709.png

144 ms

__utm.gif

__utm.gif

54 ms

ads

ads

311 ms

osd.js

osd.js

8 ms

pla

pla

14 ms

dark-bottom.css

dark-bottom.css

3 ms

Accessibility Review

vokabel.org accessibility score

89

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

Best Practices

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

SEO Factors

vokabel.org SEO score

100

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

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 Vokabel.org 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 Vokabel.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

vokabel.org

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