Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

himo2.jp

匿名が基本のモテない人コミュニティ | 非モテ+

Page Load Speed

7.9 sec in total

First Response

1.3 sec

Resources Loaded

5.8 sec

Page Rendered

847 ms

himo2.jp screenshot

About Website

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

非モテ+は、匿名が基本のモテない人限定のコミュニティサイトです。既婚者や恋人がいる人も「自分はモテない」と言う自覚がある人であれば参加可能です。非モテSNSの姉妹サイト。

Visit himo2.jp

Key Findings

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

Performance Metrics

himo2.jp performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

himo2.jp

1268 ms

pagenavi-css.css

374 ms

style.css

378 ms

AdLantisLoader.js

375 ms

topsy.js

158 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 50% of them (38 requests) were addressed to the original Himo2.jp, 13% (10 requests) were made to Image.clip.livedoor.com and 13% (10 requests) were made to Cdn.api.b.hatena.ne.jp. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Himo2.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

923.3 kB

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

HTML Optimization

-83%

Potential reduce by 66.0 kB

  • Original 79.1 kB
  • After minification 64.9 kB
  • After compression 13.1 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 14.3 kB, which is 18% 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 66.0 kB or 83% of the original size.

Image Optimization

-16%

Potential reduce by 169.1 kB

  • Original 1.0 MB
  • After minification 857.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, Himo 2 needs image optimization as it can save up to 169.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-46%

Potential reduce by 41.8 kB

  • Original 89.9 kB
  • After minification 79.8 kB
  • After compression 48.1 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 41.8 kB or 46% of the original size.

CSS Optimization

-81%

Potential reduce by 18.5 kB

  • Original 22.9 kB
  • After minification 15.3 kB
  • After compression 4.4 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. Himo2.jp needs all CSS files to be minified and compressed as it can save up to 18.5 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

74

After Optimization

43

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

Accessibility Review

himo2.jp accessibility score

56

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

himo2.jp best practices score

75

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

SEO Factors

himo2.jp SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Himo2.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Himo2.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 Himo 2. 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: