7.9 sec in total
1.3 sec
5.8 sec
847 ms
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.jpWe 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.
himo2.jp performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value6.1 s
12/100
25%
Value8.6 s
17/100
10%
Value1,160 ms
22/100
30%
Value0.112
86/100
15%
Value12.2 s
15/100
10%
1268 ms
374 ms
378 ms
375 ms
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 size can be reduced by 295.5 kB (24%)
1.2 MB
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.
Potential reduce by 66.0 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.
Potential reduce by 169.1 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.
Potential reduce by 41.8 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.
Potential reduce by 18.5 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.
Number of requests can be reduced by 31 (42%)
74
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.
himo2.jp
1268 ms
pagenavi-css.css
374 ms
style.css
378 ms
AdLantisLoader.js
375 ms
topsy.js
158 ms
HT201285
73 ms
widgets.js
5 ms
bookmark_button.js
369 ms
HIMOTETAIMUZU.js
828 ms
ybm16.gif
569 ms
clip_16_16_w.gif
360 ms
5191400
468 ms
button-only.gif
345 ms
body_bg.jpg
332 ms
header_bg.gif
497 ms
logo.gif
668 ms
twitter_link.gif
349 ms
rss_link.gif
354 ms
container_bg.jpg
365 ms
QR_Code-12.jpg
1057 ms
468x60.gif
849 ms
tag_left.jpg
712 ms
tag_right.jpg
706 ms
a0001_01246116.jpg
1488 ms
a0001_0079955.jpg
1702 ms
a0001_00805512.jpg
1803 ms
a0002_0041014.jpg
1972 ms
a0002_0040999.jpg
1931 ms
a0001_0124659.jpg
2247 ms
a0001_0124879.jpg
2578 ms
a0001_0124778.jpg
2797 ms
a0002_0041013.jpg
3065 ms
a0001_00805511.jpg
2961 ms
himote_011.jpg
2535 ms
tonya1.jpg
2793 ms
a0960_000738.jpg
3262 ms
f551db96fc0eeeab68d4f5bd9c456d371.jpg
3441 ms
hiroN2_1-300x300.jpg
3675 ms
74a83926d1aa514c5f38fac49a21de07.jpg
4097 ms
himoterogo1.jpg
3307 ms
himote_00.jpg
3936 ms
49e58d98063ca908501829a5a65c89481.jpg
4168 ms
E1250646344778_1_s.jpg
4058 ms
5192600
474 ms
5190200
508 ms
5182600
510 ms
5187400
523 ms
5184000
558 ms
5180700
809 ms
5174900
827 ms
5173100
863 ms
5171900
864 ms
link_botton.gif
3802 ms
tag_bg.jpg
3997 ms
more.jpg
4017 ms
192 ms
container_foot.jpg
4087 ms
footer_bg.jpg
4204 ms
ga.js
30 ms
__utm.gif
12 ms
__utm.gif
22 ms
reset.css
9 ms
entry-button.css
9 ms
button-counter.gif
6 ms
411 ms
356 ms
402 ms
405 ms
408 ms
358 ms
536 ms
538 ms
583 ms
adlantis.www.js
553 ms
swfobject.js
578 ms
chartbeat.js
24 ms
himo2.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
<object> elements do not have alternate text
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
himo2.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
himo2.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
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.
himo2.jp
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: