Tools & Wizards About Us
wererat.net screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

wererat.net

The Wererat's Lair: Sometimes, horror is cute(TM)

Page Load Speed

300 ms in total

First Response

73 ms

Resources Loaded

167 ms

Page Rendered

60 ms

wererat.net screenshot

About Website

Click here to check amazing Wererat content. Otherwise, check out these important facts you probably never knew about wererat.net

The Wererat's Lair: Sometimes, horror is cute(TM).

Visit wererat.net

Key Findings

We analyzed Wererat.net page load time and found that the first response time was 73 ms and then it took 227 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

wererat.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

wererat.net

73 ms

wererat.net

25 ms

index.css

4 ms

entrance.js

11 ms

copyright.js

10 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that all of those requests were addressed to Wererat.net and no external sources were called. The less responsive or slowest element that took the longest time to load (73 ms) belongs to the original domain Wererat.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.7 kB (63%)

Content Size

10.7 kB

After Optimization

4.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Wererat.net main page is 10.7 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. 15% of websites need less resources to load. HTML takes 9.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 6.4 kB

  • Original 9.0 kB
  • After minification 8.7 kB
  • After compression 2.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. 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 6.4 kB or 72% of the original size.

JavaScript Optimization

-14%

Potential reduce by 130 B

  • Original 947 B
  • After minification 947 B
  • After compression 817 B

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 130 B or 14% of the original size.

CSS Optimization

-18%

Potential reduce by 139 B

  • Original 788 B
  • After minification 788 B
  • After compression 649 B

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. Wererat.net needs all CSS files to be minified and compressed as it can save up to 139 B or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (13%)

Requests Now

48

After Optimization

42

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wererat.net

wererat.net

73 ms

wererat.net

wererat.net

25 ms

index.css

index.css

4 ms

entrance.js

entrance.js

11 ms

copyright.js

copyright.js

10 ms

email.js

email.js

17 ms

lair1.gif

lair1.gif

7 ms

lair2.gif

lair2.gif

6 ms

lair3.gif

lair3.gif

4 ms

lair4.gif

lair4.gif

7 ms

lair5.gif

lair5.gif

9 ms

lair6.gif

lair6.gif

11 ms

lair7.gif

lair7.gif

10 ms

lair8.gif

lair8.gif

10 ms

lair9.gif

lair9.gif

11 ms

lair10.gif

lair10.gif

23 ms

lair11.gif

lair11.gif

14 ms

lair12.gif

lair12.gif

14 ms

lair13.gif

lair13.gif

13 ms

lair14.gif

lair14.gif

14 ms

lair15.gif

lair15.gif

16 ms

lair16.gif

lair16.gif

18 ms

lair17.gif

lair17.gif

17 ms

bigrateyes.gif

bigrateyes.gif

18 ms

lair1g.gif

lair1g.gif

19 ms

lair2g.gif

lair2g.gif

22 ms

lair3g.gif

lair3g.gif

21 ms

lair4g.gif

lair4g.gif

25 ms

lair5g.gif

lair5g.gif

21 ms

lair6g.gif

lair6g.gif

23 ms

lair7g.gif

lair7g.gif

32 ms

lair8g.gif

lair8g.gif

25 ms

lair9g.gif

lair9g.gif

27 ms

lair10g.gif

lair10g.gif

26 ms

lair11g.gif

lair11g.gif

28 ms

lair12g.gif

lair12g.gif

28 ms

lair13g.gif

lair13g.gif

28 ms

lair14g.gif

lair14g.gif

31 ms

lair15g.gif

lair15g.gif

33 ms

lair16g.gif

lair16g.gif

32 ms

lair17g.gif

lair17g.gif

31 ms

bigrateyesg.gif

bigrateyesg.gif

32 ms

urhere.gif

urhere.gif

33 ms

dot.gif

dot.gif

32 ms

rateyes4.gif

rateyes4.gif

31 ms

rateyes3.gif

rateyes3.gif

31 ms

rateyes1.gif

rateyes1.gif

30 ms

rateyes2.gif

rateyes2.gif

30 ms

rateyes5.gif

rateyes5.gif

31 ms

wdlogo.gif

wdlogo.gif

30 ms

Accessibility Review

wererat.net accessibility score

68

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

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

Image elements do not have [alt] attributes

Best Practices

wererat.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

Serves images with low resolution

SEO Factors

wererat.net SEO score

69

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

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

wererat.net

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