Tools & Wizards About Us
lorecase.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lorecase.org

Home - MC Top List - Minecraft Server List

Page Load Speed

4.6 sec in total

First Response

216 ms

Resources Loaded

4.2 sec

Page Rendered

166 ms

lorecase.org screenshot

About Website

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

Minecraft Server Top List! View the most liked Minecraft servers, YouTube Channels and other online sites, post your own, or bid for a top spot!

Visit lorecase.org

Key Findings

We analyzed Lorecase.org page load time and found that the first response time was 216 ms and then it took 4.4 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

lorecase.org performance score

0

Network Requests Diagram

lorecase.org

216 ms

www.mctoplist.net

1126 ms

bootstrap.min.cache.css

68 ms

style.cache.css

18 ms

custom.cache.css

81 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lorecase.org, 57% (50 requests) were made to Serverwolves.com and 10% (9 requests) were made to Cdn.discordapp.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Serverwolves.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 841.0 kB (47%)

Content Size

1.8 MB

After Optimization

965.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lorecase.org main page is 1.8 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. 60% of websites need less resources to load. Javascripts take 923.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 108.2 kB

  • Original 136.1 kB
  • After minification 136.0 kB
  • After compression 27.9 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 108.2 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 24.3 kB

  • Original 567.0 kB
  • After minification 542.7 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. Lorecase images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 565.1 kB

  • Original 923.5 kB
  • After minification 923.5 kB
  • After compression 358.5 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 565.1 kB or 61% of the original size.

CSS Optimization

-80%

Potential reduce by 143.5 kB

  • Original 179.6 kB
  • After minification 178.6 kB
  • After compression 36.1 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. Lorecase.org needs all CSS files to be minified and compressed as it can save up to 143.5 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

81

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lorecase.org

lorecase.org

216 ms

www.mctoplist.net

www.mctoplist.net

1126 ms

bootstrap.min.cache.css

bootstrap.min.cache.css

68 ms

style.cache.css

style.cache.css

18 ms

custom.cache.css

custom.cache.css

81 ms

responsive.cache.css

responsive.cache.css

89 ms

style.cache.css

style.cache.css

92 ms

font-awesome.min.cache.css

font-awesome.min.cache.css

89 ms

adsbygoogle.js

adsbygoogle.js

29 ms

jquery.js

jquery.js

117 ms

functions.js

functions.js

97 ms

jsapi

jsapi

47 ms

clipboard.min.js

clipboard.min.js

26 ms

jquery.marquee.min.js

jquery.marquee.min.js

46 ms

ads.js

ads.js

403 ms

perfect-scrollbar.css

perfect-scrollbar.css

45 ms

perfect-scrollbar.jquery.min.js

perfect-scrollbar.jquery.min.js

50 ms

platform.js

platform.js

63 ms

pace.min.js

pace.min.js

22 ms

api.js

api.js

23 ms

bootstrap.min.js

bootstrap.min.js

23 ms

header_img.png

header_img.png

711 ms

36f86b63069263cdba701fd9d9bdf3f4.jpg

36f86b63069263cdba701fd9d9bdf3f4.jpg

378 ms

142605.png

142605.png

12 ms

ec5d1ceb1ebff4d619e41355df59632b.gif

ec5d1ceb1ebff4d619e41355df59632b.gif

150 ms

status_2.png

status_2.png

11 ms

142866.png

142866.png

14 ms

ebf8d3cfb45db9f2a03f445d446d9a8e.gif

ebf8d3cfb45db9f2a03f445d446d9a8e.gif

379 ms

status_1.png

status_1.png

20 ms

142989.png

142989.png

20 ms

gif.php

gif.php

389 ms

142760.png

142760.png

52 ms

gif.php

gif.php

388 ms

143021.png

143021.png

50 ms

gif.php

gif.php

387 ms

gif.php

gif.php

489 ms

142418.png

142418.png

376 ms

gif.php

gif.php

628 ms

142687.png

142687.png

488 ms

gif.php

gif.php

719 ms

status_0.png

status_0.png

487 ms

143026.png

143026.png

487 ms

gif.php

gif.php

794 ms

142448.png

142448.png

496 ms

gif.php

gif.php

798 ms

142929.png

142929.png

496 ms

gif.php

gif.php

1086 ms

142912.png

142912.png

525 ms

gif.php

gif.php

1203 ms

142763.png

142763.png

628 ms

gif.php

gif.php

1206 ms

142705.png

142705.png

720 ms

gif.php

gif.php

1834 ms

142442.png

142442.png

800 ms

gif.php

gif.php

2202 ms

status_3.png

status_3.png

800 ms

minecommerce_test.png

minecommerce_test.png

804 ms

142499.png

142499.png

807 ms

60cdff7b996d806e14ded38803cd032b.jpg

60cdff7b996d806e14ded38803cd032b.jpg

370 ms

6b875c80682f807e0ffceeb7cf9e897b.jpg

6b875c80682f807e0ffceeb7cf9e897b.jpg

369 ms

586ae08ce6ab8f640abc48d3c7b2160a.jpg

586ae08ce6ab8f640abc48d3c7b2160a.jpg

369 ms

65ff3a221e1d016f448123d4cd93152c.jpg

65ff3a221e1d016f448123d4cd93152c.jpg

381 ms

5aeb68c29b56b3d92eddb6f46df5051c.jpg

5aeb68c29b56b3d92eddb6f46df5051c.jpg

380 ms

defe7bf415f189104f1063d882696118.jpg

defe7bf415f189104f1063d882696118.jpg

380 ms

3.png

3.png

379 ms

56161b522e652e9829b203ff8ec97c7e.jpg

56161b522e652e9829b203ff8ec97c7e.jpg

380 ms

ca-pub-8179315880011483.js

ca-pub-8179315880011483.js

286 ms

zrt_lookup.html

zrt_lookup.html

404 ms

show_ads_impl.js

show_ads_impl.js

294 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2244 ms

down_arrow.png

down_arrow.png

979 ms

atrk.js

atrk.js

282 ms

chat_icon.png

chat_icon.png

711 ms

ads

ads

249 ms

osd.js

osd.js

72 ms

analytics.js

analytics.js

104 ms

pla

pla

52 ms

recaptcha__en.js

recaptcha__en.js

63 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

18 ms

iframe

iframe

52 ms

atrk.gif

atrk.gif

35 ms

collect

collect

19 ms

collect

collect

49 ms

1702706607-idpiframe.js

1702706607-idpiframe.js

14 ms

iframerpc

iframerpc

49 ms

ga-audiences

ga-audiences

15 ms

header_img.png

header_img.png

400 ms

SEO Factors

lorecase.org SEO score

0

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

lorecase.org

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