Tools & Wizards About Us
slime.cc screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

slime.cc

slime.cc | next generation slime soccer

Page Load Speed

3.3 sec in total

First Response

331 ms

Resources Loaded

2.9 sec

Page Rendered

161 ms

slime.cc screenshot

About Website

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

slime.cc is a brand new HTML-5 implementation of the game classics 'Slime Soccer'!

Visit slime.cc

Key Findings

We analyzed Slime.cc page load time and found that the first response time was 331 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

slime.cc performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

slime.cc

331 ms

www.slime.cc

576 ms

all.js

160 ms

bgSlimes.png

107 ms

headerBGLeft.png

312 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 23% of them (12 requests) were addressed to the original Slime.cc, 46% (24 requests) were made to Static.xx.fbcdn.net and 13% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (735 ms) belongs to the original domain Slime.cc.

Page Optimization Overview & Recommendations

Page size can be reduced by 27.7 kB (24%)

Content Size

113.2 kB

After Optimization

85.4 kB

  • HTML
  • Images

In fact, the total size of Slime.cc main page is 113.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. Images take 89.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 17.6 kB

  • Original 23.4 kB
  • After minification 21.6 kB
  • After compression 5.8 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 17.6 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 10.1 kB

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

Requests Breakdown

Number of requests can be reduced by 18 (36%)

Requests Now

50

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

slime.cc

slime.cc

331 ms

www.slime.cc

www.slime.cc

576 ms

all.js

all.js

160 ms

bgSlimes.png

bgSlimes.png

107 ms

headerBGLeft.png

headerBGLeft.png

312 ms

headerLOGO_beta.png

headerLOGO_beta.png

313 ms

howToPlay.png

howToPlay.png

420 ms

keyboard_instructions.png

keyboard_instructions.png

521 ms

highlights.png

highlights.png

525 ms

checkMark.png

checkMark.png

627 ms

comingSoon.png

comingSoon.png

629 ms

RemoteSlime.png

RemoteSlime.png

732 ms

feedback.png

feedback.png

735 ms

72 ms

xd_arbiter.php

xd_arbiter.php

141 ms

xd_arbiter.php

xd_arbiter.php

263 ms

comments.php

comments.php

128 ms

xd_arbiter.php

xd_arbiter.php

80 ms

like.php

like.php

59 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

292 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

330 ms

kyEKgjk51ZE.css

kyEKgjk51ZE.css

344 ms

xgj7bXhJNEH.css

xgj7bXhJNEH.css

388 ms

yBwS6rJyogl.css

yBwS6rJyogl.css

392 ms

ZeuPykSxSED.css

ZeuPykSxSED.css

423 ms

1kPfZUdGrka.js

1kPfZUdGrka.js

461 ms

Yuj_Y8xNH2C.js

Yuj_Y8xNH2C.js

481 ms

Mpe38fuBVZ2.js

Mpe38fuBVZ2.js

393 ms

qcMicXoOToy.js

qcMicXoOToy.js

547 ms

57RpJa05x58.js

57RpJa05x58.js

494 ms

7B-2ZS3Qt8r.js

7B-2ZS3Qt8r.js

436 ms

8wtUEv78jE-.js

8wtUEv78jE-.js

500 ms

zCWUGti5Sun.js

zCWUGti5Sun.js

494 ms

qbq-BpUy1j9.js

qbq-BpUy1j9.js

536 ms

BmFj6FmaQGO.js

BmFj6FmaQGO.js

502 ms

dX_jFPT72am.js

dX_jFPT72am.js

504 ms

n8qIhCw3vMx.js

n8qIhCw3vMx.js

511 ms

odA9sNLrE86.jpg

odA9sNLrE86.jpg

132 ms

62741_112991242093613_492034_n.jpg

62741_112991242093613_492034_n.jpg

206 ms

like.png

like.png

111 ms

fav.png

fav.png

40 ms

6339_4586536513453_786929335_n.jpg

6339_4586536513453_786929335_n.jpg

120 ms

385206_575927332421392_631590222_n.jpg

385206_575927332421392_631590222_n.jpg

124 ms

12079066_10208117667966236_7389881634277464498_n.jpg

12079066_10208117667966236_7389881634277464498_n.jpg

125 ms

12065830_10208337843267366_4570051023121807718_n.jpg

12065830_10208337843267366_4570051023121807718_n.jpg

127 ms

11220113_10156270468900556_859498719363023757_n.jpg

11220113_10156270468900556_859498719363023757_n.jpg

160 ms

1932274_10152308243949573_375867927_n.jpg

1932274_10152308243949573_375867927_n.jpg

126 ms

eRZ-2twM17f.png

eRZ-2twM17f.png

44 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

42 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

40 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

42 ms

AmlxWlqMvlv.js

AmlxWlqMvlv.js

44 ms

Accessibility Review

slime.cc accessibility score

86

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

slime.cc 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

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

slime.cc SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slime.cc can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Slime.cc main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

slime.cc

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