Tools & Wizards About Us
wol.gg screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

wol.gg

Wasted On LoL - How much time I wasted on League of Legends ?

Page Load Speed

1 sec in total

First Response

21 ms

Resources Loaded

926 ms

Page Rendered

63 ms

wol.gg screenshot

About Website

Click here to check amazing Wol content for Germany. Otherwise, check out these important facts you probably never knew about wol.gg

Have you ever wondered how much time you spend on LoL ? An average player has spent 832 hours on League of Legends and 8.468.557 players took the test. And you ?

Visit wol.gg

Key Findings

We analyzed Wol.gg page load time and found that the first response time was 21 ms and then it took 989 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

wol.gg performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

wol.gg

21 ms

wol.gg

205 ms

css

59 ms

app.js

175 ms

less.min.js

56 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 40% of them (18 requests) were addressed to the original Wol.gg, 40% (18 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (205 ms) belongs to the original domain Wol.gg.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.9 kB (9%)

Content Size

441.1 kB

After Optimization

403.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wol.gg main page is 441.1 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. 45% of websites need less resources to load. Javascripts take 388.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 35.8 kB

  • Original 45.7 kB
  • After minification 44.4 kB
  • After compression 10.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 35.8 kB or 78% of the original size.

Image Optimization

-29%

Potential reduce by 2.0 kB

  • Original 6.8 kB
  • After minification 4.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. Obviously, Wol needs image optimization as it can save up to 2.0 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 116 B

  • Original 388.5 kB
  • After minification 388.5 kB
  • After compression 388.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 14 (58%)

Requests Now

24

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wol.gg

wol.gg

21 ms

wol.gg

wol.gg

205 ms

css

css

59 ms

app.js

app.js

175 ms

less.min.js

less.min.js

56 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

55 ms

jquery-ui.min.js

jquery-ui.min.js

45 ms

all.js

all.js

70 ms

adsbytwadsgg.js

adsbytwadsgg.js

104 ms

app.js

app.js

45 ms

email-decode.min.js

email-decode.min.js

44 ms

js

js

75 ms

wol.js

wol.js

16 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

46 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

94 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

101 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

102 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

101 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

102 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

99 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

99 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

109 ms

wologo.png

wologo.png

45 ms

162 ms

260-united-kingdom.svg

260-united-kingdom.svg

75 ms

224-portugal.svg

224-portugal.svg

73 ms

094-south-korea.svg

094-south-korea.svg

72 ms

162-germany.svg

162-germany.svg

93 ms

128-spain.svg

128-spain.svg

99 ms

248-russia.svg

248-russia.svg

96 ms

218-turkey.svg

218-turkey.svg

99 ms

195-france.svg

195-france.svg

94 ms

211-poland.svg

211-poland.svg

93 ms

063-japan.svg

063-japan.svg

108 ms

000-none.png

000-none.png

106 ms

redspawn.png

redspawn.png

107 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf

65 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf

65 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf

65 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0ow.ttf

65 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0ow.ttf

68 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf

71 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf

70 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf

71 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0ow.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0ow.ttf

70 ms

Accessibility Review

wol.gg accessibility score

61

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.

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

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

wol.gg best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wol.gg SEO score

91

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

wol.gg

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