Report Summary

  • 55

    Performance

    Renders faster than
    73% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

watamote.jp

私がモテないのはどう考えてもお前らが悪い!

Page Load Speed

5.4 sec in total

First Response

748 ms

Resources Loaded

4.3 sec

Page Rendered

354 ms

watamote.jp screenshot

About Website

Visit watamote.jp now to see the best up-to-date Watamote content for Japan and also check out these interesting facts you probably never knew about watamote.jp

「私がモテないのはどう考えてもお前らが悪い!」全喪が泣いた話題作、待望のTVアニメ化!

Visit watamote.jp

Key Findings

We analyzed Watamote.jp page load time and found that the first response time was 748 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

watamote.jp performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

watamote.jp

748 ms

base.css

309 ms

top.css

345 ms

colorbox.css

345 ms

jquery-1.9.1.min.js

1124 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 43% of them (24 requests) were addressed to the original Watamote.jp, 27% (15 requests) were made to Pbs.twimg.com and 14% (8 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Watamote.jp.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.8 MB

In fact, the total size of Watamote.jp main page is 2.0 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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 9.4 kB

  • Original 13.2 kB
  • After minification 13.1 kB
  • After compression 3.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 9.4 kB or 71% of the original size.

Image Optimization

-3%

Potential reduce by 55.3 kB

  • Original 1.8 MB
  • After minification 1.7 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. Watamote images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 82.6 kB

  • Original 121.2 kB
  • After minification 110.5 kB
  • After compression 38.6 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 82.6 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 33.1 kB

  • Original 40.2 kB
  • After minification 38.0 kB
  • After compression 7.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. Watamote.jp needs all CSS files to be minified and compressed as it can save up to 33.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (20%)

Requests Now

55

After Optimization

44

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

Accessibility Review

watamote.jp accessibility score

100

Accessibility Issues

Best Practices

watamote.jp best practices score

58

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

SEO Factors

watamote.jp SEO score

69

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watamote.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Watamote.jp 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 description is not detected on the main page of Watamote. 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: