Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

liquipedia.net

Liquipedia

Page Load Speed

2.9 sec in total

First Response

167 ms

Resources Loaded

1.6 sec

Page Rendered

1.1 sec

About Website

Welcome to liquipedia.net homepage info - get ready to check Liquipedia best content for United States right away, or after learning these important things about liquipedia.net

The esports wiki, the best resource for live updated results, tournament overview, team and player profiles, game information, and more...

Visit liquipedia.net

Key Findings

We analyzed Liquipedia.net page load time and found that the first response time was 167 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

liquipedia.net performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value460 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

liquipedia.net

167 ms

liquipedia.net

360 ms

base.css

93 ms

dota2game.png

194 ms

dota2.png

410 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 92% of them (49 requests) were addressed to the original Liquipedia.net, 4% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (882 ms) belongs to the original domain Liquipedia.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.2 kB (5%)

Content Size

2.6 MB

After Optimization

2.5 MB

In fact, the total size of Liquipedia.net main page is 2.6 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. 25% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 140.6 kB

  • Original 164.2 kB
  • After minification 137.3 kB
  • After compression 23.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. This page needs HTML code to be minified as it can gain 26.9 kB, which is 16% 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 140.6 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.5 MB
  • After minification 2.5 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. Liquipedia images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 3.5 kB

  • Original 25.4 kB
  • After minification 25.4 kB
  • After compression 21.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 3.5 kB or 14% of the original size.

CSS Optimization

-1%

Potential reduce by 50 B

  • Original 3.9 kB
  • After minification 3.9 kB
  • After compression 3.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. Liquipedia.net has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

48

After Optimization

48

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Liquipedia. According to our analytics all requests are already optimized.

Accessibility Review

liquipedia.net accessibility score

100

Accessibility Issues

Best Practices

liquipedia.net best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

liquipedia.net SEO score

98

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

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 Liquipedia.net 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 Liquipedia.net 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

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