Tools & Wizards About Us
wocabee.app screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wocabee.app

WocaBee

Page Load Speed

5.1 sec in total

First Response

232 ms

Resources Loaded

3 sec

Page Rendered

1.8 sec

wocabee.app screenshot

About Website

Visit wocabee.app now to see the best up-to-date Woca Bee content for Czech Republic and also check out these interesting facts you probably never knew about wocabee.app

WocaBee - an app for learning foreign-language vocabulary.

Visit wocabee.app

Key Findings

We analyzed Wocabee.app page load time and found that the first response time was 232 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

wocabee.app performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value3,530 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.43

22/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

wocabee.app

232 ms

wocabee.app

744 ms

bootstrap.css

191 ms

device-mockups.css

287 ms

all.min.css

400 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 81% of them (64 requests) were addressed to the original Wocabee.app, 6% (5 requests) were made to Youtube.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Wocabee.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 353.9 kB (12%)

Content Size

2.9 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wocabee.app main page is 2.9 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 109.8 kB

  • Original 125.0 kB
  • After minification 95.2 kB
  • After compression 15.2 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 29.7 kB, which is 24% 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 109.8 kB or 88% of the original size.

Image Optimization

-9%

Potential reduce by 212.8 kB

  • Original 2.3 MB
  • After minification 2.1 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. Woca Bee images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 28.2 kB

  • Original 365.2 kB
  • After minification 365.2 kB
  • After compression 337.0 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

-3%

Potential reduce by 3.2 kB

  • Original 124.0 kB
  • After minification 124.0 kB
  • After compression 120.8 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. Wocabee.app has all CSS files already compressed.

Requests Breakdown

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

Requests Now

70

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wocabee.app

wocabee.app

232 ms

wocabee.app

wocabee.app

744 ms

bootstrap.css

bootstrap.css

191 ms

device-mockups.css

device-mockups.css

287 ms

all.min.css

all.min.css

400 ms

slick.css

slick.css

300 ms

slick-theme.css

slick-theme.css

299 ms

css

css

37 ms

wocabee-new.css

wocabee-new.css

299 ms

wocabee-responsive-new.css

wocabee-responsive-new.css

297 ms

flag-icons.min.css

flag-icons.min.css

380 ms

jquery-3.6.0.js

jquery-3.6.0.js

497 ms

jquery-ui.min.js

jquery-ui.min.js

600 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

395 ms

slick.js

slick.js

407 ms

bootstrap.bundle.js

bootstrap.bundle.js

482 ms

responsivevoice.js

responsivevoice.js

67 ms

wocabee-new.js

wocabee-new.js

494 ms

wocabee-cookies.js

wocabee-cookies.js

506 ms

dvetyFzCCgo

dvetyFzCCgo

366 ms

logo.png

logo.png

419 ms

news_packagesByTopic.jpg

news_packagesByTopic.jpg

553 ms

news_contests.png

news_contests.png

520 ms

portrait_white.png

portrait_white.png

518 ms

bg2.jpg

bg2.jpg

176 ms

54e0d1474e54a914f6da8c7dda79367a173adde25a506c4870287fd19548cd5db8_640.jpg

54e0d1474e54a914f6da8c7dda79367a173adde25a506c4870287fd19548cd5db8_640.jpg

518 ms

57e9dd454c54ac14f6da8c7dda79367a173adde25a506c4870287fd19545c550be_640.jpg

57e9dd454c54ac14f6da8c7dda79367a173adde25a506c4870287fd19545c550be_640.jpg

519 ms

57e2d6474c57ab14f6da8c7dda79367a173adde25a506c4870287fd1954ec55db9_640.jpg

57e2d6474c57ab14f6da8c7dda79367a173adde25a506c4870287fd1954ec55db9_640.jpg

518 ms

57e2dc454e52ae14f6da8c7dda79367a173adde25a506c4870287fd39048cc50b0_640.jpg

57e2dc454e52ae14f6da8c7dda79367a173adde25a506c4870287fd39048cc50b0_640.jpg

553 ms

57e3d5434f55ae14f6da8c7dda79367a173adde25a506c4870287fd2944fcd5bbf_640.jpg

57e3d5434f55ae14f6da8c7dda79367a173adde25a506c4870287fd2944fcd5bbf_640.jpg

552 ms

honeycomb-bg.svg

honeycomb-bg.svg

577 ms

portrait_black.png

portrait_black.png

688 ms

studentOliverDE.jpg

studentOliverDE.jpg

689 ms

studentMariaES.jpg

studentMariaES.jpg

689 ms

studentAdelHU.jpg

studentAdelHU.jpg

780 ms

studentAnetaSK.jpg

studentAnetaSK.jpg

780 ms

studentDominikCZ.jpg

studentDominikCZ.jpg

692 ms

studentDanielSK.jpg

studentDanielSK.jpg

913 ms

teacherAndreaSK.jpg

teacherAndreaSK.jpg

779 ms

teacherIrenaCZ.jpg

teacherIrenaCZ.jpg

914 ms

teacherSabineAU.jpg

teacherSabineAU.jpg

780 ms

teacherJaroslavCZ.jpg

teacherJaroslavCZ.jpg

807 ms

accessForDirector.png

accessForDirector.png

915 ms

accessForParents2.png

accessForParents2.png

918 ms

gb.svg

gb.svg

869 ms

de.svg

de.svg

902 ms

fr.svg

fr.svg

968 ms

es.svg

es.svg

997 ms

it.svg

it.svg

1013 ms

ru.svg

ru.svg

1015 ms

sk.svg

sk.svg

1014 ms

cz.svg

cz.svg

1016 ms

pl.svg

pl.svg

1065 ms

hu.svg

hu.svg

1091 ms

hr.svg

hr.svg

1108 ms

Overpass-VariableFont_wght.ttf

Overpass-VariableFont_wght.ttf

1112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

89 ms

fa-solid-900.ttf

fa-solid-900.ttf

1041 ms

www-player.css

www-player.css

10 ms

www-embed-player.js

www-embed-player.js

28 ms

base.js

base.js

56 ms

ad_status.js

ad_status.js

161 ms

fAKQRIhHJzkWPBJbxdRG8sE_4N5ZCu5h9VOYIQm4PUM.js

fAKQRIhHJzkWPBJbxdRG8sE_4N5ZCu5h9VOYIQm4PUM.js

125 ms

embed.js

embed.js

45 ms

fa-regular-400.ttf

fa-regular-400.ttf

608 ms

slick.woff

slick.woff

651 ms

ua.svg

ua.svg

678 ms

la.svg

la.svg

691 ms

team.jpg

team.jpg

695 ms

wocabee-post.png

wocabee-post.png

697 ms

credit-cards.png

credit-cards.png

713 ms

ajax-loader.gif

ajax-loader.gif

731 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

21 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

37 ms

bg_app.jpg

bg_app.jpg

754 ms

id

id

28 ms

gb.svg

gb.svg

725 ms

Create

Create

98 ms

GenerateIT

GenerateIT

14 ms

Accessibility Review

wocabee.app accessibility score

84

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

High

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

High

Form elements do not have associated labels

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

wocabee.app 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

Page has valid source maps

SEO Factors

wocabee.app 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

Document doesn't have a valid hreflang

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 Wocabee.app 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 Wocabee.app 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

wocabee.app

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